fix(gitea): restore routing and sourcing content the retrofit dropped

gitea-issues asserted flatly that a merge never closes an issue, contradicting
gitea-prs' references/merging.md, which documents that closing keywords in
commits landing on the default branch do close one. The qualifier that made the
claim true had been deleted; both sides now agree.

gitea-releases had lost an epistemic hedge and its verification step, leaving
conventions.md asserting unconfirmed tag auto-creation as fact. Nothing in the
research corpus sources it, so the hedge and the verify-afterward instruction are
back rather than upgraded.

Descriptions were cut 50-240 chars under the 400 budget and shed routing with
them: gitea-workflow's boundary named no target, gitea-prs lost the issue/PR
number-space directive the suite is built around at 163/400, gitea-releases lost
its boundary and every trigger. Restored, inside budget. Also restores
delete_branch's hard-refusal strength and gitea-files' Read/Write/Edit pointer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti

plugins/gitea/skills/gitea-files/SKILL.md

@@ -3,8 +3,8 @@ name: gitea-files
 
 description: >
   Use when reading or writing files or directories in a Gitea repository via the MCP server,
-  rather than the local filesystem — even when the user does not say "Gitea". Not commit
-  history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
+  rather than the local filesystem (for a local path use Read/Write/Edit) — even when the user
+  does not say "Gitea". Not commit history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
 
 compatibility: Requires the Gitea MCP server configured with a token scoped to at least
   write:repository. Tested with a token holding write:issue + write:repository; write:issue