fix(storage): declare the v44 index delta and gate schema-versioning by default

[Sinity]

Summary

An index schema bump merged without its delta declaration, the live archive silently fell back to full raw replay, and the repo CLI could not read it at all. The check that catches this already existed and ran nowhere. This declares the missing delta, moves the check into the gating path, and corrects the comment that made the cost look unavoidable. It also lands a tracker pass correcting stale bead state found while diagnosing it.

Problem

index_fast_forward_plan(43, 44) returned None, so archive_tiers/bootstrap.py fell through to full rebuild and every repo-CLI query against the live v43 archive failed:

$ polylogue --json find 'repo:polylogue'
Error: unexpected error: OperationalError: no such column: s.title_ref

devtools lab policy schema-versioning reported the violation correctly and continuously:

undeclared index schema deltas found: 1
Index fast-forward declaration drift:  missing: [44]

It is appended inside if lab: at devtools/verify.py. Default devtools verify does not run it; verify --quick (pre-push) does not run it; the CI lint job runs render all --check, verify public-claims and ruff, not this. Three other policies behind the same gate are also currently red (demo-tour-freshness, backlog-hygiene, bead-graph) — tracked in polylogue-ze5i.

Solution

Declare index v44 as SEMANTIC_REPARSE. v44 adds sessions.title_ref / title_confidence (polylogue-ih67, #3378). The DDL surface is two nullable columns on an 18,871-row table — trivially clone-safe — but the values come from the v44 Codex title resolver, affecting 3,201 of 18,871 sessions (100% of codex-session). A shape-only fast-forward would leave those NULL where a cold rebuild populates them, and that divergence must not be silently promoted.

DerivedDeltaClass has no class for "clone-safe shape, values via bounded targeted reprocess", so SEMANTIC_REPARSE is the truthful classification today. Operational behaviour is unchanged — full rebuild is what already happens. polylogue-9rw0.1 owns extending the vocabulary so this delta becomes a shape fast-forward plus a Codex-scoped reprocess.

Gate the policy by default — devtools/verify.py default step list plus the CI lint job. Static, archive-independent, measured at 0.63s.

Rewrite the stale comment above INDEX_SCHEMA_VERSION, which claimed index.db has no migration chain and that a stale generation needs ops reset --index. It predates the declared fast-forward mechanism and is the direct reason the rebuild cost was mistaken for unavoidable. (archive_tiers/embeddings.py:19-22 makes the same claim and is left alone — it is accurate, that tier has no declarations.)

Verification

devtools verify --quick                     exit 0  (58.03s, 18 steps)
devtools lab policy schema-versioning       exit 0  "Schema evolution policy intact"

Anti-vacuity — the gate fails on a real violation, not just passes on a clean tree:

INDEX_SCHEMA_VERSION -> 45 (undeclared)     exit 1  "undeclared index schema deltas found: 1 / missing: [45]"
reverted to 44                              exit 0

Tracker changes in this commit

Nine beads filed, each with bounds measured in this session rather than a single noticed instance:

bead	measured bound
9rw0.1	delta-class vocabulary gap; v44 witness, 3,201/18,871 sessions
ze5i	4 of 10 lab policies red behind --lab
cijx.1	repo identity: 106 distinct repo_ids for one repo (sinex 28, sinnix 31)
cuxz.4	tool_result outcome NULL undifferentiated: 1,333,201 rows; codex 86%, claude-code 53%, claude-ai 0%
cuxz.5	26,188 unpaired tool_use blocks
4ts.10	session_links.status/.method empty on 9,179 of 9,179 rows
b5l.3	fast-forward sprawl: 5 modules, 2,713 lines, one per-version fork
5xng	paste_spans = 4 rows / 3 sessions across 5,042,564 blocks
1hal	backlog-hygiene X2: 5 of 6 findings are false positives

Corrections to existing beads:

• m3p9 headline was 12× stale — "79% / 65,946 sessions" re-measured to 5.9% / 1,117; the original figure predated the hook de-inflation that moved the denominator 4.5×. Retitled and re-scoped.
• ih67 — 3,101 → 3,201, and it is 100% of the Codex population, not a subset.
• hjpx.2 — raw-frontier 15,264 → 2,593 and draining; the monotonic growth that justified hjpx's P0 escalation is not the current behaviour.
• z9gh AC7 bounded. It read "Every residual symptom is mapped to one class mechanism" — an unbounded quantifier with no enumeration procedure, making the bead unclosable by construction and causing cold agents to report the P0 as long-horizon. Intent preserved; the set must now be enumerated from a stated snapshot. Snapshot figures refreshed (18,428 → 18,871 sessions, 4.85M → 5,042,564 blocks).
• yla8 / lkrc / hjpx — the standing "No live apply is authorized" note was reading as a permanent prohibition and is the direct cause of an ask-defer loop running since 2026-07-15. The single operator input that lifts it is now written out once on yla8, with the agent-side prerequisites that must be reported first. No authorization is asserted in this PR — the note makes the question answerable in a line.
• de2a / 623q / xikl — acceptance criteria added (all three were P1 with none). de2a carries a live writer-starvation baseline; xikl's "operator decision" was already made on 2026-07-19 and it appears in blocked-on-decision sweeps only because the phrase occurs in its text.
• Reference corrections on yla8, 1xc.14, yyvg.7 distinguishing agent session ids from bead ids.

Ref polylogue-9rw0, polylogue-ih67, polylogue-ze5i

Summary by CodeRabbit

• Bug Fixes
  • Updated schema-version validation so version 44 changes are correctly recognized during verification.
  • Ensured version 44 index updates rebuild/reprocess instead of taking an ineligible fast-forward path.
• Documentation
  • Clarified version 44 schema changes (including session title fields) and when rebuild behavior applies.
• Chores
  • Enhanced CI lint verification with an additional devtools policy/schema-versioning step.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ad1d2fdd-b813-4b13-8ce6-652352e9ab71

📥 Commits

Reviewing files that changed from the base of the PR and between 21695bb and db924e7.

📒 Files selected for processing (2)

• .beads/issues.jsonl
• devtools/verify.py

💤 Files with no reviewable changes (1)

• devtools/verify.py

---

📝 Walkthrough

Walkthrough

The change declares SQLite index schema version 44 as requiring semantic reparse, updates its versioning documentation, and runs the schema-versioning policy check in general verification and CI lint.

Changes

Schema versioning lifecycle

Layer / File(s)	Summary
Declare schema version 44 lifecycle behavior polylogue/storage/sqlite/archive_tiers/index.py, polylogue/storage/sqlite/lifecycle.py	Documents the v44 schema change and classifies it as a semantic-reparse delta with no SQL fast-forward operations.
Run schema-versioning checks in verification devtools/verify.py, .github/workflows/ci.yml	Moves the schema-versioning gate outside the lab-only block and adds its command to the lint job.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Sinity/polylogue#2788: Extends index fast-forward lifecycle declarations and uses schema-versioning policy checks.
• Sinity/polylogue#3319: Adds another INDEX_DELTA_DECLARATIONS entry for a different schema version.
• Sinity/polylogue#3322: Adjusts tests to remain stable when new lifecycle declarations are added.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: declaring v44 and moving schema-versioning into the default path.
Description check	✅ Passed	The PR description covers Summary, Problem, Solution, and Verification with enough detail; missing template sections appear non-critical here.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/chore/tracker-accuracy-and-derived-transition-gate

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@devtools/verify.py`:
- Around line 1775-1781: Move the “lab policy schema-versioning” verification
step out of the general not-commit branch and into the later `if not quick and
not commit` block within `build_verify_steps`, preserving its existing command
and behavior for non-quick, non-commit runs while excluding it from quick
verification.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 374c4be5-b24e-4c72-a3bc-9baf80225de4

📥 Commits

Reviewing files that changed from the base of the PR and between a57b9ca and 21695bb.

📒 Files selected for processing (5)

• .beads/issues.jsonl
• .github/workflows/ci.yml
• devtools/verify.py
• polylogue/storage/sqlite/archive_tiers/index.py
• polylogue/storage/sqlite/lifecycle.py

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Keep this check out of quick verification.

Because the step is added under if not commit, build_verify_steps(quick=True, commit=False) still runs it. The stated scope is non-quick, non-commit; append it inside the later if not quick and not commit block, or explicitly confirm that quick mode should include this policy.

Proposed placement

-                ("lab policy schema-versioning", _devtools_cmd("lab policy schema-versioning")),
             ]
         )

     if not quick and not commit:
+        steps.append(("lab policy schema-versioning", _devtools_cmd("lab policy schema-versioning")))

Also applies to: 1860-1860

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@devtools/verify.py` around lines 1775 - 1781, Move the “lab policy
schema-versioning” verification step out of the general not-commit branch and
into the later `if not quick and not commit` block within `build_verify_steps`,
preserving its existing command and behavior for non-quick, non-commit runs
while excluding it from quick verification.