Repository navigation
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.
An isolated session snapshot could retain its source workspace safety root and workflow-tool owner while losing its effective budget and Scout submission settings. The branch could reject normal file operations, charge or close the source session's authored work, stop at a soft allowance treated as a hard cap, or finish without the required structured submission.
Rebind the two existing session-owned workflow tools through the copy memo, relocate built-in workspace safety bindings, and preserve hard authorization separately from the current soft allowance. Retain the budget decision callback, cleanup and history settings, and Scout enforcement through existing constructors. Autosave and external event observation keep the documented snapshot behavior. Extra allowed roots and existing command restrictions remain in effect.
All 12 new regression cases failed on the base commit and passed on this branch. Related snapshot, restore, authored-workflow and cleanup tests passed all 156 cases. Actual child processes verify that closing either session ends its own work while the other remains alive. Repository Ruff, import constraints and dependency checks passed.
The production change stays in the existing session composition module, which owns construction, restoration and binding of concrete runtime collaborators.