Revert the npm field, re-measure coverage, and hold the layer divergence

Five inbox items worked, none of which changed a credential value or moved a
secret.

whynot-design-npm-publish: field reverted npm_token -> NPM_AUTH_TOKEN and the
path confirmed, on railiance-platform's attended, read-only, no-value field
enumeration (their docs/evidence/2026-09-10-npm-lane-field-resolution.json).
Exactly one field is present at the governed path. The 2026-09-09 change was
adopted from a coordination message and would have failed at the WP-0037-T03
rotation. The ungoverned second location is recorded as an explicit non-lane,
not deleted and not tidied away.

pep-stance coverage: published figures were stale by eight lanes (unknown
18->20, not_applicable 12->15) while resolved stayed at 3 — the denominator
moved, the classification did not. Caught by the test that asserts the published
block equals what report_coverage.py measures. tests/test_workload_join.py held
the same stale counts; both now measure the same populations.

rapp-qonto-keycape-client: blocker character updated — authority exists and is
unexercised by owner decision ("not yet", offer open), which is not the same as
no authority existing. Reopen triggers are events, never elapsed time.

flex-auth -> access-engine rename (WARDEN-IN-0003): access-engine added to the
policy-check lane's keywords so routing resolves under both names from today.
owner_repo deliberately not flipped — policy.py sends it as resource.system on
every /v1/check, and FLEX-DEC-2026-013 keeps runtime names as flex-auth.

layer declaration: INTENT.md says Staff, layer.yaml says staff, section 11 does
not say which governs. Neither changed; gate-house holds the ruling. Position in
docs/layer-declaration-precedence.md, wait in WARDEN-WP-0034-T06, and a comment
in layer.yaml telling the next session not to "fix" it — the divergence is the
evidence the ruling is made against.

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

@@ -14,7 +14,7 @@ planning_priority: P1
 depends_on_workplans:
   - WARDEN-WP-0030
 created: "2026-08-29"
-updated: "2026-09-05"
+updated: "2026-09-21"
 state_hub_workstream_id: "ae3ff76f-883d-5e2f-b6aa-144d61e8fdef"
 ---
 
@@ -231,6 +231,45 @@ cost, and issuance on this lane is too sparse (3 signature records across 79 day
 T05 stays `wait` on the remaining two: `ops-mason` (no stance map published) and
 `railiance-infra` (KRL distribution versus TTL expiry). Neither has replied.
 
+## Await gate-house's §11 precedence and case-sensitivity ruling
+
+```task
+id: WARDEN-WP-0034-T06
+status: wait
+priority: low
+```
+
+ops-warden declares `layer: Staff` in `INTENT.md` frontmatter and `layer: staff`
+in `layer.yaml`. §11 permits both forms and is silent on which governs when both
+exist and disagree, so two conformance runs over this repository can disagree
+while both follow the standard. Nine of nine repositories carrying both forms do
+the same thing (flex-auth `tools/survey_layer_declarations.go`, receipt
+`docs/evidence/2026-09-21-layer-declaration-survey.json`).
+
+**Waiting on gate-house for two rulings**: which form governs, and whether the §3
+vocabulary is case-sensitive. The custodian's estate-wide sweep adds a third that
+bears on it — §3's table capitalises and types engines `Engines` while §4's
+catalog rows type them `Engine`, so the standard disagrees with itself one level
+below B1.
+
+**Deliberately not acting.** Aligning the two files now means choosing an answer
+gate-house owns, and doing it in the one place §11 says another repository may
+not speak for us. It would also erase the evidence the ruling is being made
+against: the finding is visible because nine repositories exhibit it, and a
+repository that quietly normalises itself makes the estate read as more
+conformant than it is. Position recorded in
+`docs/layer-declaration-precedence.md`; both files carry a comment saying not to
+"fix" the divergence.
+
+**Done when:** gate-house rules, the non-governing file is changed to match in
+one commit, and a regression test asserts the two declarations agree so the next
+divergence is caught rather than surveyed.
+
+Raised by flex-auth's corrected B1 (message `719b3e9e`, 2026-09-21), which
+withdrew an earlier claim that the estate disagreed *across* repositories. The
+withdrawal matters to this task: the original finding would have had ops-warden
+changing a file to match an estate consensus that did not exist.
+
 ## Related
 
 Review 2026-09-05: reviewed the pending implementation and fixed the identity