docs: let maintenance clones self-heal and abort without leaving debris

A failed nightly run left edits in the maintenance clone, and every later run
correctly refused to work on a dirty worktree, so one failure stalled the whole
pipeline until morning.

Maintenance task commands now recognise a gitignored .maintenance-clone marker.
In a marked disposable clone they discard leftover debris, return to main, and
continue; in a human working copy they still stop and touch nothing.

Add an explicit abort protocol: revert your own edits, confirm the worktree is
clean, release the claim, and report. Restore the honest skip that the
complete-file rule had squeezed out, since a laundered fix is worse than a
documented skip, and describe how to handle a file that is entirely an
external-data boundary instead of inventing generic JSON contracts.

This commit is contained in:

Bohdan Triapitsyn

2026-08-17 21:49:33 +03:00

parent d9f1c0d44c

commit 344c1b3ce3

6 changed files with 106 additions and 7 deletions

.gitignore

View File

@@ -68,5 +68,8 @@ data/
 workspaces/
 *.pid
 .worktrees/
 # Marks a disposable clone dedicated to unattended maintenance tasks.
 .maintenance-clone
 test-results/
 artifacts/