Repository navigation
grasp: owners inspect retained Git storage under shared admission - #20
Merged
Merged
Conversation
… while nested work keeps its owner
… source and package provenance
…ut changing stored objects
…ve admission without promising collection
FelineStateMachine
force-pushed
the
feat/grasp-inventory-admission
branch
from
September 4, 2026 23:13
2e07936 to
379866f
Compare
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
Quota reservations alone cannot explain how much Git storage belongs to the current root versus retained metadata. The coordination proof in #19 also showed that an alarm could await Git storage while an unrelated event changed repository authority.
Change
gitstorage(repositoryOwnerHex, identifier)method reports physical, current-root, unreferenced and unknown objects by class, alongside reservations and operation counts. It accepts no arbitrary prefix or caller-supplied limits.The 260-transaction fixtures reproduce the earlier physical/current totals: 2,147,926/144,084 bytes for growing refs and 512,431/136,809 for fixed refs. Each scan uses 349 GETs and one LIST, about $0.00013 in R2 request units before allowances/rounding, excluding execution and SQL. Counts are diagnostics, not billing meters. There is no new billing rate or separate inventory fee; existing activity and storage accounting still applies. No storage reclamation, root migration, collection or deployment occurs. Retained bytes remain on the existing storage meter; format-1 transaction limits remain unchanged.
The admission owner is local to a live instance. It does not establish crash recovery or collection safety across R2 clients.
Testing Completed
Responsible AI disclosure
Implementation, tests, documentation and review were assisted by Codex, including parallel code and cost reviews.