docs(remove): state that --force discards all uncommitted changes

[max-sixty]

The FAQ and the wt remove --force help text said --force overrides the untracked-files check "for build artifacts". --force actually removes a dirty worktree including staged and modified tracked files, not just untracked ones (test_remove_force_with_modified_files, test_remove_force_with_staged_files). On a destructive command, that wording can lead users to consent to more data loss than they expected.

Updates the --force arg help, the "Force flags" table and example in src/cli/mod.rs, and the FAQ to say --force discards staged, modified, and untracked files; the help_remove_long snapshot and the remove.md / faq.md doc and skill mirrors are regenerated to match.

This was written by Claude Code on behalf of Maximilian Roos

[worktrunk-bot]

User-facing wording is accurate — verified against test_remove_force_with_modified_files and test_remove_force_with_staged_files, and against build_remove_command which forwards --force straight to git worktree remove --force.

Two internal doc comments still carry the pre-correction framing if you want to mop them up while the context is fresh — both purely developer-facing, so happy to push a follow-up if useful:

• build_remove_command in src/commands/process.rs — /// force_worktreeadds--forcetogit worktree remove, allowing removal /// even when the worktree contains untracked files (like build artifacts).
• force_worktree field on the Remove variant in src/commands/worktree/types.rs — /// Force git worktree removal even with untracked files.