Record failed runtime trial and reviewed verification proposal (4/4)

docs/netkingdom-target-implementation.md

@@ -982,3 +982,64 @@ Evidence: dated 17 October `native-identity-r1`, `native-registration-r1`,
 `consumer-outage-owner-followthrough-r1/verified-bindings.json`,
 `native-source-publication-r1/verified-bindings.json`, and
 `storage-share-tls-r1/source-history-followthrough-r2.json`.
+
+## Partial runtime installation and pending verification, 2026-10-17
+
+Founder approval `b6abb6ab-b182-4b4f-9f84-79ddc5ad91f3` authorized exact
+installation proposal revision 2, SHA256
+`44b17589c323e1a966caf6c1b1def123092ee289b929c8ea014bc84109103b1d`.
+It ran once and installed the inactive runtime with complete native digest
+`f59959b605a51abd2901becde14e7abd852c2bd3f848004b51d250d1cb81af6d`.
+The offline rehearsal then failed with `phase_receipt_unavailable`; its process
+supervisor reported `leader_left_descendants`, followed by positive process
+quiescence. Independent readback verified the complete installed digest and
+absence of owned staging. This is a failed trial with
+a verified partial installation, not launcher acceptance or a closed target gate.
+
+A local counterexample reproduces a zombie-classification defect in the frozen
+revision 2 source. The native failure's cause remains unproven because that run
+did not retain its process trace. Verification-only revision 3 repairs the
+demonstrated defect and retains a durable public process receipt before cleanup.
+Its original three launcher checks remain required. Root source review, all
+18 candidate file pins, 29 frozen revision 2 file pins and five focused local
+process/cleanup checks passed. These local checks establish no native acceptance.
+
+The founder approved exact revision 3, SHA256
+`7d5741abc7da042d4de6cd36437801309b844760f606b3145d615fd75d6b2d30`,
+under decision `bec667cc-15ea-4f87-ae16-111f08562e48`. Its fresh read-only
+preflight refused CPU headroom (99.25% busy; limit 85%) before any remote write
+or launcher call. No revision 3 execution receipt exists and no automatic poll
+or retry follows. The approved helper has no installation or runtime archive
+transfer path. Infrastructure cost and interruption/recovery loss in EUR remain
+unknown. No model call, credential/profile/queue change, Custodian migration,
+autopilot grant or native target gate closure follows from either preparation.
+
+Evidence: `native-runtime-install-r2/execution-receipt.json`,
+`native-runtime-install-review-r2/installed-partial-verification.json`,
+`native-runtime-install-r3/FINAL-PROPOSAL.md`, and
+`native-runtime-install-review-r3/{root-review,approval-decision,approved-preflight}.json`
+in the dated 17 October packet.
+
+## KEY-WP-0039 finalization review, 2026-10-17
+
+The user-directed review confirms its source deliverables remain complete:
+T01 and T03 are done, and all 14 reviewed executable/test/producer-decision
+pins plus three Platform source pins still match. The later workplan narrative
+is not a change to those reviewed executables. Existing source acceptance,
+registration go `caafe4be-4f68-47b4-9567-316d47b94992` and the standing attended
+rule remain valid; no new helper protocol or repeated registration approval is
+needed.
+
+The parent cannot finish yet. T02 requires actual negative-claim/expiry refusals,
+a committed value-free receipt and removal of the probe clients. No such native
+receipt was found in the bounded owner-source search. KEY-WP-0038-T02/T03 remain
+open prerequisites, and Platform's 17 October return still identifies the existing
+coding-client custody proposal as unadmitted. Node route, live role/plugin/leeway
+and private custody facts remain its existing attended owner obligations.
+
+The remaining sequence is the existing Forgejo registration/claims proof,
+admission of the existing coding-client proposal and owner readiness returns,
+then the attended negative/revoke/cleanup proof. KEY39 stays active with T02
+waiting. Infrastructure source-review approval supplies no missing native proof.
+Evidence: `key39-infra-finalization-r1/assessment.json` and its linked owner
+reviews in the dated 17 October packet.