Seal five read-path files and the egress receipt's field walker

[lamemustafa]

Follows #434 on #416. #434 sealed fourteen files that decide what Bridge posts or lets leave the machine. This seals six more from the same search: five whose own bodies decide what a read tells a caller or when a sync may move past rows, and agent_receipt_fields.rs, which belongs with #434's egress record (#416 listed it as borderline).

MAX_SURFACE_FILES 232 → 238

Each file is named beside the constant, five under "What a read reports, or lets a sync skip" and one under "And the egress record". Headroom stays at zero.

file	what it holds
agent_movement.rs	the ledger_movement tool, and its voucher predicate: cancelled, optional and entryless vouchers are left out of the figures
agent_movement_math.rs	one movement row: closing = opening + debit + credit when an opening was observed; otherwise closing empty and partial / opening_balance_not_observed
agent_outstandings.rs	receivable/payable totals over open bills, and the 0–30 / 31–60 / 61–90 / 90+ / unaged buckets
agent_change_parse.rs	checkpoint_advanceable: not truncated, and the highest returned alter id — or the requested checkpoint when none was returned — reaches the company high-water
agent_changes.rs	changed_since: applies that per axis, reports checkpoint_advanceable only when both hold, picks each axis's next alter id from its own result, refuses a checkpoint past the snapshot
agent_receipt_fields.rs	released_fields, used by the egress receipt in agent_delivery.rs to record a tool response — any tool, not only reads — by key paths rather than values

Written to #434's rule — say what the file holds; "only" only where that file alone enforces it (checkpoint_advanceable = voucher && master feeding the output). Three first drafts failed that check and were narrowed against the code; the three rows above marked by a fallback, a per-axis split and a condition are the corrected wording.

"Not pinned, and deliberately"

No longer lists the read-path files. It now names observability.rs, with a reason checked against the tree: the tally_telemetry_preview Tauri command returns what it builds, but no frontend code calls that command and nothing sends the result off the machine. It becomes a candidate when something does. (An earlier framing — "no command surfaces it" — was false; the command exists, registered since July, with no caller.)

Guard

admission_and_egress_files_stay_pinned.rs gains READ_PATH_AND_RECEIPT: [&str; 6] beside ADMISSION_AND_EGRESS, sharing its two helpers rather than copying them, and the negative test now drives both lists.

Measured, not asserted — agent_movement_math.rs removed from the real surface:

read_path_files_are_still_pinned ... FAILED   (since renamed read_path_and_receipt_files_are_still_pinned)
dropped from the compatibility surface: ["src-tauri/src/agent_movement_math.rs"]

Surface restored byte-identical afterwards; all three tests pass.

Checks (local, rustc 1.96.0)

• reseal.sh --pins-changed, then --verify current. Diff vs master: 6 pins added, 1 rehash (lib.rs), nothing else.
• cargo fmt --check, clippy with CI's flags: clean. Workspace tests: 1,560 passed, 0 failed. Compatibility tool tests pass, including the real-tree cap invariant.

Review

Two sonnet reviews. Mechanics: all 238 hashes and the manifest digest recomputed independently, invariant test run, guard shown non-vacuous for both lists — clean. Reasons: eight of nine claims verified against the code, including >= vs >, the 91+ bucket and no cross-axis leakage; one overstatement found and fixed in the second commit — released_fields runs on the generic response path for every tool, so it is no longer framed as read-path. docs/proposed-rust-module-conventions.md stopped quoting a stale pin count.

Ordering with #436: it touches the surface/matrix hashes but not this constant or paragraph; whichever merges second reseals. #436's branch predates #434's squash, so git currently reports add/add conflicts in lib.rs and the guard file even though #436's content there is byte-identical to master; rebasing #436 onto master removes them.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.