Repository navigation
grasp: ntig 0.2 preserves repository authority across explicit checkpoints - #16
Merged
Merged
Conversation
…pository roots stay in format 1
…d correction retries survive later commits, and retained metadata stays reserved
This was referenced Sep 4, 2026
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
ntig 0.2.0 supports explicit checkpoint migration and indexed historical receipts. Bindws needs the pinned upgrade and its ref-only read path without changing existing repository formats or bypassing signed state.
Change
loadRefs, preserving authoritative HEAD and hidden PR filtering while migrated repositories advertise with two object GETs.Existing and new roots remain format 1. No migration endpoint, scheduled work, pricing change, production deployment or production migration is included.
Testing Completed
Cost evidence: the growing-ref fixture retains 2,353,325 bytes across 986 keys at sequence 260, up from 42,094 bytes before migration at sequence 128. An old corrected PR HTTP retry uses 30 GETs / 59,569 bytes and zero PUTs. These are synthetic local measurements, not production CPU or invoice estimates. Tenant rates and allowances remain unchanged; retained metadata uses existing storage accounting.
Responsible AI disclosure
Codex implemented and reviewed this update with scoped subagents. Validation evidence comes from the commands and isolated fixtures above; production rollout and migration remain separate decisions.