docs: update published Warden original-context checkpoint

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1468b-63fa-7710-85dc-8f2e16b3ebfa

workplans/NK-WP-0048-security-case-types.md

@@ -783,13 +783,15 @@ described in T31.
 Owner: NetKingdom for registration state, with Warden owning kernel evidence
 admission. T22 records the completed source review and exact existing-seam gaps;
 T15 retains implementation and authenticated restart/lost-receipt acceptance.
-Next action: identify the actual owner publisher/authenticator and bounded
-original-attempt readback contract, and obtain Warden's reviewed original-intent
-lookup/context interface through existing WARDEN-WP-0044-T03. The current Journal
-retains attempt identity in historical rows but only hashes evidence references;
-load drops that context and reconcile passes a fresh attempt to the callback.
-The adapter's original payload and creation record remain process-local. Neither
-that journal nor a current matching registry entry reconstructs creation authority.
+Next action: select and admit the actual owner publisher/authenticator and bounded
+original-attempt readback contract for the merged holder/observe adapter seam.
+Warden's original-intent persistence/interface (`a45cf475`) and additive validation
+(`117fec9241e7b985dfb187b992e173d0a5dc3700`) are now published and projected.
+The local Journal retains admitted nonsecret original context, validates original
+actor/attempt and metadata linkage to the original running receipt, and supplies
+it separately from the new reconciliation attempt. This local consistency is not
+independent original-holder authorization or creation provenance; neither the
+journal nor a current matching registry entry reconstructs creation authority.
 
 The owner contract must bind the original Invocation, case/type/descriptor/catalog/
 acceptance pins, source, principal and admitted tenant/realm provenance, separately
@@ -804,9 +806,10 @@ Completion requires restart/lost-receipt fixtures against the selected actual ow
 contract: independently authenticated original created-only provenance, original
 exact client entry and unchanged current postcreation UID/resourceVersion before
 any undo, with wrong attempt/case/source/principal and unavailable-holder refusals.
-The T13 adapter deliberately refuses post-restart rollback and installs no
-reconciliation callback. Existing source review, JSON receipts and synthetic
-trust do not satisfy native holder acceptance or authorize attended recovery.
+The merged T13 adapter exposes reconciliation only through paired injected
+holder/observe capabilities and still refuses post-restart rollback. Existing
+source review, JSON receipts and synthetic trust do not satisfy independent
+holder authorization/provenance or native admission, or authorize attended recovery.
 Exact remaining owner facts: Custodian native-registration-r1/original-attempt-review.json.
 
 2026-10-17 check (net-kingdom-worker): Warden's original-intent lookup interface
@@ -817,6 +820,16 @@ T16's decomposition under the same token budget. Remains todo, gated on Warden
 publishing the reviewed lookup/context interface and on owner selection of the
 authenticated original-attempt holder.
 
+2026-10-17 current-source correction: the earlier same-day `d97652a` lookup
+checkpoint and T31 adapter-next-action note above are historical and superseded
+by the published Warden interface/validation and merged `061461e` adapter seam.
+The 54 focused Warden checks establish source behavior only. Current admission
+leaves tenant/realm empty; no admitted tenant/realm provenance is inferred.
+T15 remains wait for actual independently authenticated owner-holder/readback
+selection, independent review of the changed adapter, and native restart/lost-
+receipt acceptance. Existing task metadata, owner gates and historical reviews
+are unchanged.
+
 ## T16 — Select and review the actual machine descriptor composition
 
 ```task