Repository navigation
grasp: scoped reads and pending promotion reduce repeated Git reads - #17
Merged
Merged
Conversation
…ries finish interrupted publication
…nstruction without migrating repository roots
…e roots, writes and quota checks stay fresh
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.
Motivation
A historical Git retry repeatedly read immutable objects for authorization, WAL validation and promotion. The host fixture used 30 R2 GETs even with no relevant Nostr events pending. Sequential checkpoint construction also retained intermediate receipt-index nodes.
Change
This stacks on PR #16 without changing it. No production deployment/migration, new rates, wakes or garbage collection is included. New and existing repositories remain format 1 unless explicitly migrated separately.
Testing Completed
The read-session default bounds retained payload to 2 MiB / 512 entries, not total request memory. Git validation still runs; the measured I/O reduction is not a production CPU or margin estimate. Retained growing-ref manifests remain material. Tenant rates and allowances are unchanged.
Responsible AI disclosure
Codex implemented and reviewed the integration with scoped subagents. Commands and isolated fixtures supply the validation evidence; deployment and migration remain separate decisions.