v0.2.62: Fix connected ACP agents and AMP

Hotfix for 0.2.61. If you are on 0.2.61, upgrade.

Fixed

• Connected ACP agents no longer refuse the first prompt. An agent could connect successfully,
  report a ready ACP session, and then fail to answer. Three separate hardcoded lists decided which agents
  could actually run: 19 short names in the message dispatch, 23 in the unified runner, and a command
  chain naming each agent individually. The registry ships 46 agents, so 23 of them were affected.

  Depending on which list was missed, the agent either:

  • answered 🚧 integration coming soon!
  • was silently executed as the opencode CLI, answering as the wrong vendor
  • was rejected with Unsupported ACP agent type

  Affected agents included GitHub Copilot, Cursor, Droid, Kiro, GLM, Qwen, Cline, and Kilo.

  Routing now keys off the protocol each agent declares and the run_command from its own registry
  entry, so a newly added agent works without editing the dispatch. A new test suite runs every registered
  agent through the dispatch on each CI run.

Notes

• GitHub Copilot is verified end to end: real TUI, real Copilot CLI, real prompt and answer, on a
  Copilot Free account.
• Other repaired agents are verified to route and resolve a launch command. Vendor-side issues
  (authentication, credits, plan limits) are reported by the agent itself and are unrelated to this fix