Defame1297
06b01f8afc
- say apm hook/instruction/prompt so pre-commit hooks stay with pc-author - restore the idea-without-a-home trigger - cite checkpoints forge's apm routes actually hit - diff version bumps against the remote default branch Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi
2.3 KiB
source_keys
| source_keys | |
|---|---|
|
Routing a plugin or marketplace entry to apm-workflow
Reached from SKILL.md Step 2 when the classified artifact is a plugin or a marketplace entry.
Both route to apm-workflow — a plugin to its configure flow (apm plugin init), a marketplace
entry to its marketplace flow (apm marketplace package add).
No other skill is a candidate for these two rows: plugin-author and marketplace-author were
removed per ADR-0015 once issue #90 landed, and apm-workflow is their sole successor.
Always inline, never forked
Run these routes inline, in the current conversation. Their flows are short, prompt-heavy or
gated — editing a package's manifest metadata republishes its public plugin.json description,
and removing a marketplace entry takes a conversational confirmation before apm pack changes the
consumed catalog — and a backgrounded fork cannot surface those checkpoints to the user in real
time.
No clean-context recheck, and no automatic audit
Skill, agent, and hook, instruction or prompt routes close with a clean-context audit rerun; these two do not, and the omission is deliberate rather than an oversight. Neither artifact type has an audit skill counterpart to re-run, so detaching the route to earn a recheck it would never get buys nothing.
These routes get no automated terminal check either. apm audit is a separate action on
apm-workflow's own dispatch table, not a closing step of the configure or marketplace flow a
forge route lands in, so a completion message from either says nothing about it. Do not wait for
one and do not report one you did not see.
Verify by hand instead. Read back what the route wrote against what the grill settled:
- Plugin — the package directory exists where the intent said it should, and its
apm.ymlcarries the intendedname, a top-leveltype:field, and aversion. - Marketplace entry — the entry names that package, points at the source the intent settled on, and carries the version the package actually declares.
If the change warrants the full integrity and policy check rather than a read-back, invoke
apm-workflow again for its audit action and run apm audit deliberately. Then return to
SKILL.md Step 3 for the closing gates common to every route.