Apply GH-DEC-2026-017 to the layer declaration; close KG-IN-0007.

INTENT.md frontmatter governs and layer.yaml is marked derived from it.
standard_version is removed from both forms (A12). The checker and its
tests change in the same commit: they no longer require the field, they
reject it, they fold case against the four-token vocabulary (A9) instead
of comparing with plain equality, and they still fail a layer disagreement
that survives the fold (A11). Neither layer value is re-spelled.

The ruling answers kings-guard's "validated-against" reading of the field
(§5: version-scoped state belongs in the derived conformance record), so
that version now lives in the checker as VALIDATED_AGAINST and is printed
in every run's output. The standard: path in INTENT.md is unversioned to
match the reference form.

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

decisions/decisions.md

@@ -360,3 +360,6 @@ dereferencing a judgment. Argument: `docs/StatuteV08Review.md` F1.
   §3.4 properties holding.
 - `layer.yaml` is not edited by this decision. Its `standard_version: "0.7"`
   stays pending the B4 ruling (`KG-IN-0007`, commentary F4).
+  *Superseded 2026-09-21:* B4 was ruled in `GH-DEC-2026-017` §5 and the field was
+  removed under `KG-IN-0007`; the validated-against version now lives in
+  `scripts/check_layer_conformance.py` (`VALIDATED_AGAINST`).