# sgit-ai 0.26.1.dev0: pack index verify 120 times faster, and a new pack vault's gate fixed, cli.sgit.ai

> Pre-release of 27 October 2026, from the CLI's dev at b9c8baac. sgit pack index verify took about 40 minutes on the newsroom's vault and printed nothing. It is now about 300 times faster, prints a line per pack, and --last N checks only the newest packs. A new pack vault is gated at what its features need, 0.24.0, not at the creating build's version, which fixes R3-2. sgit update gains --stable. Reviewed by cli.build. 4,752 tests pass. On 8,000 files and 6 packs, verify went from 82.9 s on 0.26.0 to 0.69 s. A new pack vault reads min_client 0.24.0. Maturity good. R3-1 is still open.

*Source: <https://cli.sgit.ai/builds/0-26-1.html> · generated from the same content as the page, so the two cannot drift.*

---
# sgit-ai 0.26.1.dev0

```text
┌─ sgit-ai 0.26.1.dev0 ── pre-release ── 27 Oct 2026, 23:51 UTC ──────────────────
│ tag v0.26.1 = b9c8baac (dev) · PyPI package == tag, but for the version file
│ fixed   pack index verify ~300x (field report) · new pack vault gate = 0.24.0
│ tests   4,752 unit+security ✓ · G1 ✓ G2 ✓ · verify 82.9 s → 0.69 s
│ maturity  ########--  good
└──────────────────────────────────────────────────────────────────────────────────
```

## What is new {#new}

- **`sgit pack index verify` is about 300 times faster.**
  - **What was slow:** for every `folder:` member it re-flattened the head, and every member read rebuilt the header's member table.
  - **On the newsroom's 79,465-file vault:** about 57 s a pack, and about 40 minutes in all, with no output.
  - **The CLI team's measurement:** 1,002 s → 3.5 s on 24,000 files and 9 packs.
- **One progress line per pack,** flushed as it goes, so a pipe or a file shows progress too: `3/9 commits 4b84cea48e03 — ok in 0.8s`.
- **`sgit pack index verify --last N`** checks only the N newest index packs, so "did my last push's index match?" costs under a second.
- **`sgit pack index stats`** explains its generation line: this clone's memo, which is 0 on a clone that only reads.
- **A new pack vault's gate is what its features need, 0.24.0,** not the creating build's version. `init --packs` and `pack import` used to write their own version, so a vault made by an agent on a dev build refused every agent on the release. This is [R3-2](../research/pack-indexes-review-round-3.md#r3-2), fixed. Existing vaults keep their gate; `sgit vault format --min-client` lowers it.
- **`sgit update --stable` and `--pre`** choose between the newest release and the newest build.

## Review by cli.build {#review}

**Verdict: good.** Both fixes hold.

```text
┌─ checks on the PyPI package 0.26.1.dev0 ──────────────────────────────────────────
│ ✓ G1  init --packs: min_client = 0.24.0          (0.26.0 wrote 0.26.0)
│ ✓ G2  verify, all packs and --last 1: ok
│       verify, 8,000 files, 6 packs:   0.26.0  82.89 s   →   0.26.1  0.69 s  (120x)
│ ✗     R3-1 unchanged: compaction of a 0.25.0 vault, then verify: 64 bad offsets
└────────────────────────────────────────────────────────────────────────────────────
```

**R3-1** is unchanged in every build up to 0.26.6. The faster `verify` now reports it in seconds instead of minutes. The fix proposed in [round 3](../research/pack-indexes-review-round-3.md#r3-1) still stands: archive the original bytes, or let `verify` call such an index stale.

*Scripts: `check_build.py`, `verify_speed.py 8000 6`. All builds: [the builds page](../builds/index.md).*

---

*[Site index for agents](../llms.txt) · [HTML version](https://cli.sgit.ai/builds/0-26-1.html)*