fix(dispatcher): stop old-step corrections starving independently ready follow-ups #382
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/retained-amendment-readiness"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Live follow-up to #379: parent consolidation now works (15 exact originals archived, replacement revision16, typed source followUp attached to SAME execution). However the old live step reviewer keeps returning continue/read-only configuration corrections. Readiness selection previously ran only after blocked/waiting, so the old-step continuation became a global scheduling veto and starved the explicit source amendment.
Reuse the exact existing independent ready-step gate after a current-step continue when an explicit follow-up exists. No default execution, no skipped authority/review; readiness may refuse. If admitted, atomically settle the old intent with retained report and reordered checkpoint BEFORE any new worker. Original hold/correction budget/session preserved, same execution/stable intent IDs, no duplicate publication or writer.
Failing-before reproducer against merged #379: repair runs0 times rather than1. Pass-after proves publication + original live report + admitted source repair each run once, then genuine live hold remains open. Negative control proves refusal does not admit repair and preserves durable correction pacing. Full suite2086 pass /1existing skip /zero fail; typecheck/build/diff-check pass. Await normal exact-head CI before non-force merge and activation.
COMBINED LIVE AND FLEET PROOF COMPLETE for generic orchestration fixes #375/#379/#382/#383. Published release0.1.269 revision73418505750996a83bac175740551deb0c529331 (or verified descendant) activated on all THIRTEEN current active installations, including newly present Grace/Minerva. Each installed artifact passed 40 bounded synthetic recovery transfers, exact correlation preservation and guard checks, plus active monotonic decision revision>32, same-owner followUp tool/module and oversized readiness projection with unchanged authority/candidate. Serving API revision/authenticated identity checked where configured; configured API-disabled Matrix installations retained that policy and actual process-entry identity was verified. No new Slack/API/credentials/admin rights copied or enabled. Native graceful owner updates; Kubernetes normal GitOps PR merges and Recreate/checkpoint recovery.
Actual local original owner559dbf4d recovered from its poisoned in-memory session with old transcripts preserved. Parent used supported consolidation: 15 exact old records archived, revision16 accepted, followUp attached. Readiness probe proved former captured-evidence budget prevented all backend calls; new projection + first-safe-action policy selects exact candidate5 on configured actual reviewer, refuses missing-approval control. Production order became[0,1,3,4,2], original same owner ran18 real read/bash calls, independently completed source followUp using existing integrated commit7602e575a53cb1ed3599812e4e5e091003cc3e84 and exact-head green compatibility run141 (Core2084pass/1skip, Plugins139pass). No duplicate writer/push/merge performed by maintenance. Subsequent original-parent coordination completed another followUp; original live hold stays open, not falsely marked complete.
Final Core#383 local suite2095pass/1existing skip/zero fail; typecheck/build and exact-head full CI green before regular non-force merge. Fleet evidence ~/.cache/hayate-maintenance/orchestration-fleet-269/summary.json, per-instance installed JSON, original-writer-progress.json and test/provider logs. Image/control/config receipts in the same directory. Separate Randy volume startup mitigation agent-randy-waterhouse#176 passed normal required CI and merged, preserving UID/GID/permissions, to avoid re-chowning >740k files on every unchanged PVC mount.