feat(aidd-orchestrator): route by discovered capability, not hardcoded plugin #146

Problem

The orchestrator's route is hardcoded. It names aidd-dev by address in its routing regexes and its check-sdlc step, which violates the cross-plugin orthogonality rule in docs/ARCHITECTURE.md — see #406, the concrete violation.

It has no choice today: nothing lets a skill discover, at runtime, what the installed plugins can do. So the pipeline is written down instead of derived.

Scope

An orchestrator that, on every request, reads what is available and proposes a plan, instead of replaying a fixed pipeline.

Its inputs:

• The installed plugins — context, dev, pm, vcs, ui, plus stack and craftsmanship plugins (feat(framework): specialized plugins — craftsmanship and tech stacks #148). It reads their skills and agents directly; no separate declaration contract.
• The project — its state, its memory, its detected stack.
• The request — what the user actually asked for.

Its output: an orchestration plan, presented, then run.

Acceptance criteria

• The orchestrator names no plugin by address. Remove the hardcoded aidd-dev and the routing regexes of fix(aidd-orchestrator): hardcodes aidd-dev, violates cross-plugin orthogonality #406, and nothing breaks.
• Installing a new plugin changes the plan it proposes, with no code change.
• Uninstalling a plugin degrades the plan instead of breaking it.
• The plan is shown before it runs.

Related

• fix(aidd-orchestrator): hardcodes aidd-dev, violates cross-plugin orthogonality #406 — the violation this feature makes impossible. Its call sites are the acceptance fixture.
• ci(framework): mechanically enforce cross-plugin orthogonality on PRs #250 — the CI check that stops the next violation from landing.