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-labels-milestones/references/labels.md

@@ -62,9 +62,15 @@ label_read  method: "get_repo_label"  owner: <owner>  repo: <repo>  id: <id>
 ## Resolve a name to an ID
 
 There is no direct name lookup. List all repo labels (paginating if needed), scan for a
-case-insensitive name match, and extract `id`. This is the required first step before any label
-application on an issue or PR — the actual `add_labels`/`replace_labels`/`remove_label` call lives
-in `gitea-issues`/`gitea-prs` via `issue_write`/`pull_request_write`, which take numeric IDs only.
+case-insensitive name match, and extract `id`. Both pools can apply to one issue: if the name is
+not in `list_repo_labels`, also check `list_org_labels` before reporting it unresolved. That method
+takes `org`, not `owner`/`repo` — pass the repo's `owner` as `org`, which is what it means when the
+owner is an organisation. If that call fails, the owner is a user account, there is no org pool, and
+the miss is a real miss.
+
+Resolution is the required first step before any label application on an issue or PR — the actual
+`add_labels`/`replace_labels`/`remove_label` call lives in `gitea-issues`/`gitea-prs` via
+`issue_write`/`pull_request_write`, which take numeric IDs only.
 
 ## Create a label