v1.6.0 — /context-report pre-empts committee-recurring findings

Changed — /context-report skill & documentation standard

Lessons distilled from generating several application context reports, encoded so future runs clear the review committee on the first pass:

• Valid CML — declare every context used in a relation (incl. external systems), keep the upstream/downstream direction right, one downstream strategy per upstream (ACL or Conformist, not both).
• ADRs as decision atoms — Context, Options considered with trade-offs, Decision, Consequences; outcome-only prose fails.
• Given/When/Then verifiable quality scenarios with anchor + RED/AMBER/green verdict.
• Cross-document count reconciliation — two authoritative docs must never contradict each other on the same seal; reconcile or fix.
• Complete Annex A inventories — promise N, list N.
• Honest severity calibration — a parametrized query with a constant-bounded table name is a mitigated smell, not a critical injection; reward calibration, reject both alarmism and omission.

Documentation standard (§5 ADR) gains a Common pitfalls note naming the three most frequent failures.

Fully generic — no example-stack or client/domain references. All 7 self-test suites green (178 asserts).