docs(interactive): retain native worker recovery evidence - #1158
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.
Two native workers remained running after the coordinator received SIGKILL.
A separate process reattached their exact persisted identities and matched all 372 original output frames by sequence and SHA-256.
Fresh control stopped one worker while its sibling remained running, then stopped the sibling.
Both sandbox deletions were verified.
Retains the executed scripts, journals, preparation receipts, frame hashes, process outcomes, and the failed first attempt.
The evidence distinguishes attachment recovery from resumed scheduling and Braid restart.
Issue #773 remains open for the untested acceptance criteria, including local Bridge and expiry behavior.
Validation: independent script and record review, secret scan, journal/summary reconciliation, and checked cleanup receipts.
No runtime behavior or public package contract changes.