zara-coding: prove detached worktree creation before returning success #193

New issue

Closed

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

nsaspy commented

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

Owner

Advances #1.

add_detached_worktree() currently returns success immediately after git worktree add exits zero. That is weaker than the rest of the coding harness evidence contract: a mocked/abnormal Git result can claim success without proving the target is registered, detached, and still at expected_head.

Acceptance:

deterministic RED where git worktree add exits zero but post-add inventory does not contain the expected target;
after creation, prove exactly the expected registered worktree path, detached state, no branch, and expected HEAD before returning success;
reject changed/malformed post-add identity with bounded CodingError;
preserve allowed-root confinement, direct commit verification, fixed argv/no shell and approval boundary;
focused tests, registry compatibility, full nix flake check, generated package builds, exact-head protected merge.

Advances #1. `add_detached_worktree()` currently returns success immediately after `git worktree add` exits zero. That is weaker than the rest of the coding harness evidence contract: a mocked/abnormal Git result can claim success without proving the target is registered, detached, and still at `expected_head`. Acceptance: - deterministic RED where `git worktree add` exits zero but post-add inventory does not contain the expected target; - after creation, prove exactly the expected registered worktree path, detached state, no branch, and expected HEAD before returning success; - reject changed/malformed post-add identity with bounded `CodingError`; - preserve allowed-root confinement, direct commit verification, fixed argv/no shell and approval boundary; - focused tests, registry compatibility, full `nix flake check`, generated package builds, exact-head protected merge.

nsaspy closed this issue

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

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

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

coding: fail closed on changing diff evidence #384