Repository navigation
grasp: storage inventory separates current dependencies from retained bookkeeping - #18
Merged
Merged
Conversation
…te current dependencies from superseded metadata
…torage total is not a per-repository floor
…y cleanup can remove pending rows
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
The growing-tag benchmark retains about 2.15 MB, but that number does not distinguish current-format dependencies, superseded metadata and conservative quota reservations.
Change
The isolated checkpoint fixture now compares 260 transactions with one fixed ref against 260 growing refs. A read-only helper reconciles every paginated R2 key and size against the quota ledger, traverses current dependencies, verifies all historical receipt lookups and checks that the root remains unchanged.
The growing fixture contains 2,147,926 physical/reserved bytes: 144,084 current-format bytes and 2,003,842 superseded metadata bytes. The fixed-ref fixture contains 512,431 bytes, with 136,809 current-format bytes. Both have zero reservation slack. An untouched fixture uses zero Git-object bytes; its first commit uses 631 bytes. These are workload measurements, not a platform floor or permission to delete objects while readers or publishers remain active.
Fuel and cost documentation explains the categories. Runtime behavior, rates, receipt retention and production storage remain unchanged. Retained bookkeeping continues to count toward the tenant's existing file allowance; this change adds no production operations or wakes. README and landing copy remain accurate and already link the expanded fuel/cost documentation.
Stacks on #17; #16 and #17 retain their existing heads.
Testing Completed
Responsible AI disclosure
Codex authored the test and documentation changes, coordinated the backend comparison, and reviewed the storage interpretation with a second agent. Measurements and checks are reproducible from the documented npm command.