fix(aidd-orchestrator): hardcodes aidd-dev, violates cross-plugin orthogonality

[blafourcade]

Rule

Cross-plugin orthogonality: plugins never reference each other by name — orchestrators included. A skill discovers a cross-plugin capability at runtime by description matching, never a hardcoded aidd-<plugin>:… address. It is not yet mechanically enforced, so violations slip through.

Violation

aidd-orchestrator/skills/00-async-dev hardcodes aidd-dev:

Should delegate by capability:

• SKILL.md:29 + references/routing.md:36-37 — trigger regexes match /aidd-dev:02-implement, /aidd-dev:05-review.
• SKILL.md:81 — check-sdlc verifies aidd-dev:00-sdlc (should be "an SDLC-capable orchestrator").
• README.md:17 — pointer "use aidd-dev:00-sdlc".

Deployment-level (names the package to install it — harder to make capability-based):

• SKILL.md:62, actions/setup/07-install-user-scope-plugins.md, assets/setup/workflow-template.yml:165,260 — setup installs aidd-dev@aidd-framework.

Fix options

1. Capability-based for triggers + check-sdlc + README; leave setup/install naming the package.
2. Full: make setup capability-driven too (needs design).
3. Add a lefthook grep for cross-plugin literals so this can't regress.

Found during the docs rework while verifying ARCHITECTURE.md against the code.

Acceptance criteria

• No file under plugins/aidd-orchestrator/ names another plugin by address.
• The skill discovers an SDLC-capable orchestrator by capability, not by the string aidd-dev.
• Uninstalling aidd-dev degrades the flow with a clear message instead of failing on a missing address.
• The check from ci(framework): mechanically enforce cross-plugin orthogonality on PRs #250 passes on this plugin.

Related

• feat(aidd-orchestrator): route by discovered capability, not hardcoded plugin #146 — the feature whose absence causes this: with no runtime capability discovery, there is nothing to route by except a hardcoded address.
• ci(framework): mechanically enforce cross-plugin orthogonality on PRs #250 — the CI check that stops the next violation.
• refactor(aidd-orchestrator): async-dev is 1915 lines with a 131-line router, four times the median #420 — slims this same skill; its router holds the offending regexes. Land them together.

[blafourcade]

Two issues sit around this one:

• feat(aidd-orchestrator): route by discovered capability, not hardcoded plugin #146 (dynamic orchestration by installed plugins) is the feature whose absence causes this violation: with no runtime capability discovery, the orchestrator has nothing to route by except a hardcoded address.
• ci(framework): mechanically enforce cross-plugin orthogonality on PRs #250 (CI check for cross-plugin orthogonality) stops the next violation from landing. Fixing this one without that check means it recurs.

[blafourcade]

Related: #420 slims this same skill. Its router (131 lines) holds the routing regexes that hardcode aidd-dev. Fixing the address and shrinking the router touch the same lines — pair them.