validate-registry

To validate a feature registry against local Git branches, you run an audit process that checks the `workspace/STATE.md` file for status mismatches and stale entries. This verifies registered branches and worktrees exist and are correctly linked.

Detecting unregistered Git worktrees involves auditing your feature registry to flag any active worktrees missing from the tracking records. This identifies active development work that lacks proper registry documentation.

Yes, you can automatically fix feature registry inconsistencies using an automated fix mode. This mode corrects identified issues like stale entries and status mismatches directly in the `workspace/STATE.md` file after running an audit.

A feature registry shows stale entries when registered branches and worktrees no longer correspond to active development work. This happens when the registry state in `workspace/STATE.md` diverges from actual Git branch and filesystem state.

Yes, the registry validation process supports read-only auditing. You can perform consistency checks to verify registered branches and worktrees exist and are correctly linked without making any automated changes.

You need to run a feature registry consistency check before a release to confirm all features marked as active have corresponding Git branches and worktrees. This prevents inconsistencies and ensures no stray worktrees exist.