Persist egress posture before durable resume - #408
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
1 participant
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.
What changed
A durable resume now records
screenshots_may_leave_box=truein the retained manifest and continuation authority before revalidation, a model call, or a resumed step can run.The regression stops the process before the first resumed step. It proves that the egress posture is already sticky, no backend action occurred, the external authority matches the new manifest, and the pending pause remains available.
Why
The cumulative audit update ran after resumed execution began. An early exit before that update could retain the earlier false value even though the resumed leg allowed model grounding. The audit record must describe the admitted data boundary even when execution stops early.
Checks