fix(orchestrator): SDLC Frame hands a TBD-laden spec to Deliver unchecked

Read plugins/aidd-orchestrator/skills/01-sdlc/references/01-frame.md and compare its Spec → Contract flow with spec-validator.yml. Trace where the current flow skips validation. Done means invalid specs with residual TBD markers route to clarification before Deliver, while valid specs can continue.

Description

aidd-orchestrator:01-sdlc's Frame stage produces $contract via /aidd-pm:04-spec and hands it straight to Deliver, with no check that the spec it just wrote actually validates. A spec with residual TBD: markers in a required section (hard constraints, non-goals, done-when) is already invalid per spec-validator.yml's own definition (any_required_unfulfilled: invalid, constraints must be "concrete and testable, not vague") — but nothing in 01-frame.md's flow consults that validator before treating the spec as a finished $contract.

Found while dogfooding 04-spec (post-#564 router migration) on a real project: build correctly marked 3 genuine open questions (platform, sharing model, ingredient source) as TBD:, lifted straight from the source PRD's own Dependencies/Open Questions. That's 04-spec working as designed. But SDLC runs autonomously ("decide and act without confirmation, asking only before... a decision that requires user authority") — platform/sharing-model choices are exactly that kind of decision, yet nothing wires the TBD count to SDLC's own pause condition. A TBD-laden spec can silently flow into 02-deliver's Plan → Implement, building against undecided requirements.

Affected file(s)

plugins/aidd-orchestrator/skills/01-sdlc/references/01-frame.md

Expected behaviour

Before Spec --> Contract in 01-frame.md's flow, the spec must validate against spec-validator.yml (no residual TBD: in a required section). A spec that doesn't validate should route back to clarification (matching the "decision that requires user authority" pause SDLC already claims to honor) rather than continuing to Deliver.

Observed behaviour

01-frame.md's mermaid goes straight from Spec to Contract to Deliver, unconditionally. No validation gate, no reference to spec-validator.yml anywhere in the SDLC skill.

AI tool

Claude Code

OS

macOS

Additional context

Surfaced during #564's 04-spec router-contract migration (out of scope there — different plugin, no behaviour change allowed in that issue). spec-validator.yml itself is sound; the gap is purely that nothing in the orchestration layer consults it.