Complete journal sovereignty - #113
Merged
Merged
Conversation
Preserve original accounts through stable provenance and append-only corrections. Add bounded versioned export and prove return-session retrieval plus zero managed residue across two real MCP processes.
blisspixel
marked this pull request as ready for review
July 27, 2026 16:32
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
Why
The 0.4 return-session exit requires player-owned continuity that can be inspected, corrected without rewriting history, exported, and erased with evidence. This completes that machine acceptance while leaving the learning cohort and independent review explicitly open.
Validation
scripts/check.ps1scripts/verify.ps1cargo test -p numinous-mcp --test stdio_session returning_journal_survives_two_processes_then_leaves_zero_managed_residue