fix: bounded decision checkpoint for blocked child dependencies #239
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/blocked-child-parent-reconciliation"
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?
Small source-only correction. A blocked child no longer prevents a one-shot host-owned, tool-free supervisor decision checkpoint. Receipt persists claim and global-hold/independent-next-proposed provenance; no proposed next becomes execution admission while child effects are uncertain. Active/ready/question children stay fenced; separate admitted mandates remain runnable. Existing fail-closed productive admission and child replay policy unchanged. Tick wait path also respects dependency fence.
Evidence: real Harness + ExecutionStore, actual temporary file edit then fake 503, unchanged ledger/no replay, restart, stale cancellation, pause, queue, expiry, budget and failed persistence. Negative control: 4 failures on canonical base. Typecheck/build passed, full serial 1350/1350, persistent exact-worktree plugin review passed zero findings. No live activation, old-task mutations, provider probes or GitOps operations. Evidence: /home/node/development-evidence/blocked-child-parent-reconciliation/RESULT.md.