feat: improve ADR command consequences quality

[tractorjuice]

Summary

Strengthens the Consequences section of the ADR command prompt to produce more actionable output:

• Project-specific metrics — require measurable outcomes tied to actual NFR/BR IDs (e.g., "API response time: 500ms → < 200ms per NFR-P-001") instead of generic "improved performance"
• Requirement traceability — tie each positive consequence to a specific requirement or stakeholder goal
• Explicit trade-offs — require mitigation strategies with named owners and timelines, not vague statements
• After-action review — schedule a review 1 month after implementation to verify assumptions

How this was found

Used the autoresearch command prompt optimiser against the UK Gov ADR Framework and MADR v4.0 references:

Iteration	Score	Status	Change
0 (baseline)	8.6	keep	—
1	9.0	keep	Strengthen consequences with project-specific metrics and after-action review
2	9.2	discard	Tie monitoring metrics to consequences (delta < 0.3)

Net: +3 lines of prompt, score 8.6 → 9.0

Test plan

• Run /arckit:adr against a test project and verify consequences reference specific NFR/BR IDs
• Verify trade-offs include named owners and timelines
• Verify after-action review is scheduled in output
• Run python scripts/converter.py to regenerate extension formats

🤖 Generated with Claude Code