Audit destructive command UX and dry-run output for v1.0

[devgamesan]

Context

Commands such as branch delete, branch prune, config remove, doctor --repair, and recover --yes can delete refs, modify remotes, or repair repository wiring. For v1.0, the UX should make scope and consequences clear.

Tasks

• Review destructive or state-changing commands for clear prompts and dry-run output.
• Confirm each command identifies affected locations: origin, gateway repo, dev cache repo, and dev work repo.
• Ensure --yes behavior is documented and cannot be confused with dry-run behavior.
• Add or update tests for any unclear behavior found during the audit.

Acceptance Criteria

• Every destructive command has clear confirmation or explicit --yes behavior.
• Dry-run output lists planned operations with enough detail to audit before execution.
• README/README.ja document the safety model for these commands.
• Tests cover any changed prompts or output contracts.