Files
holocron/plugins/kyberforge/skills/apm-workflow/references/install.md
Defame1297 394052ff66 docs(kyberforge): fix remaining PR #91 review findings, add apm install routing
Re-review (comment 24) of fix commit e16c3dc found six new issues, mostly
introduced by that fix commit itself: a dangling reference to a Hard Rule
bullet the same commit deleted (apm-orchestrate.md/.agent.md Process step
2 still named "secret indirection"), and an ADR-0015 Decision bullet that
claimed "this ADR does not update CONTEXT.md" while the same commit had
just added a forward-pointer sentence to CONTEXT.md's Plugin/Plugin
marketplace entries. Both reworded to match what actually happened.

apm-install's APM_INSTALL_DIR escape-hatch example dropped the curl pipe
entirely (`APM_INSTALL_DIR=... sh` with nothing piped into it) — fixed in
both apm-install/SKILL.md and the installation.md research doc, verified
against the upstream Microsoft APM docs via Context7.

Neither apm-workflow nor apm-orchestrate routed to plain `apm install
[PACKAGE_REF]`, the CLI command that actually resolves/fetches
dependencies declared in apm.yml — apm-install only bootstraps the apm
binary/runtime, not per-package deps. Added a 5th "install" dispatch
action to apm-workflow (new references/install.md, SKILL.md table row,
README usage/files sync, sources.md provenance entry) and a matching
"install" operation group on apm-orchestrate so it can route there.

configure.md's apm.yml schema block was also missing the "legacy singular
`target:` CSV form is still accepted" caveat its sibling research doc
documents for the same field — added for consistency.

The sixth finding (paired .md/.agent.md Output-contract disagreement) was
checked against git-orchestrate and gitea-orchestrate's existing pairs and
found to match established repo convention (JSON schema in .md, prose
summary without the enum in .agent.md) — left unchanged as a false
positive rather than "fixed."

kyberforge bumped 1.3.0 -> 1.3.1 via agent-author's normal improve flow.

Refs: #91

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0186ERbyACLRuRxPRnqwpa4m
2026-08-11 11:09:43 +00:00

1.3 KiB

topic, source_keys
topic source_keys
install
context7-microsoft-apm

apm install

apm install                            # resolve/install everything in apm.yml against apm.lock.yaml
apm install acme/internal-tools#^1.0.0  # install and add this dependency
apm install --update                    # re-resolve; accept new upstream content even if it doesn't match the lockfile hash
apm install --target agent-skills       # emit a vendor-neutral output dir instead of a harness-specific one

With no arguments, resolves and installs everything declared under dependencies:/devDependencies: in apm.yml against apm.lock.yaml. One or more PACKAGE_REF arguments (any of the forms in references/configure.md's "Dependency reference forms" — pinned tag, plain repo, single primitive, raw git URL, git:/path:/ref: object, or local relative path) install that dependency and add it to apm.yml.

--update is the escape hatch for a lockfile hash mismatch against upstream — normal apm install treats that as drift and won't silently accept it; see references/audit.md for the CI-side check (apm install --frozen) that fails instead of re-resolving.

--target agent-skills generates the vendor-neutral output directory instead of a Claude/Copilot-specific one — for IDE-agnostic tool support.