fix(pi): make watcher wake delivery durable - #396
Merged
Conversation
ruby-dlee
force-pushed
the
fm/pi-watch-durable-r4
branch
from
August 28, 2026 16:24
90f80be to
7331cd4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
Make Pi follow-up supervision continuously self-rearm across actionable exits and retry wake delivery until observably admitted, preserving direct captain input priority. Fix the asynchronous duplicate-admission race: mark each fire-and-forget handoff pending before calling Pi, never retry while asynchronous admission remains possible, and retry only after the concrete agent_settled non-admission boundary or synchronous caller failure. Executable coverage must prove delayed admission after the former retry timer remains exactly once, settlement without admission retries with one stable delivery identity, two consecutive wakes retain distinct identities and live successors, and direct input/image continuity, ownership stops, and cleanup remain intact. Keep validation bounded to the focused deterministic, exact installed-Pi, continuity, guard, lint, and isolated Pi 0.84.2 live proofs already established; skip unrelated repository-wide local test and lint pipeline steps. Continue through exact-head review, push, PR, and green CI without approving or skipping findings.
What Changed
Risk Assessment
Testing
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
✅ No issues found.
⏭️ **Test** - skipped
Step was skipped.
✅ **Document** - passed
✅ No issues found.
⏭️ **Lint** - skipped
Step was skipped.
✅ **Push** - passed
✅ No issues found.