diff --git a/workplans/STATE-WP-0095-historical-source-receiving.md b/workplans/STATE-WP-0095-historical-source-receiving.md index d9c7ec7..93f44cf 100644 --- a/workplans/STATE-WP-0095-historical-source-receiving.md +++ b/workplans/STATE-WP-0095-historical-source-receiving.md @@ -237,7 +237,7 @@ admission or new autonomy/cost grant is inferred. id: STATE-WP-0095-T07 status: wait priority: high -depends_on: [STATE-WP-0095-T06, RMGR-WP-0019-T06] +depends_on: [STATE-WP-0095-T06, RMGR-WP-0019-T06, STATE-WP-0095-T10] state_hub_task_id: "cfd1ea99-e75b-542e-a434-acefb62f3c7d" ``` @@ -357,3 +357,27 @@ Verify the actually loaded CLI checker hash after ordinary owner package refresh before any retry; capture legitimate source HEAD transitions rather than assume a static revision. T07 and T10 remain wait. No original parent preimage recovery, new runtime delivery or broader authority follows from this source repair. + + +T07 current-baseline client return, 2026-10-17: after the owner refreshed the +installed package and verified the actually loaded checker matched the reviewed +R6 source, ordinary Cluster deep consistency and fast projection passed. +Bindings synced 20/20, omitting the three frozen histories; all three parent +and 15 task CURRENT full-row hashes remained unchanged across +before-verified-client.json / after-verified-client.json. Unrelated staged brief +state was preserved. This proves the corrected installed client stage against +its fresh current baseline; earlier parent-hash failures remain retained +historical exceptions, not restored preimages or backfilled successes. + +T10 remains wait/needs_human for exact proposal +STATE-WP-0095-T10-frozen-bindings-guard-r1 revision 1, metadata +sha256:81d365926fc585a186955d8c98ee83501fd3cec12135b2256d71b46a75097932, +pending decision df703266-6719-4c04-ae1b-ba9afd3bca1c. The inspected candidate +image is main-c103cbf@sha256:4cc4ce17bbcdb1b66132d07c5b7b741f46df83124ef1c8403ffabdafba6993d1, +from runtime source c103cbf3c8bed5dba87a03e320595ddded9301a3. Image-only +server dry-run passed eight identities with only three image-field changes. +The exact proposal and recovery limits are retained in the Custodian dated +2026-10-17 guard-successor-review-r1 packet. No new API runtime is approved or +delivered by this source-only note; its later workplan commit does not change +the image's source pin. T09 stays done, T07/T10 stay wait pending reviewed API +delivery and explicit successor/current-baseline acceptance disposition.