ADR completeness and promotion

[ashleythedeveloper]

What

Audit ADRs 001-010 in docs/ADRs/. Write the four missing ADRs (semantic relations rationale, solution & deployment model, admin CLI, module integration patterns). Promote Draft ADRs to Accepted where the implementation matches.

Why

Currently 9 of 10 ADRs sit in Draft, and four important architectural decisions have no ADR yet. Drafts undermine the authority of the documents: contributors treat them as suggestions rather than constraints. Missing ADRs leave parts of the architecture without rationale.

Scope (in)

• Write the four missing ADRs (Write ADR for semantic relations #95, Write ADR for solution and deployment model #96, Write ADR for admin CLI #97, Write ADR for module integration patterns #98).
• Audit each existing ADR against current implementation; promote Drafts to Accepted, supersede where superseded, correct where stale (Promote ADRs from Draft to Accepted #101).
• Date fields updated on promotion.

Scope (out)

• New architectural decisions (those should arrive as new ADRs in their own scope).
• Implementing the things ADRs describe (that's the work of the other Epics).

Decomposition

Walking skeleton: audit ADRs 001-010, write one missing ADR (likely admin CLI, smallest), promote one Draft to Accepted, prove the workflow.

Subsequent Stories: each of the other three missing ADRs; one final pass to promote remaining Drafts.