zara-coding: fail closed if branch inventory changes during read #200

New issue

Closed

opened 2026-09-08 02:03:12 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:12 +00:00

Owner

Advances #1.

RepositoryInspector.branches() already performs a bounded second for-each-ref probe to detect overflow, but it currently discards the probe result after parsing. A concurrent local ref mutation between the first inventory and the probe can therefore return stale branch evidence while claiming success.

Acceptance:

deterministic RED proving a changed branch/ref snapshot between the two reads fails closed;
retain the existing branch-count bound and structured parser behavior;
compare canonical parsed snapshots, not raw output ordering assumptions;
emit a useful local incompatibility/error instead of returning mixed evidence;
no new mutation/tool surface or Core dependency;
focused tests, registry compatibility gate, nix flake check, generated package build, exact-head merge.

Advances #1. `RepositoryInspector.branches()` already performs a bounded second `for-each-ref` probe to detect overflow, but it currently discards the probe result after parsing. A concurrent local ref mutation between the first inventory and the probe can therefore return stale branch evidence while claiming success. Acceptance: - deterministic RED proving a changed branch/ref snapshot between the two reads fails closed; - retain the existing branch-count bound and structured parser behavior; - compare canonical parsed snapshots, not raw output ordering assumptions; - emit a useful local incompatibility/error instead of returning mixed evidence; - no new mutation/tool surface or Core dependency; - focused tests, registry compatibility gate, `nix flake check`, generated package build, exact-head merge.

nsaspy closed this issue

2026-09-08 02:03:13 +00:00

nsaspy referenced this issue from a pull request that will close it,

2026-09-08 02:19:38 +00:00

coding: prove detached worktree creation #381