chore: neutralize team-internal identifiers on the public surface - #29
Merged
Merged
Conversation
An outside reader clones this repo without our workspace, our people, or our drive layout. Names in comments read as noise; a documented example command pointing at E:\Project cannot be copied and run by anyone but us. - comments and test fixtures use neutral placeholder names - example and fixture paths move off this machine's drive layout - the benchmark README's example command no longer hardcodes a local checkout Behaviour is unchanged: these are comments, fixture strings and doc examples. meta-gate (14 cases) and supersede-shrink (24 cases) both still pass. The published MCP server identifier chinatsu-memory is deliberately untouched -- renaming it would break existing user configs, so that one is a product naming call, not a cleanup. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 11, 2026
Merged
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.
Someone cloning this repo has none of our workspace, our people, or our drive layout. Names sitting in comments read as noise to them, and a documented example command pointing at
E:\Project\mneme\index.mjscannot be copied and run by anyone but us.What changed — comments, test fixtures and one doc example only:
Behaviour is unchanged.
meta-gate(14 cases) andsupersede-shrink(24 cases) both pass;memory-healthandencoding-damageneedTOKENMEM_DB_PATHand exit 2 the same way onmain.Deliberately not touched: the published MCP server identifier
chinatsu-memoryinadapters/codex-recovery-proxy/. Renaming it breaks existing user configs, so that is a product naming call rather than a cleanup — flagging it here rather than deciding it. The scan rules now carry it as an explicit exception so it stops tripping the guard on every push.Why now: a scan of all 7 public repos turned up 15 such spots (12 here, 3 in typeless-but-free). None of them are leaks — no credentials, no production topology — they are all the generalization half. Found while wiring up a daily scan from the private side, since the local push hook never sees merges done through the web UI or PRs from others.