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/skills/gitea-labels-milestones/README.md

@@ -14,7 +14,7 @@ That relationship is documented here rather than in the skill description, which
 
 ## Usage
 
-```
+```text
 /gitea-labels-milestones
 ```
 

plugins/gitea/skills/gitea-labels-milestones/SKILL.md

@@ -24,7 +24,7 @@ allowed-tools: Bash mcp__gitea__label_read mcp__gitea__label_write mcp__gitea__m
 
 - **Applying a label takes a numeric ID, but issue/PR responses slim labels down to name strings.** An issue's existing labels yield no IDs — resolve name → ID with `label_read`.
 - **`pull_request_read` returns `milestone` as a bare title string** where `issue_read` returns `{id, title}` — recover the milestone's ID by listing milestones and matching the title.
-- **Never assume a `Kind/*`/`Priority/*`/`Status/*` scope is exclusive — read each label's own `exclusive` field.** `list_repo_labels` returns it per repo label, it is not org-only, and where it is `true` Gitea enforces one-per-scope itself. Replacing rather than stacking on a label whose `exclusive` is `false` destroys a valid label.
+- **Never assume a `Kind/*`/`Priority/*`/`Status/*` scope is exclusive — read each label's own `exclusive` field.** `list_repo_labels` returns it on every repo label, so it is always *readable* per label; `label_write` documents it as "(org only)" because it is only *settable* through the org create methods. Where it is `true` Gitea enforces one-per-scope itself, and replacing rather than stacking on a label whose `exclusive` is `false` destroys a valid label.
 
 ## Step 1 — Resolve owner, repo and org
 

plugins/gitea/skills/gitea-labels-milestones/references/label-inference.md

@@ -12,15 +12,11 @@ description) to this repo's `Kind/*` / `Priority/*` / `Status/*` label taxonomy.
 `gitea-issues` and `gitea-prs` before creating or updating an issue/PR, and directly when the user
 asks to label something without naming exact labels.
 
-## Exclusivity is per label — read it, never infer it
+## Branching on exclusivity
 
-Gitea's `exclusive` flag is a real per-label boolean returned by `list_repo_labels`, and where it is
-`true` the server enforces one-label-per-scope itself. It is not an org-only setting, and the `/`
-delimiter in a name says nothing about it. Verified on `Defame1297/holocron`: every `Priority/*`,
-`Reviewed/*` and `Status/*` label is `exclusive: true`, while every `Kind/*` label — and
-`Compat/Breaking` — is `exclusive: false` and is used stacked.
-
-So read each candidate label's own `exclusive` value from the resolution call and branch on it:
+`references/labels.md` owns the exclusivity rule and the read-versus-write asymmetry behind it. Read
+it there rather than assuming a scope's behaviour from its name. Inference needs only the branch:
+carry each candidate label's own `exclusive` value forward from the resolution call and act on it.
 
 - **`exclusive: true`** — the server drops the sibling on write. Add the label and let it; do not
   pre-remove the label already there, and do not compute a replacement set client-side. Inferring
@@ -29,7 +25,7 @@ So read each candidate label's own `exclusive` value from the resolution call an
   same scope destroys a valid one: an issue can legitimately carry `Kind/Bug` and `Kind/Security`
   at once.
 
-There is no client-side exclusivity convention for this skill to enforce.
+This skill enforces no client-side exclusivity convention of its own.
 
 ## Signal → label mapping
 
@@ -42,6 +38,7 @@ There is no client-side exclusivity convention for this skill to enforce.
 | Improvement to existing behavior, "make X better", refactor with behavior change | `Kind/Enhancement` |
 | Docs-only change, README/comment/guide updates | `Kind/Documentation` |
 | Vulnerability, credential exposure, injection risk, auth bypass | `Kind/Security` |
+| Test coverage, "add tests for X", a missing or flaky test, a test-only change | `Kind/Testing` |
 
 **`Priority/*`** (urgency):
 
@@ -49,6 +46,7 @@ There is no client-side exclusivity convention for this skill to enforce.
 |---|---|
 | "blocking", "critical", "urgent", production-down | `Priority/Critical` |
 | "soon", "high priority", "should do this sprint" | `Priority/High` |
+| "low priority", "nice to have", "whenever", explicitly deferred | `Priority/Low` |
 | No urgency signal present | `Priority/Medium` (default) |
 
 **`Status/*`** (workflow state):
@@ -57,6 +55,10 @@ There is no client-side exclusivity convention for this skill to enforce.
 |---|---|
 | Explicit statement that the work is blocked on something else | `Status/Blocked` |
 
+The label names in all three tables are the taxonomy this guide was written against; none of them is
+guaranteed to exist on the target repo. Step 2 below resolves every inferred name against the live
+label set, and a name that does not resolve is reported rather than substituted.
+
 ## Procedure
 
 1. Read the conversation context (issue/PR title, body, or the triggering discussion) for the

plugins/gitea/skills/gitea-labels-milestones/references/labels.md

@@ -46,30 +46,37 @@ runtime error from Gitea rather than a client-side validation error.
 
 ## List repo labels
 
-```
+```text
 label_read  method: "list_repo_labels"  owner: <owner>  repo: <repo>  per_page: 50
 ```
 
 Paginate (`page: 1, 2, ...`) until the returned count is less than `per_page`. This is the only way
 to build a complete name → ID map — there is no lookup-by-name endpoint.
 
-Every returned repo label carries its own `exclusive` boolean; the field is not org-only. Verified on
-`Defame1297/holocron`: all `Priority/*`, `Reviewed/*` and `Status/*` labels are `exclusive: true`,
-while all `Kind/*` labels and `Compat/Breaking` are `exclusive: false`. Where it is `true` Gitea
-enforces one-label-per-scope server-side; where it is `false` labels in that scope stack legitimately.
-Read the field — never infer exclusivity from the `/` in a name.
+Every returned repo label carries its own `exclusive` boolean, so exclusivity is always *readable*
+per repo label. That does not contradict `label_write`'s schema, which annotates `exclusive` as
+"(org only)": reading and setting are different questions, and only the setting half is org-scoped
+(see "Create a label" below). Where the field is `true` Gitea enforces one-label-per-scope
+server-side; where it is `false` labels in that scope stack legitimately. Read the field — never
+infer exclusivity from the `/` in a name, and never carry another repo's map over.
+
+On the instance this skill was authored against (`Defame1297/holocron`) the split ran: every
+`Priority/*`, `Reviewed/*` and `Status/*` label `exclusive: true`, every `Kind/*` label and
+`Compat/Breaking` `exclusive: false`. That is one repo's configuration at one point in time, recorded
+as a worked example of what the field looks like in practice — it is not a property of the taxonomy
+and says nothing about the repo you are called against.
 
 ## Get one label
 
-```
+```text
 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`. 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
+The tool surface carries no lookup-by-name method. List all repo labels (paginating if needed),
+scan for a 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. Its failure modes are not interchangeable. `token does not have at least
 one of required scope(s), required=[read:organization]` means the org pool was never queried — report
@@ -82,7 +89,7 @@ Resolution is the required first step before any label application on an issue o
 
 ## Create a label
 
-```
+```text
 label_write  method: "create_repo_label"
   owner: <owner>  repo: <repo>
   name: "Kind/Bug"
@@ -98,7 +105,7 @@ tool — it is set in the Gitea UI or against the REST API directly, and read ba
 
 ## Edit a label
 
-```
+```text
 label_write  method: "edit_repo_label"  owner: <owner>  repo: <repo>  id: <id>  color: "#ff0000"
 ```
 
@@ -106,7 +113,7 @@ Only pass the fields being changed — `id` plus any of `name`/`color`/`descript
 
 ## Delete a label
 
-```
+```text
 label_write  method: "delete_repo_label"  owner: <owner>  repo: <repo>  id: <id>
 ```
 

plugins/gitea/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>
 ```