docs: remove superseded recover-dirty-worktree template (#46)

Corrective cleanup: PR #47 was closed-not-merged but a partial landing left
skills/llm-project-workflow/templates/recover-dirty-worktree.md on master. The
intended #47 state replaced it with the two more precise templates, which are
already present:
- recover-bad-state.md
- worktree-cleanup.md

Remove the superseded template. No references to recover-dirty-worktree.md
exist in README/docs/skills (verified before and after), so no reference updates
are needed. Docs-only; no runtime code touched.

Full suite 291 passed / 0 failures; git diff --check clean.

Closes #46.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

skills/llm-project-workflow/templates/recover-dirty-worktree.md

@@ -1,31 +0,0 @@
-# Recover Dirty Worktree Prompt
-
-You are recovering repository state in `<repo-name>`.
-
-Rules:
-
-- Do not reset, delete, clean, or overwrite work unless explicitly instructed.
-- Do not edit another issue's worktree unless assigned to that issue.
-- Preserve ambiguous work before any destructive operation.
-
-Workflow:
-
-1. Run `git status --short --branch`.
-2. Identify whether dirty files belong to the current issue, another issue, or
-   unknown work.
-3. If dirty work belongs to another issue, leave it alone and use a separate
-   worktree for the current task.
-4. If an unauthorized untracked file was created, stop and report its exact path.
-5. Remove unauthorized files only when explicitly instructed.
-6. If local `<default-branch>` is ahead of `<remote>/<default-branch>`, stop and
-   report both commit hashes.
-7. If cleanup is requested, verify the branch is merged or explicitly abandoned
-   before deleting any branch or worktree.
-
-Report:
-
-- current branch
-- dirty files
-- ownership assessment
-- actions taken
-- remaining blockers