Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
49d21bcb4dd280b8cf1e785fa37648d6ff616feb
holocron/plugins/gitea/skills/gitea-workflow/references/sources.md
Defame1297 38f1ba4e03 fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery 
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
2026-08-13 16:59:03 +00:00

2.0 KiB
Raw Blame History

Sources

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. This skill's status view relies on list_issues/list_pull_requests semantics (via gitea-issues/gitea-prs), and its ambiguous-number resolution relies on issue_read's is_pull field, both verified against this source at authoring time.
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: SKILL.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 — confirms is_pull is present on a single-item issue_read response, the field this skill's resolution step depends on to distinguish an issue from a PR sharing the same number.
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: SKILL.md
  • Status: extracted

context7-websites-gitea

  • URL: context7:/websites/gitea
  • Description: Official Gitea docs mirror on Context7 — confirms issues and pull requests share a single per-repository number sequence, and that Gitea returns 404 for permission failures rather than a distinct 403, both facts this skill's resolution and error-handling steps depend on.
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: SKILL.md
  • Status: extracted

context7-gitea-tea-cli

  • URL: context7:/git_gitea_com/gitea_tea
  • Description: Official tea CLI docs on Context7 — practitioner conventions for issues, PRs, and releases. Consulted as part of the shared research pass but its content is domain-specific (PR/release workflow patterns), out of scope for pure status/routing behavior — no content from it was used in this skill.
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: (none)
  • Status: extracted
Reference in New Issue View Git Blame Copy Permalink