chore(gitea): regenerate the flat content mirror after the ADR-0020 retrofit

Generated output, not authored content: scripts/sync-plugin-content.sh --all.
Claude Code has no .apm/ awareness, so this compiled mirror must track .apm/ or
the check-plugin-content-sync pre-push hook reports drift.

Deferred to a single commit at the end of the wave on purpose. sync_dir runs
rm -rf before every copy, so running it while seven agents were editing the
same plugin would have raced them; agents were told not to sync for that reason.

Refs #99

plugins/gitea/skills/gitea-branches/README.md

@@ -10,6 +10,18 @@ history (list commits, get a single commit's full detail) against a Gitea reposi
 pagination conventions specific to Gitea's API (e.g. refusing to delete a protected branch without
 explicit confirmation, and treating unexpected 404s as possible masked 403s).
 
+## Boundaries
+
+This skill operates on the Gitea server via the MCP tools, never on your local checkout. Branch
+and commit-history work against the working copy belongs to `git-branches` and `git-history`.
+Branch references that only exist relative to a pull request — a PR's head or base branch, and
+cross-repo fork PR heads in particular — belong to `gitea-prs`; `list_branches` cannot see a fork's
+head at all.
+
+The skill triggers on phrasings like "list branches", "create a branch", "delete a branch",
+"what commits are on this branch", "show commit <sha>", and "what changed in that commit", even
+when the user does not say "Gitea", as long as the repo's remote is a Gitea instance.
+
 ## Before you start
 
 Requires a Gitea MCP server configured with a token that has `write:repository` scope. This is