fix(gitea-issues): list_issues does have type and milestones on v1.7.0

SKILL.md's headline Gotcha said `list_issues` "has no `type` filter", and
references/issues.md stated in bold that neither `type` nor `milestones`
exists, "despite both appearing in api-reference.md". Both parameters are
present on the deployed gitea-mcp v1.7.0 and both work: `type: "issues"`
returns only issues, `type: "pulls"` only PRs, and `milestones` filters by
name. Unfiltered, the same window returns them interleaved, so the mixing
the Gotcha describes is real — only the stated remedy was wrong.

This mattered most in gitea-workflow's no-args check-in, which lists open
issues through this skill and so reported PRs under "Open Issues" while
the skill forbade the one-parameter fix. The list flow now passes
`type: "issues"`.

references/sources.md recorded the absence as a live-verification win over
stale research docs; it now records that the earlier check was superseded
by v1.7.0, since drift runs in both directions. gitea-prs cited the same
parameter as its canonical drift example and no longer does — no
replacement example was substituted, because the obvious candidate was not
verified in this pass.

Also defaults label writes to `add_labels`: `replace_labels` clears every
label not in the array, and per-label exclusivity makes blanket replacement
destructive for a non-exclusive scope.

Verified live against gitea-mcp v1.7.0, read-only calls.

Refs #99

plugins/gitea/.apm/skills/gitea-issues/references/sources.md

@@ -1,12 +1,13 @@
 # Sources
 
 **Note on call signatures:** per `docs/adr/0011-gitea-skill-deep-modules.md`, the tool parameter
-signatures in `references/issues.md` and `references/search.md` were re-verified live via
-`ToolSearch` against the deployed `gitea-mcp` server at authoring time — they are not copied
-verbatim from `api-reference.md`. This resolves issue #6 comment #849's root-cause finding that a
-prior skill was authored from API docs that had drifted from the actual MCP tool schema; the live
-check caught exactly this drift on `list_issues` (see `references/issues.md` — the research doc
-documents a `type` and a `milestones` parameter that do not exist on the deployed server).
+signatures in `references/issues.md` and `references/search.md` are re-verified live via
+`ToolSearch` against the deployed `gitea-mcp` server — they are not copied verbatim from
+`api-reference.md`. This resolves issue #6 comment #849's root-cause finding that a prior skill was
+authored from API docs that had drifted from the actual MCP tool schema. That re-verification is
+ongoing, not one-off: an earlier live check recorded `list_issues` as lacking the `type` and
+`milestones` parameters `api-reference.md` documents, and both are present on the deployed
+gitea-mcp **v1.7.0**, which is the version these signatures are current as of.
 
 ## gitea-mcp-repo