Defame1297
095929142f
No wave on this branch bumped a version across 56 commits, though apm-workflow's own configure.md states the policy: bump a package's apm.yml version: whenever anything reaching its compiled output changes. All six local packages have substantive .apm/ edits here. Minor rather than patch. The retrofit rewrote every skill description, which is the routing surface a caller matches against, and redistributed bodies into references/. Behaviour is preserved but discovery changes, so this is more than a fix. The same file is explicit that versions are per package — editing plugins/foo/.apm/ never bumps plugins/bar — so this is six independent bumps that happen to land together, not one release number. Under the per_package strategy the catalog carries a second copy in marketplace.packages[], and apm-marketplace-check fails the push when the two disagree; it cannot see a bump skipped in both, which is the state the branch was in. executables.allow is version-pinned by apm's design and moves with kyberforge, or the SessionStart hook silently stops deploying (ADR-0019). The comment above that block predicted exactly this; the pre-push suite caught it when the first bump orphaned the key. Refs #99
bin
A place for things to be binned
Install
Claude Code:
claude plugin marketplace add <owner>/<repo>
claude plugin install bin@<marketplace-name>
GitHub Copilot CLI:
copilot plugin marketplace add <owner>/<repo>
copilot plugin install bin
Local (development):
# Claude Code
claude --plugin-dir ./plugins/bin
# GitHub Copilot CLI
copilot plugin install ./plugins/bin
Contents
| Component | Path | Description |
|---|---|---|
| Skills | .apm/skills/ → skills/ |
Slash commands available after install |
| MCP servers | .mcp.json |
The obsidian server (npx @bitbonsai/mcpvault@0.15.0 docs/), hand-authored at the plugin root |
.apm/ is the authoring source; skills/ is the generated mirror plugin hosts scan (ADR-0017). This plugin ships no agents. It is the only plugin here with a non-empty .mcp.json, which is why its compiled manifests are the only ones carrying an mcpServers block.
The two compiled manifests get that block by different routes. .claude-plugin/plugin.json gets it from apm itself: build_plugin_manifest's Claude branch calls collect_mcp_servers, which reads .mcp.json, sanitizes it, and inlines the resulting server objects. .github/plugin/plugin.json gets nothing from apm — the Copilot branch drops the field — so scripts/sync-plugin-content.sh's reinject_mcp_servers() puts it back, as the string ".mcp.json" rather than the resolved objects. Copilot's manifest schema types the field as "string or object — MCP server config path or inline definitions", and a path reference cannot carry a credential into a committed manifest. See ADR-0017's mcpServers amendment.
Author
Defame1297