stale-checkout-recovery

To recover from a stale git branch, create a sibling worktree directly from origin/main. This isolates the recovery process, validates the starting SHA, and ensures you begin implementation from a clean, up-to-date base without modifying the original checkout.

Incorrect task status occurs because a local checkout parked on a stale branch falls behind origin/main. Reading task status directly from origin/main instead of the local stale branch ensures accurate batch progress and prevents missing tasks or conflicting changes.

The best way to align a working tree with origin/main is creating a fresh sibling worktree from the remote main branch. This preserves the stale local clone for reference only while validating the correct starting SHA for new batch cycles.

Yes, creating a sibling git worktree from origin/main isolates batch work from a stale main clone. This approach verifies the starting branch and commits before beginning work, preventing divergence between local and remote repositories.

You need to validate the starting SHA whenever batch work must begin from a known-good base. Verifying the starting state, including branch and commits, prevents missed tasks and incorrect completion status during new batch development cycles.