Fix corpus reds: status readers, controlled reads, tier fixtures, retired tokens

[Sinity]

Summary

Eight more red classes from the 2026-09-03 corpus run, stacked on #4591.
Four are product defects; four are fixtures pinned to shapes the runtime
has moved past.

Problem and solution, per class

Status readers raised instead of reporting tier skew

#4485's open-time tier check reached the readers whose subject is a
tier's version. The workload probe's payload carries user_version and
version_status fields; metrics is supposed to emit
schema_mismatch:index as a blocker series; the convergence-debt summary
has an error field for saying why the view is unavailable. All of them
raised instead:

SchemaSkewError: index schema skew: expected 85, found 1

Metrics, the workload probe (three sites), the embedding status payload,
the schema-inference gate's tier identity read and the debt summary now
open without the version assertion and report what they find. The context
preamble's scheduler receipt is best-effort by its own contract and
already swallowed sqlite errors; a tier this runtime cannot use joins them.

The relink route never derived attachment provenance

attachment_refs.direction is NOT NULL and only the main write route
derived it, so blob-reference closure failed the constraint on any record
parsed before attachments carried direction. The relink path uses the same
shared derivation, reading the owning turn from the index when the append
payload's own message map does not carry it.

One session cost total on two model rows

sessions.reported_cost_usd is one exact dollar total, written onto a
single session_model_usage row. A merge-append that switched models left
the superseded row holding the previous total, double-counting it in every
sum over the session.

A read that skipped the controlled reader

The delegation work-evidence materializer opened a read-only ArchiveStore
directly — the one thing the read-surface boundary forbids, because such a
read carries no admission, no execution budget and no cancellation.

Fixtures that open a tier before building it

A connection profile checks a tier's declared version at open time, so a
test cannot open a tier-named path and initialize it afterwards. The
assertion tests build the tier first through the production bootstrap; the
mmap-budget test builds every attached tier the same way, since the tier
filenames are its subject; the descriptor-binding test names its database
for what it is. The embedding-drain stubs declare the version they claim,
without which the daemon's probe passes them over and the drain silently
reports no work.

The resilience suite launched another checkout's daemon

which("polylogued") resolves from PATH, which in a worktree is the main
checkout. The tests launched a different tree's daemon against this tree's
archive, then waited out their budget with nothing ingested and reported a
timeout. The running interpreter's own script directory comes first now.
The installed-wheel smoke had the same shape: uv venv picked whatever
interpreter uv found, and the package refuses to start off free-threaded
CPython.

Rendered ages re-baselined instead of redacted

"relative_time": "70w ago" became "71w ago" on its own, because the
value is computed against the host clock over fixture timestamps that never
move. This file's own contract routes such a field to _redact, "not to
update the baseline".

Surfaces that read a retired token as removed

#4363 retired the Beads issue route, but the Origin token stays:
deleting it would narrow the durable source.db CHECKs that still admit
stored rows. Three surfaces each encoded a different guess. Origin has
twelve tokens, ten of them public badges — the generated-contract test
derives that split from PUBLIC_ORIGIN_TOKENS, the teaching table follows
the enum, and the namespace policy stays exhaustive over executable
origins, which the retired one is not. Separately, exclusive_keys and
scratch are retired descriptor keys, as test_dev_loop_service already
declares.

Verification

devtools test <file> -n 2, worktree venv resynced to the current lockfile:

file	before	after
tests/unit/storage/test_durable_change_train.py	3 failed	98 passed
tests/unit/daemon/test_metrics_endpoint.py	2 failed	pass
tests/unit/maintenance/test_schema_inference_gate.py	1 failed	pass
tests/unit/storage/test_connection_profile.py	1 failed	pass
tests/unit/storage/test_archive_tiers_assertions.py	3 failed	pass
tests/unit/daemon/test_embedding_readiness.py	1 failed	pass
tests/unit/context/test_preamble.py::…non_git…	1 failed	pass

devtools verify --quick green at this head.

Residual risk

validate_schema=False is now used at seven read sites. Each is a status
or identity projection whose caller models skew as data; none of them
writes.

A first attempt at this branch also relaxed the identity guard so an
ops.db predating the ledger would converge. That fixed three tests and
broke thirty in test_durable_change_train.py — bootstrap proceeded where
it used to refuse. The relaxation is dropped and those three ops-convergence
tests remain red; the reader change that types the absent ledger as None
is kept and was measured separately as harmless (98 passed with it alone).

🤖 Generated with Claude Code

https://claude.ai/code/session_01YGi8wLWGR2HYBh8p8fXFXz

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: a720fe8e-87d0-4b8a-88ab-160c9a346d52

---

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.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-03T10:16:45.755165Z	d7ae654	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.