fix(gitea): correct is_draft param and soften unverified claims in gitea-releases docs

An audit against plugins/gitea/docs/research/docs/gitea/*.md found the
gitea-releases skill told callers to set create_release's draft flag
as `draft` instead of `is_draft` (the actual input param; `draft` is
only the response field name) - a call following that gotcha would
have the flag silently ignored, publishing a non-draft release.

Also corrected an overclaimed "verified against live MCP schema"
provenance note in call-signatures.md/README.md (its sources are
gitea-mcp source-code extraction, not a live tool call - now noted
alongside a narrow live ToolSearch cross-check performed this session
for 3 of the 9 tools' input params), and softened three behavioral
claims (create_release auto-creating tags, get_latest_release
excluding drafts/prereleases, delete_tag preserving a wrapping
release) that don't trace to any research doc, with a recommendation
to verify release/tag state after delete operations rather than
assume it.

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

@@ -7,9 +7,18 @@ source_keys:
 
 # Release and tag call signatures
 
-Verified against the live MCP tool schemas at authoring time (not copied from upstream API docs,
-which can drift from the deployed gitea-mcp version). `owner` and `repo` are required strings on
-every tool below and are omitted from the per-tool lists for brevity.
+Signatures and response shapes are derived from gitea-mcp source (`operation/*.go` and `slim.go`,
+see `references/sources.md`) rather than copied from upstream API docs, which can drift from the
+deployed gitea-mcp version — but this is a source-code extraction, not a live MCP tool call.
+
+Input parameter schemas for 3 of the 9 tools here — `create_release`, `delete_tag`, and
+`get_latest_release` — were additionally cross-checked live via `ToolSearch` against the deployed
+`mcp__gitea__*` tools in session 2026-07-05, and confirmed to match exactly (required/optional
+params and names). That check covered only input params for those 3 tools, not response shapes,
+and not the other 6 tools — treat the rest of this document as source-derived, not live-verified.
+
+`owner` and `repo` are required strings on every tool below and are omitted from the per-tool lists
+for brevity.
 
 ## Releases
 
@@ -23,12 +32,12 @@ every tool below and are omitted from the per-tool lists for brevity.
 
 **`get_latest_release`**
 - No parameters beyond `owner`/`repo`.
-- Returns a single release object for the most recently published (non-draft, non-prerelease by Gitea's own "latest" definition) release.
+- Returns a single release object for the most recently published release. It is assumed (by analogy with typical "latest release" semantics) that this excludes drafts and prereleases, but that exclusion is not directly confirmed by any of the research docs — verify with `list_releases` if the caller depends on this.
 
 **`create_release`**
 - Required: `tag_name` (string), `target` (string — branch, tag, or commit SHA to cut the tag from), `title` (string)
 - Optional: `body` (string — release notes), `is_draft` (boolean), `is_pre_release` (boolean)
-- If `tag_name` doesn't already exist as a tag, Gitea creates it against `target` as part of this call.
+- Assumed (not confirmed by the research docs) that if `tag_name` doesn't already exist as a tag, Gitea creates it against `target` as part of this call. Verify with `get_tag`/`list_tags` afterward if the caller needs certainty.
 
 **`delete_release`**
 - Required: `id` (number) — same numeric id as `get_release`. Does not accept `tag_name`.
@@ -56,7 +65,7 @@ id, tag_name, target, title, body, draft, prerelease, html_url, author, created_
 
 **`delete_tag`**
 - Required: `tag_name` (string). Does not accept a numeric id.
-- Does not delete any release wrapping the tag.
+- Assumed by symmetry with `delete_release` (documented above as not deleting the underlying tag) to also not delete any release wrapping the tag — but this reverse direction is not independently confirmed by the research docs, and is the more dangerous direction to get wrong: an agent might skip an explicit `delete_release` call assuming the release survives. Verify with `list_releases`/`get_release` after calling `delete_tag` rather than assume.
 
 ## Pagination
 

plugins/gitea/skills/gitea-releases/references/conventions.md

@@ -27,11 +27,15 @@ caller-supplied tag name against semver; just pass it through.
 
 ## Draft and prerelease are explicit flags
 
-`draft` and `is_pre_release`/`prerelease` are booleans the caller sets directly on `create_release`
-— Gitea does not infer either from the tag name, even though the `-beta`/`-rc` suffix convention
-above is commonly used to signal a prerelease to humans. When a user asks to "cut a beta" or
-"publish a release candidate," set `is_pre_release: true` explicitly in the same call rather than
-relying on the tag string to carry that meaning.
+`is_draft` and `is_pre_release` are booleans the caller sets directly on `create_release` — Gitea
+does not infer either from the tag name, even though the `-beta`/`-rc` suffix convention above is
+commonly used to signal a prerelease to humans. When a user asks to "cut a beta" or "publish a
+release candidate," set `is_pre_release: true` explicitly in the same call rather than relying on
+the tag string to carry that meaning.
+
+Note the input/output naming mismatch: the input param is `is_draft`, but the release object
+returned by the API uses `draft` (and `prerelease`) as the field names. `draft` is never a valid
+input key — passing `draft: true` to `create_release` is silently ignored rather than erroring.
 
 ## Release notes sourcing