zara-coding: fail closed when diff evidence changes during snapshot #197

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.diff() fences repository HEAD but reads working-tree/index diff evidence only once. If that evidence changes while HEAD remains stable, the harness can return a stale/mixed diff snapshot.

Acceptance:

deterministic RED where HEAD stays stable but git diff --numstat evidence changes during the snapshot window;
fail closed rather than returning stale diff evidence;
preserve max-files bounds and structured numstat parsing;
no patch-content collection, shell, or new authority;
focused tests, registry compatibility, full nix flake check, generated package builds, exact-head protected merge.

Advances #1. `RepositoryInspector.diff()` fences repository HEAD but reads working-tree/index diff evidence only once. If that evidence changes while HEAD remains stable, the harness can return a stale/mixed diff snapshot. Acceptance: - deterministic RED where HEAD stays stable but `git diff --numstat` evidence changes during the snapshot window; - fail closed rather than returning stale diff evidence; - preserve max-files bounds and structured numstat parsing; - no patch-content collection, shell, or new authority; - focused tests, registry compatibility, full `nix flake check`, generated package builds, exact-head protected merge.

nsaspy closed this issue

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

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

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

coding: validate git log object IDs #382