coulomb/repo-manager
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Qualify Cluster preservation wait with verified client and API gate

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1468b-63fa-7710-85dc-8f2e16b3ebfa
This commit is contained in:
tegwick 2026-10-17 02:39:42 +02:00
parent 7c15c0ea48
commit 1dacdd4a31
1 changed files with 29 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

30
workplans/RMGR-WP-0019-historical-source-admission.md
View file

@ -199,7 +199,8 @@ No direct API patch, history rename or bypass substitutes for this gate.
id: RMGR-WP-0019-T06
status: wait
priority: high
depends_on: [RMGR-WP-0019-T05]
depends_on: [RMGR-WP-0019-T05, STATE-WP-0095-T10]
blocking_reason: "Await State Hub T10 founder approval, delivered API guard verification and explicit current-baseline/historical-exception disposition; original parent hashes are not restored."
state_hub_task_id: "4d1675b6-f49f-5b01-8d76-bbf2030d1b34"
```
@ -237,6 +238,33 @@ the reviewed exact-frozen binding guard, regression coverage and a verified
recovery/preservation disposition. No source or native gate is promoted by the
successful publication alone; no TLS or credential-custody acceptance follows.
Verified installed-client successor, 2026-10-17: after verifying the installed
R6 checker module rather than assuming canonical source was loaded, the full
normal Cluster maintenance pipeline preserved all 18 CURRENT historical row
hashes. It synced 20/20 ordinary bindings while omitting the three exact frozen
histories. Cluster HEAD remained 6ae3f847c83da3402883453ee7110457bfb2d0d6;
the owner's original staged brief and dirty WORK-RECORDS content were preserved.
Passing CURRENT before/after snapshots are retained under the Custodian packet
receiver-rollout-r4/before-verified-client.json and after-verified-client.json;
verified-loaded-client.json, verified-client-cluster-consistency.json and
verified-client-cluster-projection.json retain the actual client/pipeline proof.
This new baseline pass does not restore or replace the earlier failed three
parent comparisons; those failures and unavailable original preimages remain.
The new API guard artifact c103cbf3c8bed5dba87a03e320595ddded9301a3 at
image digest sha256:4cc4ce17bbcdb1b66132d07c5b7b741f46df83124ef1c8403ffabdafba6993d1
has image-only server dry-run proof, not delivered-runtime acceptance. T06
therefore also depends on STATE-WP-0095-T10. Founder decision
df703266-6719-4c04-ae1b-ba9afd3bca1c remains pending for exact proposal
STATE-WP-0095-T10-frozen-bindings-guard-r1 revision 1, metadata SHA256
81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932, in
Custodian docs/changes/netkingdom-target-2026-10-17/guard-successor-review-r1/.
That decision includes the proposed CURRENT-baseline acceptance with the
earlier mismatch retained as an exception; no baseline disposition is inferred
here. Await its approved scope and verified owner return before T06 closes.
T05 stays done; no runtime activation, guessed database restoration, worker
wakeup, TLS recovery or native private-admission acceptance follows.
## Receiver-first registrar source follow-through, 2026-10-17