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
2.4 KiB
2.4 KiB