fix(telescope-install): drop bin/fsa hard-dependency; spawn via dart run fluttersdk_telescope

[anilcancakir]

Summary

telescope:install no longer depends on the AOT-compiled bin/fsa. The chained subprocess calls (install + plugin:install fluttersdk_telescope) now spawn dart run fluttersdk_telescope ... directly through the telescope CLI wrapper, mirroring the Cat C subprocess pattern landed in fluttersdk_dusk (dusk_install_command.dart Step 3.3 of the cross-repo plan dusk-cli-fixes-rename).

Bug

Before this change, telescope:install spawned ./bin/fsa plugin:install fluttersdk_telescope HARDCODED. On a clean checkout where bin/fsa has not been AOT-compiled yet, the command crashed:

✗ Unexpected error in telescope:install: ProcessException: No such file or directory
  Command: ./bin/fsa plugin:install fluttersdk_telescope
#0 _ProcessImpl._start (dart:io-patch/process_patch.dart:411:33)
#1 Process.start (dart:io-patch/process_patch.dart:42:20)
#2 _runNonInteractiveProcess (dart:io-patch/process_patch.dart:613:18)
#3 Process.run (dart:io-patch/process_patch.dart:56:12)
#4 TelescopeInstallCommand._defaultProcessRunner (lib/src/commands/telescope_install_command.dart:56:15)
#5 TelescopeInstallCommand.handle (lib/src/commands/telescope_install_command.dart:97:40)

Same class of bug as Bug 1 from dusk-cli-fixes-rename (substrate mcp:install assumed bin/fsa unconditionally), discovered during that plan's E2E verification phase on a fresh flutter create consumer.

Fix

Route both chained subprocesses through dart run fluttersdk_telescope which proxies the artisan substrate via the telescope CLI wrapper (bin/fluttersdk_telescope.dart — preloads TelescopeArtisanProvider, sets delegateToConsumer: false). The wrapper itself is Flutter-free so the chain works on a clean checkout where fsa has not been compiled.

• lib/src/commands/telescope_install_command.dart:75-78: ['run', 'fluttersdk_artisan', 'install'] → ['run', 'fluttersdk_telescope', 'install'].
• lib/src/commands/telescope_install_command.dart:97-100: './bin/fsa' + ['plugin:install', 'fluttersdk_telescope'] → 'dart' + ['run', 'fluttersdk_telescope', 'plugin:install', 'fluttersdk_telescope'].
• Docblock at lines 5-30 updated to reflect the new behavior. The legacy claim about bin/artisan.dart wrapper rejection is removed — that constraint no longer applies once we route through the telescope-own CLI wrapper instead of fluttersdk_artisan.
• test/src/commands/telescope_install_command_test.dart: 3 test assertions updated to match the new subprocess args (test names + expected runner.calls shapes).
• CHANGELOG.md: ### Changed bullet under [Unreleased].

Surface unchanged for consumers who already have fsa scaffolded: the chained subprocess routes through the dart toolchain either way; ./bin/fsa is just a faster proxy when present.

Test plan

dart format --output=none --set-exit-if-changed lib/ test/ bin/    # clean
dart analyze lib/ test/ bin/                                        # No issues found
flutter test test/src/commands/telescope_install_command_test.dart  # 8 pass
flutter test --exclude-tags=integration --timeout=30s               # 249 pass

Plus E2E smoke against this branch:

# Fresh flutter create consumer, path-dep on telescope + artisan override
# bin/fsa absent (the precondition that triggered the bug):
dart run fluttersdk_telescope telescope:install
# →  Consumer wrapper missing; running install...
#    [scaffold output]
#    Registering fluttersdk_telescope via plugin:install...
#    [plugin install output]
#    Wiring TelescopePlugin into lib/main.dart...
#    ✓ telescope:install complete.

Pre-fix, the chain crashed at the second subprocess with ProcessException: No such file or directory because ./bin/fsa did not exist yet.

Companion PR cluster

This is a follow-up to the cross-repo dusk-cli-fixes-rename PR cluster:

• feat(mcp): add mcp:install --invocation=<exec> option for plugin-aware .mcp.json fallback artisan#18 — substrate --invocation flag
• fix(cli): bug 1 fallback + bug 3 collectMcpTools + full dart run fluttersdk_dusk rename dusk#10 — dusk-side Bug 1 + Bug 3 + rename sweep (where this same pattern fix landed for dusk's chained subprocesses in dusk_install_command.dart:123,151-155)
• fix(bin): force collectMcpTools: true for mcp:serve + inject --invocation for mcp:install #7 — telescope wrapper Bug 1 + Bug 3 (independent fix; this PR is structurally separate)
• fluttersdk/telescope#NEW (this PR) — telescope:install fastcli-absent fallback

Independent of #7; cuts cleanly from master so review and revert are isolated.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates telescope:install so it no longer assumes the consumer already has an AOT-compiled bin/fsa available, by routing the scaffold + plugin registration subprocesses through dart run fluttersdk_telescope ... instead.

Changes:

• Switch subprocess invocations from dart run fluttersdk_artisan install / ./bin/fsa plugin:install ... to dart run fluttersdk_telescope ... for both steps.
• Update TelescopeInstallCommand tests to assert the new subprocess executable/args and ordering.
• Add a [Unreleased] changelog entry describing the behavior change.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
lib/src/commands/telescope_install_command.dart	Routes both scaffold and plugin:install steps through dart run fluttersdk_telescope to remove the hard dependency on ./bin/fsa.
test/src/commands/telescope_install_command_test.dart	Updates assertions and test text to match the new subprocess calls.
CHANGELOG.md	Documents the install-chain change under [Unreleased].