598a7c326a
Retrofits all 39 skills to ADR-0020's description/body context contract, then fixes what six rounds of independent review found in that retrofit — including four ways the hot gate itself failed open. Closes #99, #107, #108, #110, #111, #114, #115, #120. ## The retrofit (waves 1-5) | | Start | Now | |---|---|---| | Description FAILs (>400 chars) | 26 | **0** | | Body FAILs (>900 words, body-only) | 9 | **0** | | Dangling routing targets | 2 | **0** | | `Kyberforge.CompositionNote` | 10 | **0** | | Preload tax | 21,005 chars | **~10,500** | Under the 12,000-char success criterion. Per-wave detail is on #99. ## The review fixes **The gate failed open four ways, three of them found after the retrofit shipped.** An unrecognised follower token made a dangling target vanish. A skill directory with no `SKILL.md` resolved as a valid target, so a commit could be green locally and red in a fresh clone — three existing fixtures were relying on that, one of which made the install-leak A/B pass vacuously. Then the free-standing `/name` sweep turned out to be gated on the sentence carrying a boundary marker, so route notation in any other sentence was invisible — not an ERROR, not a SUGGESTION, not an INFO — which left the documented "`/name` always blocks" promise false from a second direction. All four fixed and pinned. **Two checks were silently not running.** `validate-provenance.sh` checks 7-8 were dead across nine skills. Waking them exposed a deeper problem: they assume `Research doc:` names a source index, but 30 of 121 entries point at topic content documents, so every new check-7 INFO was a false positive and check 8 was saved from a false-FAIL flood only by an *unannounced* skip. Checks 7/8 are now scoped to source indexes and every skip announces itself (#121). **The retrofit's own anti-goal, four times.** ADR-0020 warns that a blunt gate gets satisfied by deleting content rather than relocating it. `diagnose` and `skill-audit` relocated prose and then read it unconditionally; `prototype` and `vale-config` deleted rules outright that survived nowhere. All four addressed. ## Verification - `bash tests/run-tests.sh --strict` — 24 suites, 0 skipped, 0 failed - `bash tests/run-bats.sh` — 325 tests, 0 failures - `pre-commit run --all-files` — 17/17 - `pre-commit run --hook-stage pre-push --all-files` — 16/16, with `apm marketplace check` and `apm pack --check-clean` run against the remote, not skipped - `scripts/skill-size-check.sh` over all 39 skills — rc 0, 0 ERROR/FAIL, SUGGESTION-only - Preload tax measured at **10,498 chars**, max description 390 — both inside budget - Every new test proven non-vacuous by a deliberate mutation of the behaviour it covers **Per-commit sync, stated accurately:** the ten commits from the latest review round each pass `check-plugin-content-sync` in isolation, verified by checking each out in a detached worktree with a clean between. The earlier gitea window (`dfacf05..bedbd1d`, nine commits) does **not** — its mirror was regenerated in one batch at `bbc7300`. An earlier revision of this description claimed the property held for every commit; it does not, and a bisect through that window lands on a red commit. **Squash-merge** to collapse it, or accept that this range is not bisectable. ## Version bump Six plugins and the catalog take a **patch**, not a minor. The branch is **89 commits — 40 `fix` / 30 `refactor` / 12 `docs` / 5 `chore` / 2 `test` — zero `feat`, zero `!`, zero `BREAKING CHANGE`** — and adds no skill, agent, command or hook. (Two earlier revisions of this section cited a stale histogram, most recently 78 commits; the figures above are measured at HEAD.) Both rules this repo ships (`forge/references/version-bump.md`, landing in this PR, and `git-commits/references/conventional-commits-spec.md`) make that a patch, and the catalog set is unchanged at 7 entries. Not settled by that: four published files were removed from the installed tree, three moved, and `caveman` gained `disable-model-invocation`, retiring its old triggers. Under a strict reading those are major-class and currently ship under `refactor:` with no marker. Whether the deployed skill surface is a public contract is written down nowhere — worth deciding, but it outlives this PR. ## Deliberately not in scope #112 (cherry-pick ownership, now resolved in favour of `git-commits`), #113 (`rtk git` normalisation), #116 (research fan-out), #101 (audit-skill merge), #122 (non-spec skill-root files), #123 (no PRD producer) stay open. #117 is the one worth reading: the contract's remedy is to move prose into `references/`, which is exactly where neither the size gate nor Vale looks — and the blind spot is wider than #117 currently records, since there is no root `.vale.ini` at all, so every ADR, `CONTEXT.md` and `README.md` is unlinted too. That blind spot let this branch carry two `level: error` `Kyberforge.SentenceOpenerThereIs` violations into `references/` files it created — `provider-adapter-author/references/provider-matrix.md:31` and `agent-audit/references/finding-criteria.md:95`. Both are reworded in `afadaae`, confirmed by routing each file through the audit's own `vale-wrap.sh` (1 error each before, 0 after). Five further occurrences sit in `references/` files already on `main`; those are the pre-existing corpus and stay with #117, which is the real fix. Also unfixed and not this PR's: `apm install` appends a duplicate `SessionStart` entry to `.claude/settings.json`, so a fresh clone cannot get pre-push green without an edit AGENTS.md warns against. Reproduces identically on `main`. Co-authored-by: Defame1297 <gitea@rkdr.net> Reviewed-on: https://git.dev.rkdr.net/Defame1297/holocron/pulls/129 Co-authored-by: Claude Code AI - Gitea MCP <claude@noreply.git.dev.rkdr.net> Co-committed-by: Claude Code AI - Gitea MCP <claude@noreply.git.dev.rkdr.net>
77 lines
4.1 KiB
Markdown
77 lines
4.1 KiB
Markdown
---
|
|
topic: call-signatures
|
|
source_keys:
|
|
- gitea-mcp-repo
|
|
- gitea-mcp-slim-go
|
|
---
|
|
|
|
# Release and tag call signatures
|
|
|
|
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 all 9 tools here were additionally cross-checked live via `ToolSearch`
|
|
against the deployed `mcp__gitea__*` tools and confirmed to match exactly — required and optional
|
|
params, names, and defaults. Last verified against gitea-mcp **v1.7.0**, as reported by
|
|
`get_gitea_mcp_server_version`. That check covers input params only: the response shapes below
|
|
remain source-derived, not live-verified, so re-verify them if a response reads differently than
|
|
documented here.
|
|
|
|
`owner` and `repo` are required strings on every tool below and are omitted from the per-tool lists
|
|
for brevity.
|
|
|
|
## Releases
|
|
|
|
**`list_releases`**
|
|
- Optional: `is_draft` (boolean), `is_pre_release` (boolean), `page` (number, default 1), `per_page` (number, default 20)
|
|
- Returns an array of release objects (shape below), one page at a time.
|
|
|
|
**`get_release`**
|
|
- Required: `id` (number) — the release's numeric id, not its tag name.
|
|
- Returns a single release object.
|
|
|
|
**`get_latest_release`**
|
|
- No parameters beyond `owner`/`repo`.
|
|
- Returns a single release object for the most recently published release. The deployed tool's own description reads "the most recent published (non-draft) release" — it names drafts as excluded and is silent on prereleases, so whether prereleases are also excluded is *unconfirmed*; verify with `list_releases` if the caller depends on it. Either way a release created without `is_pre_release: true` is eligible, which is why that flag has to be set in the create call (see `conventions.md`).
|
|
|
|
**`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)
|
|
- 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`.
|
|
- Does not delete the underlying tag.
|
|
|
|
**Release object shape** (returned by list/get/create/latest):
|
|
```text
|
|
id, tag_name, target, title, body, draft, prerelease, html_url, author, created_at, published_at
|
|
```
|
|
`author` is the creator's login. `body` holds the release notes.
|
|
|
|
## Tags
|
|
|
|
**`list_tags`**
|
|
- Optional: `page` (number, default 1), `per_page` (number, default 20)
|
|
- Returns an array of `{ name, commit_sha }` — no `message` field on list responses.
|
|
|
|
**`get_tag`**
|
|
- Required: `tag_name` (string)
|
|
- Returns `{ name, message, commit_sha }` — the only tag call that returns `message`.
|
|
|
|
**`create_tag`**
|
|
- Required: `tag_name` (string)
|
|
- Optional: `target` (string — commitish to tag; if omitted, Gitea tags the default branch tip), `message` (string — annotated tag message)
|
|
|
|
**`delete_tag`**
|
|
- Required: `tag_name` (string). Does not accept a numeric id.
|
|
- 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
|
|
|
|
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.
|