docs(857): refresh stale "out of scope" comments on landed phase-6 cutovers (#1126)

The render-hooks resolver and capability-state resolver headers (and their CONTEXT.md glossary entries) still claimed "no workflow calls this yet" / "consumed by nothing yet (phase-6 wiring is out of scope)". Both are now false: loop.render-hooks is consumed live by plan-phase.md/autonomous.md (plan:pre ui-phase, verify:post ui-review), and capability-state is the `gsd-tools capability state` CLI diagnostic.

Comment/prose only — no behavior change. Surfaced by the ADR-857 phase 1-5 completeness audit.

Closes #1125

Refs #857

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

src/loop-resolver.cts

@@ -5,7 +5,9 @@
  * filters the materialized Capability Registry by config activation and returns
  * the active hooks as a JSON envelope with a rendered-markdown field.
  *
- * REGISTRY-ONLY: no workflow calls this yet (phase-6 cutover is out of scope).
+ * Consumed live by the landed phase-6 loop-hook cutovers: plan-phase.md / autonomous.md
+ * at plan:pre (ui-phase) and autonomous.md at verify:post (ui-review). Further per-feature
+ * cutovers are ongoing.
  *
  * Command surface: gsd-tools loop render-hooks <point>
  *