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
This branch has not been deployed
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.
Repository search provenance now shows independently known absolute UTC commit dates for the served snapshot and a different resolved requested commit. Dates stay attached to their own SHA; usable hits still lead to the exact served read, and existing conditional HEAD/exact-ref wait advice is unchanged.
The shared GraphQL selection, nullable parser, normalizer and lean projection now retain backend
committedAtvalues. Search and retained status share the same copy; JSON retains full known timestamps and omits unknown values. Existing shared read and legacy CLI navigation provenance also gain the metadata; public list/grep use separate queries. Permanent contract, examples and evidence are indocs/implementation/search-snapshot-presentation.md.Validation:
AUTH_REQUIRED.Not logged in); no qualitative quality or performance claim.Rollout: confirm production backend schema support before client release or hosted MCP adoption. An early rollout makes all read requests fail validation; search/status reach the existing fallback that drops target provenance. Historical date enrichment stays backend scope. No runtime fallback/backfill, metadata-only requests, version bumps, release or deployment are included. Both public artifacts carry pending minor impact.
Review: Internal preflight and fresh Claude Opus 5.5 loop clean after documentation/test cleanup. The same fresh-context final-check subagent covered the full delta; its last minor doc wording fix is applied. The completed plan was removed after review, with durable knowledge retained in implementation docs.
CI is green on
ad5491a: Pull Request build/test/compatibility run and MCP package validation. Linux/Windows tests, root/MCP builds, package artifact checks, built CLI/MCP smokes and Bun/Node 20/22/24/26 compatibility all pass. MCP publication and unlabeled agent-eval jobs are skipped as expected on this PR.Commits:
4b52bc6implementation;5b2ba65review closure;ad5491apermanent verification and completed-plan cleanup.