docs: trim repeated boilerplate in git, gitea, and bin skills

Finding 13: five blocks of near-identical wording were repeated across
skills within a plugin — the gitea "resolve owner and repo" step (5
skills), the 404-masks-403 note (6 files), the manual pagination
explanation (8 files), the git plugin's main/master force-push refusal
(7 files, some with multiple internal restatements), and the bin
skills' domain-glossary/ADR paragraph (5 skills). Tightened each
instance in place — same meaning, fewer words — rather than extracting
to a shared file, which ADR-0014's one-file-per-skill install
constraint rules out. Left the three git skills' structured-result
JSON shapes alone (coupled to the separate, out-of-scope git-orchestrate
merge candidate, finding 19).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD

plugins/gitea/.apm/skills/gitea-releases/references/call-signatures.md

@@ -70,7 +70,6 @@ id, tag_name, target, title, body, draft, prerelease, html_url, author, created_
 
 ## Pagination
 
-None of the list tools auto-paginate. To collect a full result set, call with `page: 1`, then
-`page: 2`, etc., stopping when a page returns fewer items than `per_page`. `list_releases` and
-`list_tags` default `per_page` to 20 — lower than the 30-default used by most other gitea-mcp list
-tools, so a caller assuming 30 will under-count pages needed for a fixed total.
+Nothing auto-paginates. Loop `page: 1, 2, ...` until a page returns fewer items than `per_page`.
+`list_releases`/`list_tags` default `per_page` to 20, not the usual 30 — assuming 30 under-counts
+pages needed.