physical-verification-failure-recovery

Git status discrepancies are fixed by probing the working tree for divergent changes, selectively staging problematic paths, and re-aligning the index until the filesystem matches the claimed completion state. This enforces deterministic recovery steps with explicit verification before resuming.

Repository modifications occur when ghost completions claim success but the physical git state disagrees. A diagnostic probe examines git status, checks for hidden .git artifacts, and verifies whether .git is a directory or a file to locate the inconsistency.

Recovering a clean working tree requires truth-based correction that selectively stages problematic paths and re-checks until the working tree is clean. This approach stops progress and prohibits destructive actions until the inconsistency is understood.

The protocol applies to any directory or project where AI-assisted steps reported completion but physical state disagrees. It locates divergent changes across the suspected directory and verifies with git status and ls -la before correcting the index.

Before resuming work after a git verification failure, you must apply explicit verification steps to ensure a clean state. The protocol enforces safe interaction with git and prohibits destructive actions until the discrepancy between completion claims and repository status is fully reconciled.