Repository navigation
Deliver bounded cached filename service and contained refresh/monitoring - #14
Merged
Merged
Conversation
added 4 commits
October 4, 2026 22:50
This was referenced Oct 5, 2026
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
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.
Agents can search private cached filename snapshots through a bounded JSON CLI and a resident private service, while separately contained refresh and monitoring preserve the accepted snapshot on failures. Native candidate acceleration keeps qualified warm queries within frozen latency/resource gates. Upstream GUI defaults remain intact.
Validation: fresh 19-target Meson pass; installed 91-case native acceptance; removed-root query traces and moved-parent race red/green proof; three installed million-name corpora and three replacement-overlap fixtures pass unchanged gates. File-searcher MCP integration is merged through CochranResearchGroup/file-searcher#21 and its installed runtime is qualified. Canonical evidence: docs/research/2026-10-04-monitor-install-acceptance.md and docs/research/2026-10-04-publication-review.md.
Publication uses a fresh fork-base commit after push protection caught credentials in a historical inherited-environment log. That line is redacted, original local evidence/history is preserved privately, and product bytes equal the qualified local source. No protection bypass, production-root indexing, default service activation or user registration change.
Refs #1, #2, #3, #4, #6, #7, #8, #9, #10, #11, #12, #13. Acceptance checkbox reconciliation follows verified CI/main custody; #5 real-root adoption remains a separate scope boundary.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.