Skip to content

grasp: ntig 0.2 preserves repository authority across explicit checkpoints - #16

Merged
FelineStateMachine merged 2 commits into
mainfrom
feat/ntig-0.2
Sep 4, 2026
Merged

FelineStateMachine merged 2 commits into
mainfrom
feat/ntig-0.2

Conversation

@FelineStateMachine

@FelineStateMachine FelineStateMachine commented Sep 4, 2026 •

Copy link
Copy Markdown
Owner

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

  • Pin the supplied 0.2.0 package, lockfile and complete source archive with SHA-256 provenance. A clean source rebuild has identical uncompressed tar contents; gzip bytes differ across toolchains.
  • Forward the accepted-state adapter's loadRefs, preserving authoritative HEAD and hidden PR filtering while migrated repositories advertise with two object GETs.
  • Cover checkpoint migration, historical correction retries, retained metadata and ambiguous-write reservations. Document format-specific limits and costs.

Existing and new roots remain format 1. No migration endpoint, scheduled work, pricing change, production deployment or production migration is included.

Testing Completed

  • Typecheck and 193 bindws tests passed locally and in CI.
  • Local bindws Worker + DO/R2: 16 general conformance tests passed, plus the explicitly GRASP-enabled stock Git test passed with zero skips (push/clone/fsck/incremental fetch/partial clone). The initial disabled-GRASP skip was detected and corrected.
  • Additional stock Git harness: nine checks across format 1 and isolated format 2.
  • Vendored-source checks: 132 backend tests, typecheck and builds passed.
  • Isolated DO/R2 repository reaches 260 transactions, replays old receipts after a cold reconstruction, and retains checkpoint metadata reservations.
  • Hidden PR correction replays after checkpointing and 130 later transactions without changing sequence or issuing PUTs. HTTP advertisement checks preserve HEAD/visibility with exactly two GETs.

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.

…d correction retries survive later commits, and retained metadata stays reserved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant