Always preserve and systematically re-apply changes in a branch-based workflow

The user follows a strict plan-driven development process for PRs, expecting work to occur on a dedicated branch off master with a todo list derived from an approved plan. When a worktree is deleted or uncommitted changes are lost, they re-create the worktree and re-apply every change phase by phase — source, docs, tests — rather than skipping anything. They also require committing changes to the remote branch so progress persists, and they value preserving plan/untracked files (e.g., .lore.md, .craft-issue-842-plan.md, .opencode/). After re-applying, the user expects validations: tests, typecheck, lint, and build. When reviewing external changes, they inspect diffs in detail before proceeding. This pattern shows the user never tolerates lost work and always wants a meticulous, recoverable, and verifiable workflow.