Record the second application round and the measured A12 split.

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

docs/assessments/2026-09-21-layer-declaration-boundaries.md

@@ -221,3 +221,27 @@ names the defect generally. The custodian's contribution that survived is the
   runbook would not reach the live publish path. Held for the operator.
 
 Ten repositories still carry the pre-ruling sidecar form.
+
+## Second round, 2026-09-21
+
+GH-DEC-2026-017 is applied in thirteen repositories. No `standard_version` field
+remains in any declaration, and no layer value was re-spelled. Seven
+repositories carried a copy of ops-warden's conformance checker, not five as
+first counted; zone-engine's was under `tools/`. Each required
+`standard_version`, and several compared layers with plain equality. Every one
+changed in the same commit as its field.
+
+Three questions about A12's reach went to gate-house with counts measured on
+disk. The repositories' own reports had suggested a 3–3 split on the versioned
+`standard:` path. On disk, only audit-core and user-engine still pin one.
+
+- **flex-auth** closed FLEX-WP-0022. It enforces tenant-engine's invariant
+  (`tenant` = `resource.id`) as a deny, and states and tests cross-tenant scope.
+  One exception is named: user-engine's onboarding grant excludes
+  `tenant:platform`. That was sent back to tenant-engine rather than decided.
+  v3 is not rolled out.
+- **tenant-engine** is admitted as an audit-core sender but cannot deliver:
+  the egress NetworkPolicy, the URL, and the token projection are missing from
+  its deploy manifests. TEN-IN-0005; this needs an operator credential path.
+- **secrets-engine** surfaced a question: the service JWT design names
+  `tenant:coulomb`, but the approval chain resolved to `tenant:platform`.