reconcile

To detect state drift across parallel git worktrees, you can run a reconcile check that reviews recent git history, compares modified files, and validates state consistency to surface overlapping edits or unmerged work before they cause subtle bugs.

SSOT violations occur when the same fact appears in multiple files with different values. A reconcile check validates single-source-of-truth consistency by comparing state logs and file diffs to surface contradictions introduced during a crash or parallel session.

You can check for merge conflicts and orphaned references by scanning recent git branch history and comparing state file timestamps. This read-only reconcile process detects duplicate entries, contradictions, and unmerged work without modifying your repository.

Yes, you can validate state consistency safely because the reconcile process stays strictly read-only until approval. It reviews git history, file diffs, and SSOT validation checks to detect drift without making automatic commits or file modifications.

You should run a worktree reconciliation check after merging branches, recovering from a Claude Code session crash, or performing periodic sanity checks when multiple parallel sessions may have caused commits, state files, or documentation to diverge.

The best way to catch session drift is running a reconcile check that uses recent git history, file diffs, and state consistency checks to detect overlapping edits, duplicate state entries, and SSOT violations across parallel worktrees before they break work.