Apply GH-DEC-2026-020: checker prints version and scope, A12 r2 by content.

The layer conformance checker now prints VALIDATED_AGAINST and SCOPE on every
run, including the PASS line (kings-guard pattern), and enforces A12 r2 over
every key and value of INTENT.md frontmatter and layer.yaml: a versioned
standard: path and a companion_version are caught, schema_version and comments
are not reached, pep-stance.yaml is outside the run. Tests guard both returns.
The playbook carries the adopter change set and confirms the section 5
citation is canonical. WARDEN-WP-0034's open 4220413a note is closed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703

workplans/WARDEN-WP-0034-layer-model-v07-conformance.md

@@ -292,6 +292,12 @@ says version-scoped state belongs in the derived conformance record, which
 checker that emits nothing durable, not an emitted record. Whether §11 expects an
 emitted artifact or a re-runnable check discharges it is asked of gate-house in
 message `4220413a` and unanswered. Nothing applied above depends on the answer.
+**Closed 2026-09-21 by `GH-DEC-2026-020` §4 (gate-house@104f3fc):** §5 was wrong
+that the record exists; a re-runnable checker is sufficient if every run prints
+the version it checks against and its scope. Applied: the checker now prints
+`VALIDATED_AGAINST` and `SCOPE` on every run and enforces A12 r2 by content, not
+key name (versioned `standard:` path, `companion_version`); `pep-stance.yaml`
+untouched per §3; the playbook carries the adopter change set.
 
 **Ruled the same day, and still `wait` — deliberately.** `GH-DEC-2026-017`
 (message `3715e247`) landed hours later: `INTENT.md` governs, the sidecar is a