fix(dispatcher): recover bounded steering with durable exact decision consolidation #379
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/durable-decision-consolidation"
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?
Work in progress follow-up to live steering saturation: add explicit authenticated parent consolidation of applied working directives with exact durable audit, no silent eviction or raised lifetime cap. Monotonic revisions fence stale assessments independent of active window length. Archived IDs remain exactly idempotent after reload. Pending/manual pause/stop/ownership/unknown effects preserved. Core-native bounded maintenance tool is automatically exposed with dispatcher, no operator config change. Full suite at initial head 2083 passed / 1 existing skip; typecheck/build pass. Adding same-execution independently admitted follow-up work for explicit parent amendments so new source repair cannot remain stranded behind an unrelated saved live-verification step. Not ready to merge until final combined regression/full CI.
FINAL combined implementation ready: integrated current main #378 normally; local full suite 2084 passed / 1 existing skip / zero failures, typecheck/build/diff check pass. Exact final head
11e16ab705full-validation succeeded in 2m27s after the superseded head finished. Includes typed explicit same-execution followUp in consolidated parent context, attached once at durable assessment boundary and independently admitted by the existing ready-step validator; genuine old hold remains OPEN. Tests prove source publication is not repeated, no follow-up effect without independent readiness, repeated wake idempotency, >32 lifetime revisions with bounded active context, exact archived retry/conflict receipts, archive-before-ledger crash, claim/unsafe intent/manual pause/pending/foreign-worker guards and typed native tool contract. No new operator settings, second writer, ledger editing or authority bypass.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.