feat(memory): inherit private legacy context in Piri - #957
Merged
Conversation
jinon86
approved these changes
Aug 5, 2026
jinon86
left a comment
jinon86
left a comment
Contributor
There was a problem hiding this comment.
Approved after explicit operator authorization using the Seoseo-held jinon86 credential for this exact head.
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
2 participants
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.
Summary\n\n- inherit pre-scope Claude and Hermes MEMORY/USER content only into an opaque private audience\n- fall back to legacy Wiki and Honcho caches for the first private bootstrap, then refresh route-local caches\n- allow the legacy nunchi snapshot only through an exact private compatibility route\n- increase only the private Piri bootstrap budget so all bounded legacy blocks survive materialization\n- keep shared/group audiences fail-closed with no legacy Wiki or nunchi context\n\n## Safety\n\n- existing memory files and databases remain read-only and are not copied or merged\n- private route validation requires the canonical legacy state and nunchi paths\n- caller-supplied NUNCHI_SNAPSHOT cannot override the canonical private legacy snapshot\n- public routes keep Wiki disabled and cannot enable node-global nunchi\n\n## Validation\n\n- ruff check: passed\n- focused memory materializer tests: passed\n- audience/Piri runtime tests: 36 passed, 6 subtests passed\n- memory hook contract: 35 passed; one pre-existing Termux timing threshold is host-sensitive\n- bash syntax and git diff checks: passed\n\nThis is the private legacy-read compatibility slice related to #950. Scope-preserving collection of new audience transcripts remains tracked there.