Repository navigation
Unify CLI/MCP source and indexing metadata with partial search by default - #454
Merged
Merged
Conversation
jlitola
force-pushed
the
jlitola/search-commit-dates
branch
from
October 6, 2026 06:08
ad5491a to
d29541f
Compare
Carry backend commit timestamps through shared transport and lean metadata, and attach independent UTC dates to served and requested snapshot copy. Preserve read-now guidance and exact served locators; cover initial/status parity and navigation JSON, and document the backend rollout prerequisite.
Document that unified reads have no schema fallback and fail before backend support, while shared legacy navigation differs from public list and grep. Close review wording findings and remove a duplicate date assignment in snapshot tests.
Record the clean Claude full-delta review and precise whole-document read validation requirement. Preserve contract, evidence and rollout limits in permanent implementation docs, then remove the completed working plan.
Record the approved compact CLI/MCP row format, verified provenance contracts, minimal list selection, and focused acceptance checks. Include the clean internal and Claude plan review closure before implementation.
Render proved served snapshots and actual preparation work with shared compact wording. Preserve per-tool actions, raw content and JSON while selecting minimal list provenance and keeping browser tools free of service imports.
Verify pending n8n source calls on CLI and local MCP with minimal waits. Keep the package alias under actual work without repeating a tag that has no independent SHA, and update parallel search documentation to match the shared sections.
Select original repository and package identity fields for text provenance so unavailable targets retain their full Requested label. Keep detailed recovery fields and silent selection unchanged, and cover the compact wire projection and repository/package output.
Update the working checkpoint to reflect the implemented and independently verified identity regressions before external review.
Enable partial search by default while preserving explicit atomic requests. Keep indexed alternatives with preparation targets, retain healthy provenance for text, and close reviewed indexing explanation, empty-list guidance and wrapping defects.
jlitola
force-pushed
the
jlitola/search-commit-dates
branch
from
October 6, 2026 09:58
a8bde7e to
d7d09ce
Compare
Retain healthy zero-hit and repository-doc provenance for text while preserving compact JSON. Derive exact hit pins when resolution is absent, hide grep input numbers, and place read templates after matches. Align legacy assertions with the shared row grammar.
jlitola
changed the title
Omit normalized true from JSON query metadata while preserving explicit false. Exercise default omission through the actual builder and document the user-directed default exception.
Record final authenticated CLI and local MCP behavior after Keychain approval, scope legacy provenance wording accurately, and retire the reviewed working plan with its durable contracts retained in implementation documentation.
jlitola
marked this pull request as ready for review
October 6, 2026 11:21
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.
Search withheld ready documentation while repository code indexed, and commands described overlapping source/indexing facts differently. This change returns ready search subsets by default and gives CLI/MCP consistent Sources and Preparing rows with exact evidence attribution.
--no-allow-partial/allow_partial_results: false) and truthful JSON query echo.Validation:
bun test5,595 passed / 0 failed (234 files, 22,303 assertions); typecheck, CLI/MCP builds, all four source/built smoke commands, and public-package validation passed. Smoke modes validate unauthenticated handling/registration. Final authenticated dev CLI and local stdio MCP separately exercised all four tools on registry-confirmed, fresh Express versions 2.3.10 and 2.3.11: search and grep returned ready docs while code prepared, read reported INDEXING, and list returned no files yet with its independently known commit date. Grep had no input indices and placed its native read recipe after matches. Ready n8n search on both surfaces also confirmed resolution-free hit-pin provenance. Qualitative Claude workloads failed provider login before tool use, so no agent-quality result is claimed. CI passed on final HEAD b7dd6cd: Ubuntu/Windows tests, build checks, Bun and Node 20/22/24/26 compatibility, and MCP package validation. Main run. Publishing was skipped.Review: Luna implementation pre-flight, internal code review, and three Claude Opus 5.5 rounds completed. The last Claude round included its one fresh-context full-delta check and is clean after a minor documentation wording correction. The reviewer is retained for follow-up. The completed working plan is retired in this PR; durable contracts, evidence and rollout limits live in implementation docs. No major deferred development or required refactoring remains.
Rollout: backend date contracts were verified on dev; production schema support must be confirmed before client release or hosted adoption. GraphQL validates the full read/list query even when directives skip fields. Hosted adoption additionally needs an MCP package release, remote-mcp dependency update and deployment. This PR remains a draft; no merge or release is authorized.