fix(gitea): make gitea-releases executable and correct misleading domain claims

gitea-releases was the weakest skill in the plugin: no allowed-tools, no
owner/repo resolution, and a checkbox list where a dispatch table belongs, so
an agent reaching it had to guess both its permissions and its inputs. The
id-vs-tag_name trap — deleting by tag name where the API wants the numeric id —
is restored as an explicit Gotcha because it destroys the wrong release
silently.

Elsewhere the `exclusive` flag was documented on the wrong side of the
read/write split, and label data from one instance was presented as though it
were universal, which invites an agent to assume a taxonomy that does not
exist on the target repo. rename_branch was missing from the branch surface.
Reference prose and fences are cleaned up in passing.

plugins/gitea/.apm/skills/gitea-issues/README.md

@@ -10,9 +10,8 @@ its state, adding/editing comments, applying labels, and searching issues/PRs ac
 The create flow closes out four enrichments deferred from issue #6 comment #848: label inference
 and milestone assignment (both by composing `gitea-labels-milestones`), an assignee workaround for
 the blocked `get_me` scope, and the "Depends on #N" dependency-linking convention. It supersedes the
-`issue`/`issue <N>`/`issue close <N>`/`issue comment <N>` dispatch in the old flat
-`plugins/bin/skills/gitea/SKILL.md`, removed per
-`docs/adr/0011-gitea-skill-deep-modules.md`.
+`issue`/`issue <N>`/`issue close <N>`/`issue comment <N>` dispatch this plugin's old single flat
+Gitea skill carried, retired when the plugin was split into per-domain deep modules.
 
 ## Before you start
 
@@ -34,7 +33,7 @@ issue request: local git branch or commit work belongs to `gitea-branches` (Gite
 
 ## Usage
 
-```
+```text
 /gitea-issues
 ```