rebase
Keywords: rebase, git rebase, history replay, rebase conflict, continue rebase, abort rebase, git worktree, rewritten history, authorized force-with-lease publication
Result-bound verification
For start/continue completion, bind validation to the immutable result commit R.
Run repository-required and changed-interaction checks on a clean detached worktree
or equivalent isolated checkout of R, separately from restored user changes.
Preserve unrelated work; a passing dirty worktree does not validate its commit.
Record the checked OID and environment; verify checks left tracked source unchanged.
Source-mutating checks invalidate that evidence. Commit a required correction within
the existing task authority, then rebind R and rerun its checks. When that commit
is blocked or unauthorized, pause rather than reporting the correction published.
Every result change, including remote reconciliation, invalidates earlier result
validation. Reobserve the named result ref before completion; it must still name
R. A decision or stopped-state path cannot become a success merely because its
refs or ancestry still satisfy the goal.