Allocate sitting-requester CCR pair and record operator gates.

CCR-2026-0026/0027 are proposed source only: new KV path, no apply,
and no widening of 0024/0025. Record destroy-after-confirm for the
npm duplicate, coordinated 0018 disablement, blocked historical
NetKingdom paths, and no Forgejo retention cutover.

Assistant: grok
Assistant-Session: 01a0a23b-3bf0-7341-b4e5-9dc05f72573a

workplans/RPF-WP-0027-keycape-live-secret-exposure-recovery.md

@@ -9,7 +9,7 @@ flavor: implementation
 owner: codex
 topic_slug: railiance
 created: "2026-08-23"
-updated: "2026-09-05"
+updated: "2026-09-15"
 related:
   - KEY-WP-0011
 origin: routed
@@ -137,6 +137,11 @@ publication, update `docs/net-kingdom-credential-custody-contract.md`, ask
 ops-warden to refresh lane resolvability, and pass only protected inputs to
 NetKingdom's minimal resolver reconciliation flow.
 
+**Operator decision, 2026-09-15:** leave both historical resolver lanes blocked.
+Do not invent mount/path/field names. The KeyCape factor service lane from
+RPF-WP-0040 remains the separate active custody; it does not close these
+incident lanes.
+
 ## Portfolio review — 2026-09-05
 
 INTENT binding: secure custody and incident closure. The goal above is historical;