Unstaged user edits can ride into an executor commit #158

New issue

Closed

opened 2026-08-15 14:33:53 +00:00 by john · 0 comments

john commented

2026-08-15 14:33:53 +00:00

Owner

Source: strict re-review C-15
Verdict: DISPUTE - documented limit, closing

Claim as reviewed

Pre-existing unstaged user edits on a leased file can ride into an executor commit, so commit attribution is not guaranteed by a clean index.

At HEAD `f354864` (v3.3.0)

Accurate, and stated at the site in both directions. cadence-core/workflows/execute.md:74-92: an unstaged edit to a declared path rides into the commit because staging a path stages its whole working-tree content, and an untracked file outside the lease that a later git add sweeps in reads as a lease violation the executor never committed.

The workflow also gives the remedy: "start it from a clean worktree (git status --porcelain empty), not merely a clean index."

Note

"The lease gate cannot separate them either: the path is declared, so the write is legal, and provenance is not a property of a path." Widening the check does not close it.

**Source:** strict re-review C-15 **Verdict:** DISPUTE - documented limit, closing ### Claim as reviewed Pre-existing unstaged user edits on a leased file can ride into an executor commit, so commit attribution is not guaranteed by a clean index. ### At HEAD f354864 (v3.3.0) Accurate, and stated at the site in both directions. `cadence-core/workflows/execute.md:74-92`: an unstaged edit to a declared path rides into the commit because staging a path stages its whole working-tree content, and an untracked file outside the lease that a later `git add` sweeps in reads as a lease violation the executor never committed. The workflow also gives the remedy: "start it from a clean worktree (`git status --porcelain` empty), not merely a clean index." ### Note "The lease gate cannot separate them either: the path is declared, so the write is legal, and provenance is not a property of a path." Widening the check does not close it.