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
42 lines
2.6 KiB
Markdown
42 lines
2.6 KiB
Markdown
# 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 SKILL.md Gotchas — 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`
|