fix(memory-probe): accept piri provider in mempalace refresh/install status - #947
Merged
Conversation
…status Follow-up to #946. ccc_memory_probe.mempalace_refresh_probe and the Termux install-metadata validator only accepted provider in {claude, codex}, so on a Piri node with nunchi+MemPalace enabled the refresh status (provider=piri, state=ok) was rejected as refresh-invalid and flagged refresh-provider — making `memory cache` a perpetual 경고 even though the lane works. Add piri to both provider allow-sets. ccc-memory.test.sh gains a piri provider case in the refresh-probe valid-states matrix.
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.
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.
Follow-up to #946.
Why
While enabling nunchi+MemPalace on a live Piri node (jingun), `ccc-doctor` still reported `memory cache` 경고 (`mempalace=degraded`) with reasons `refresh-invalid` + `refresh-provider`, even though `mempalace-refresh.sh piri` ran cleanly (`state=ok`, `provider=piri`).
Root cause: `ccc_memory_probe` validated the refresh-status `provider` field against `{claude, codex}` only — so a valid Piri refresh record was rejected as `invalid`, and its `piri` provider was flagged as a provider mismatch. The Termux install-metadata validator had the same gap.
This made `memory cache` a perpetual 경고 on every Piri node with nunchi+MemPalace, defeating the goal of #946.
What
Verification
Sibling change to #946 (no bridge runtime change).