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

@@ -43,7 +43,7 @@ schema level — there's no scope variant to omit them for.
 
 ## List milestones
 
-```
+```text
 milestone_read  method: "list"  owner: <owner>  repo: <repo>  state: "open"
 ```
 
@@ -51,7 +51,7 @@ Report each as: id, title, state, due date, open/closed issue counts.
 
 ## Get one milestone
 
-```
+```text
 milestone_read  method: "get"  owner: <owner>  repo: <repo>  id: <id>
 ```
 
@@ -60,7 +60,7 @@ milestone_read  method: "get"  owner: <owner>  repo: <repo>  id: <id>
 Needed whenever the only handle available is a title — e.g. a `pull_request_read` response, which
 returns `milestone` as a bare title string rather than `{id, title}`. Call:
 
-```
+```text
 milestone_read  method: "list"  owner: <owner>  repo: <repo>  name: <title>
 ```
 
@@ -69,7 +69,7 @@ title typo or case mismatch), fall back to listing without the filter and matchi
 
 ## Create a milestone
 
-```
+```text
 milestone_write  method: "create"
   owner: <owner>  repo: <repo>
   title: "v1.0"
@@ -82,7 +82,7 @@ this milestone via `issue_write`/`pull_request_write`.
 
 ## Update or close a milestone
 
-```
+```text
 milestone_write  method: "update"  owner: <owner>  repo: <repo>  id: <id>  state: "closed"
 ```
 
@@ -90,7 +90,7 @@ Only pass the fields being changed — `id` plus any of `title`/`description`/`d
 
 ## Delete a milestone
 
-```
+```text
 milestone_write  method: "delete"  owner: <owner>  repo: <repo>  id: <id>
 ```