Files

Defame1297 78015893d4 refactor(gitea-issues): retrofit to the ADR-0020 context contract

Description 827 -> 182 chars, body 902 -> 584 words, Gotchas 7 entries/43% of
body -> 4/23.1%. Clears both size FAILs, the dangling-target FAIL and the Vale
CompositionNote error.

The dangling 'gitea-labels' target is gone with the composition sentence that
carried it -- a YAML fold artifact, not a typo: the '>'-folded scalar joined
'gitea-labels-' and 'milestones' across a line break, leaving the name terminal
and danglable. Both boundary names now sit whole on one source line each, and
both resolve.

Cut the second trigger register, the seven-verb capability enumeration, the
issue_write implementation detail and a gitea-branches boundary that defended
nothing. Two Gotchas deleted as spec restatement carried in references/, one as
a paraphrase of the step below it.

Closes a capability hole rather than papering over it: gitea-labels-milestones
routes label application here and has no issue_write, but no dispatch row
existed for add/replace/remove/clear_labels or get_labels. Both rows added.
The label ID/name Gotcha is now stated per method -- issue_write takes IDs,
list_issues and search_issues filter by name, issue_read 'get' returns names
but 'get_labels' returns full objects with IDs.

Drops a stale quotation of gitea-labels-milestones' description from
references/enrichments.md; that string went with its composition note.

Refs #99

2026-08-30 12:28:54 +00:00

2.6 KiB

Raw Blame History

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).

gitea-mcp-repo

URL: https://gitea.com/gitea/gitea-mcp
Description: Official gitea-mcp repository (v1.3.0); operation/*.go source files documenting all 55 MCP tools, their parameters, and CLI flags.
Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
Contributing files: SKILL.md, references/issues.md, references/search.md, references/enrichments.md
Status: extracted

gitea-mcp-slim-go

URL: https://gitea.com/gitea/gitea-mcp/raw/branch/main/operation/issue/slim.go
Description: Slim response shape structs from gitea-mcp source; defines exactly which fields the MCP server returns for issues (label name-vs-ID slimming, milestone object-vs-string shape, is_pull presence on single-item reads only).
Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
Contributing files: SKILL.md, references/issues.md
Status: extracted

context7-websites-gitea

URL: context7:/websites/gitea
Description: Official Gitea docs mirror on Context7 (docs.gitea.com content) — backs the automatic cross-reference rendering (#N/!N) that validates the "Depends on #N" dependency-linking convention.
Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
Contributing files: references/enrichments.md
Status: extracted

context7-gitea-tea-cli

URL: context7:/git_gitea_com/gitea_tea
Description: Official tea CLI (reference Gitea client) docs on Context7 — practitioner command patterns for issues, PRs, and releases. Consulted alongside context7-websites-gitea while researching workflow-conventions.md's cross-reference-linking section (both sources contribute to that research doc); its issue-specific command patterns did not end up informing any gitea-issues content beyond what context7-websites-gitea already backs.
Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
Contributing files: (none)
Status: extracted

2.6 KiB Raw Blame History