Repository navigation
Start suspended Session recovery promptly after committed input - #41
Merged
Merged
Conversation
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.
A committed next-Turn input for an initialized, suspended managed Session could wait for the next five-second lifecycle scan before restore started. A best-effort hint now lets the existing maintenance loop observe eligible pending work sooner.
Keep the normal ticker, lifecycle gate, cursor, 32-allocation page bound, ownership fences and restore state machine. Coalesce hints and permit at most one extra scan per normal cycle, including under repeated pending-request retries. Running work, initial creation, terminal receipts and file operations keep their existing scheduling. The contributor guide documents the boundary.
The container acceptance wrapper also forwards the existing daemon URL supplied by the official-client fixture, matching direct-binary acceptance. The baseline wrapper omitted it, leaving execution disabled for required initial-input cases. Production enablement and container isolation are unchanged.
Validation:
These observations are not a latency SLA. Idle cadence is unchanged; under sustained eligible hints there is at most one extra bounded maintenance scan per normal cycle, plus up to two best-effort eligibility reads per pending submission. No CPU-percentage reduction is claimed.
Full
make check(76 Web cases), both required CI workflows including official-client/container acceptance, and fresh independent blind review passed on the final head. Design and acceptance record.