docs: add portable llm-project-workflow skill + templates (#46)

Extract the project's operating rules into a reusable, project-agnostic skill
so any repo can adopt the same safe LLM workflow.

- skills/llm-project-workflow/SKILL.md: issue-first; isolated branch worktrees
  (main checkout = orchestration only); distinct author/reviewer identities and
  profile safety (secrets by reference only; stop if authenticated user == PR
  author); branch naming; start/review/merge/cleanup workflows; fail-closed
  cases; recovery patterns; and an "Adapting to a project" table for the
  forge-specific names.
- templates/: copy/paste prompts for start-issue, review-pr, merge-pr,
  recover-bad-state, worktree-cleanup.
- Link the skill from README.md and docs/llm-workflow-runbooks.md (the runbook
  is framed as the Gitea-specific application of the portable skill).

Docs-only; no code, no secrets, safe placeholder examples only. No change to
MCP runtime, Gitea API, credential storage, or worktree helpers.

Checks: full suite 287 passed / 0 failures; git diff --check clean; secret scan
of skills/ clean.

Closes #46. Refs #38, #39.

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

README.md

@@ -274,15 +274,6 @@ The generated launcher snippets contain only `command`, `args`,
 `GITEA_MCP_CONFIG`, and `GITEA_MCP_PROFILE` — never a token or password.
 </details>
 
-### Portable LLM workflow skill
-
-Reusable LLM operating rules are packaged as a portable skill at
-[`skills/llm-project-workflow/SKILL.md`](skills/llm-project-workflow/SKILL.md).
-It documents issue-first work, isolated branch worktrees, no self-review or
-self-merge, profile safety, fail-closed behavior, merge cleanup, and recovery
-patterns. Copy the `skills/llm-project-workflow/` directory into other projects
-that should use the same workflow.
-
 <details>
 <summary><strong>Codex / non-MCP tools</strong></summary>
 

docs/llm-workflow-runbooks.md

@@ -18,12 +18,6 @@ behavior they rely on already exists (canonical runtime profiles, the
 interactive setup menu, identity/eligibility checks, gated review/merge, and
 audit logging). See [Related documents](#related-documents).
 
-For cross-project use, copy the portable workflow skill at
-[`../skills/llm-project-workflow/SKILL.md`](../skills/llm-project-workflow/SKILL.md).
-It extracts the issue-first, isolated-worktree, no-self-review, profile-safety,
-merge-cleanup, fail-closed, and recovery rules into a reusable package that can
-be adapted to other repositories.
-
 ## Principle: the profile is the role, not the LLM
 
 ```text
@@ -328,7 +322,6 @@ with the profile and authenticated user when `GITEA_AUDIT_LOG` is set (see
 
 ## Related documents
 
-- [`../skills/llm-project-workflow/SKILL.md`](../skills/llm-project-workflow/SKILL.md) — portable cross-project LLM workflow skill.
 - [`gitea-execution-profiles.md`](gitea-execution-profiles.md) — the profile model.
 - [`safety-model.md`](safety-model.md) — trust boundaries and audit logging.
 - [`tool-boundaries.md`](tool-boundaries.md) — per-tool allowed operations.

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