Defame1297
38f1ba4e03
Claude Code's (and Copilot's) native plugin installer has zero awareness of .apm/ nesting -- it convention-scans only flat skills/, agents/, commands/, hooks.json at each plugin's root. Confirmed via strings on the installed claude binary and live installs of git@holocron/gitea@holocron/kyberforge@ holocron, all reporting Skills(0) Agents(0) Hooks(0) post ADR-0015's apm conversion. Root cause (apm_cli/core/plugin_manifest.py): apm's plugin.json compiler deliberately strips skills/agents/commands keys, assuming the host already auto-discovers those convention directories -- it has no model of .apm/ being host-visible at all. Separately, apm's own bundle exporter (apm_cli/bundle/plugin_exporter.py, behind `apm pack --format plugin`) implements the correct .apm/ -> flat mapping, but only ever targeted build/<name>-<version>/, a path nothing in marketplace.json's source: points at. scripts/sync-plugin-content.sh wraps that bundle exporter and copies its agents/, skills/, commands/, instructions/, extensions/, and merged hooks.json back into each plugin's own root as a second tracked compiled-output category -- same governance status as .claude-plugin/plugin.json: generated from .apm/, never hand-edited. tests/ subdirectories are excluded from the mirror (dev fixtures, not host-visible runtime content; several hardcode a relative repo-root walk-up sized for the .apm/-nested depth, which breaks when duplicated one level shallower). Applied for real across all 6 plugins and verified two ways: `claude plugin validate --strict` passes on every real plugin directory, and a live `claude --plugin-dir <path> -p "list skills/agents"` behavioral test confirms content is now actually discovered. Also, from the same issue #90 review round: - scripts/check-manifests.sh pointed at each plugin's root-level plugin.json (checking skills/hooks/mcpServers/agents pointer fields) -- that file was a stale near-duplicate of .claude-plugin/plugin.json nothing else read or wrote, now deleted across all 6 plugins. check-manifests.sh is rewritten to validate .claude-plugin/plugin.json instead, and drops the pointer-field checks entirely (nothing to check -- those fields are correctly absent by design). Content-presence drift is now check-plugin-content-sync's job, a new pre-push hook wired in .pre-commit-config.yaml. docs/adr/0017 records the root cause and decision in full, including two rejected alternatives (patching plugin.json's path fields directly -- apm's compiler strips them on every run; pointing marketplace.json at apm pack's build/ output -- a version-suffixed non-source directory nothing can install from without an extra build step). ADR-0015 and CONTEXT.md are updated to point at it. Refs: #90
3.9 KiB
topic, source_keys
| topic | source_keys | ||
|---|---|---|---|
| call-signatures |
|
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 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
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. 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_releasesif 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) - Assumed (not confirmed by the research docs) that if
tag_namedoesn't already exist as a tag, Gitea creates it againsttargetas part of this call. Verify withget_tag/list_tagsafterward if the caller needs certainty.
delete_release
- Required:
id(number) — same numeric id asget_release. Does not accepttag_name. - Does not delete the underlying tag.
Release object shape (returned by list/get/create/latest):
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 }— nomessagefield on list responses.
get_tag
- Required:
tag_name(string) - Returns
{ name, message, commit_sha }— the only tag call that returnsmessage.
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 explicitdelete_releasecall assuming the release survives. Verify withlist_releases/get_releaseafter callingdelete_tagrather 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.