fix(kyberforge): resolve PR #91 review findings in apm docs and orchestrators
Addresses 7 verified findings from the /code-review pass on PR #91's APM-conversion changes: - apm-workflow's description omitted install triggers, misrouting "install my apm dependencies" requests to apm-install instead - `apm marketplace check` was listed under both the marketplace and audit dispatch rows, breaking the "one reference file per action" contract; kept under marketplace.md, its real usage-sequence home - ADR-0015 claimed apm-workflow docs are generic/repo-agnostic while marketplace.md cited this repo's AGENTS.md and git-commits/ git-remotes skills by name; stripped the holocron-specific citations (marketplace.md, compile.md) so the claim now holds - plugin-author/marketplace-author are superseded per ADR-0015 with deletion deferred to #90; added deprecation notices pointing to the replacing apm-workflow dispatch actions - apm-orchestrate/gitea-orchestrate/git-orchestrate all instruct dispatch "via Skill" without granting the Skill tool; added it to all three - apm-orchestrate mandated strictly sequential fan-out across independent packages with no shared state; relaxed to permit parallel dispatch, matching this repo's own subagent-parallelization guidance Refs: #91
This commit is contained in:
@@ -4,13 +4,15 @@ description: >
|
||||
Use when the user wants to author or edit an apm.yml manifest
|
||||
(dependencies, scripts, compilation, policy, registries), scaffold a new
|
||||
apm package or marketplace (apm plugin init, apm marketplace init/package
|
||||
add), register a marketplace as a consumer, compile/pack/publish an apm
|
||||
package for distribution, or validate/audit apm.yml and installed content
|
||||
(apm audit, apm marketplace check) — even if the user doesn't say "apm"
|
||||
explicitly, e.g. "set up the package manifest", "scaffold this as an apm
|
||||
package", "build the distributable", "check this passes CI". Do not use
|
||||
for installing the apm binary itself or setting up an agent runtime — use
|
||||
apm-install for those.
|
||||
add), install or resolve dependencies declared in apm.yml (apm install,
|
||||
apm install [PACKAGE_REF]), register a marketplace as a consumer,
|
||||
compile/pack/publish an apm package for distribution, or validate/audit
|
||||
apm.yml and installed content (apm audit, apm marketplace check) — even if
|
||||
the user doesn't say "apm" explicitly, e.g. "set up the package manifest",
|
||||
"scaffold this as an apm package", "install my apm dependencies", "resolve
|
||||
apm.yml deps", "build the distributable", "check this passes CI". Do not
|
||||
use for installing the apm binary itself or setting up an agent runtime —
|
||||
use apm-install for those.
|
||||
metadata:
|
||||
category: apm
|
||||
source_keys:
|
||||
@@ -35,7 +37,7 @@ metadata:
|
||||
| `/apm-workflow install` | Resolve/fetch dependencies declared in `apm.yml` (`apm install`, `apm install [PACKAGE_REF]`) | `references/install.md` |
|
||||
| `/apm-workflow marketplace` | Build a marketplace, register packages into it, or register a marketplace as a consumer (`apm marketplace init/check/package add/add`) | `references/marketplace.md` |
|
||||
| `/apm-workflow compile` | Generate per-target output, bundle, or publish (`apm compile`, `apm pack`, `apm publish`) | `references/compile.md` |
|
||||
| `/apm-workflow audit` | Validate integrity/policy, wire a CI gate, or check marketplace refs resolve (`apm audit`, `apm audit --ci`, `apm marketplace check`) | `references/audit.md` |
|
||||
| `/apm-workflow audit` | Validate integrity/policy or wire a CI gate (`apm audit`, `apm audit --ci`) | `references/audit.md` |
|
||||
|
||||
Read only the reference file matching the requested action — each is self-contained for its concern.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user