zara-coding: fail closed when dirty-state evidence changes during inspection #198

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.inspect() rechecks HEAD/branch identity, but repository_clean verification also depends on the collected tracked/untracked changed-path set. That set is currently read once, so filesystem/index drift can produce a stale or mixed clean/dirty snapshot without changing HEAD or branch.

Acceptance:

deterministic RED where HEAD/branch stay stable but changed-path evidence changes during collection/recheck;
fail closed instead of returning stale dirty/changed_paths evidence;
preserve the 100-path bound and deduplication semantics;
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.inspect()` rechecks HEAD/branch identity, but `repository_clean` verification also depends on the collected tracked/untracked changed-path set. That set is currently read once, so filesystem/index drift can produce a stale or mixed clean/dirty snapshot without changing HEAD or branch. Acceptance: - deterministic RED where HEAD/branch stay stable but changed-path evidence changes during collection/recheck; - fail closed instead of returning stale `dirty`/`changed_paths` evidence; - preserve the 100-path bound and deduplication semantics; - 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