akm-cli 0.9.30 → 0.9.31

package/docs/migration/release-notes/0.2.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.2.0
+# akm v0.2.0 migration notes
 
 - Asset refs are user-facing `type:name` values; do not rely on URI-style refs.
 - The old fixed asset-type union was replaced by an extensible asset type system.

package/docs/migration/release-notes/0.3.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.3.0
+# akm v0.3.0 migration notes
 
 - The old `stash` and `kit` command groups were folded into the top-level CLI.
 - Use `akm add`, `akm list`, and `akm remove` instead of the older split command surfaces.

package/docs/migration/release-notes/0.5.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.5.0
+# akm v0.5.0 migration notes
 
 - New top-level surfaces: `akm wiki …`, `akm workflow …`, `akm vault …`, and `akm save`.
 - If you tried the unreleased single-wiki LLM prototype, move to the new `akm wiki …` workflow.

package/docs/migration/release-notes/0.6.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.6.0
+# akm v0.6.0 migration notes
 
 This release ships the v1 architecture refactor on top of the earlier 0.6
 terminology cut (`kit` → `stash` in the registry wire format). The CLI

package/docs/migration/release-notes/0.7.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.7.0
+# akm v0.7.0 migration notes
 
 0.7.0 is the last pre-1.0 ship in the v1 cycle. It introduces the
 proposal queue, agent reflection commands, the `lesson` asset type, the

package/docs/migration/release-notes/0.7.3.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.7.3
+# akm v0.7.3 migration notes
 
 0.7.3 includes stability improvements, security hardening, and UX refinements. Key changes include:
 
@@ -13,4 +13,4 @@ Migration notes for akm v0.7.3
 - **`.stash.json` no longer drives incremental stale detection** — editing `.stash.json` alone no longer forces directories to rescan during incremental indexing.
 - **One-shot URL ingest for `akm import` and `akm wiki stash`** — both commands now accept a single HTTP/HTTPS URL in addition to file paths and stdin. `akm import <url>` fetches the exact page, converts it to markdown, and writes it into `knowledge/` using a URL-path-derived default name. `akm wiki stash <wiki> <url>` fetches the exact page, converts it to markdown, and writes it into `wikis/<wiki>/raw/`. Neither command registers a persistent website source or crawls linked pages.
 
-For stash authors on the 0.7.x pre-release line: `.stash.json` remains supported for compatibility in this release, but it is deprecated and will be removed in v0.8.0. That timeline is intentional: during this aggressive pre-release phase-out window, compatibility shims do not stay around until 1.0 unless they still earn their cost. Prefer frontmatter for markdown assets and structured code comments for scripts, and migrate any remaining `.stash.json` metadata before taking the 0.8 upgrade.
+For stash authors on the 0.7.x pre-release line: `.stash.json` remains supported for compatibility in this release, but it is deprecated and will be removed in v0.8.0. That timeline is intentional: during this aggressive pre-release phase-out window, compatibility shims do not stay around until 1.0 unless they still earn their cost. Prefer frontmatter for markdown assets and structured code comments for scripts, and migrate any remaining `.stash.json` metadata before taking the 0.8 upgrade.

package/docs/migration/release-notes/0.7.4.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.7.4
+# akm v0.7.4 migration notes
 
 This is a patch release that fixes the publish process. No functional changes from v0.7.3.
 

package/docs/migration/release-notes/0.7.5.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.7.5
+# akm v0.7.5 migration notes
 
 0.7.5 is a patch release that rolls up all changes shipped on `main` after v0.7.4.
 

package/docs/migration/release-notes/0.8.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.8.0
+# akm v0.8.0 migration notes
 
 This release combines the 0.8.0 CLI/storage break with the final improve-owned
 maintenance migration work that landed before release validation closed.

package/docs/migration/release-notes/0.9.0.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.0
+# akm v0.9.0 migration notes
 
 These notes apply to the 0.9.0 release candidates and final release. If you
 were already running a 0.9.0 beta, align scripts, prompts, and stash layout

package/docs/migration/release-notes/0.9.14.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.14
+# akm v0.9.14 migration notes
 
 The derived `index.db` generation changes from v22 to v23 to support lexical
 Markdown fragments. On the first normal read after upgrade, akm detects that

package/docs/migration/release-notes/0.9.15.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.15
+# akm v0.9.15 migration notes
 
 `RUN_LEASE_HELD` (a workflow run-lease refusal) and the new
 `STATE_DB_CONTENDED` (state.db write contention) now exit 75 (`EX_TEMPFAIL`)

package/docs/migration/release-notes/0.9.16.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.16
+# akm v0.9.16 migration notes
 
 Scheduled execution is now authorized by host-local config and bound to the
 specific source installed under a bundle id. Existing

package/docs/migration/release-notes/0.9.17.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.17
+# akm v0.9.17 migration notes
 
 Run this after upgrading:
 

package/docs/migration/release-notes/0.9.19.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.19
+# akm v0.9.19 migration notes
 
 Nothing has to run after upgrading from 0.9.18: 0.9.19 adds no config keys,
 changes no index layout, adds no state.db migration and leaves scheduler rows

package/docs/migration/release-notes/0.9.2.md

@@ -1,4 +1,4 @@
-Migration notes for akm v0.9.2
+# akm v0.9.2 migration notes
 
 Exact-prefix additive `state.db` upgrades remain automatic. The released
 historical migration 018 is classified separately because it removes retired

package/docs/migration/release-notes/README.md

@@ -7,40 +7,36 @@ live one level up in `docs/migration/`.
 
 ## Available notes
 
-- [0.9.19](0.9.19.md) — `akm improve` planning only the bundle it writes to
-  (a scheduled run needs one `--bundle` run per other bundle),
-  `akm proposal reopen` and the retire-proposal diff, consolidate's coverage
-  check and content-driven hold on decided promotions, distill's grounding
-  check, and what a downgrade to 0.9.18 undoes
-- [0.9.17](0.9.17.md) — consolidate's retire proposals and continuity check,
-  promotions archiving their source memory, declared links replacing the LLM
-  entity graph, index layout 26, scheduler rows carrying their own context,
-  and `akm improve` scoped to what retrieval actually returns
-- [0.9.16](0.9.16.md) — source-bound scheduler grants, local execution
-  authority, config inheritance's portable-data boundary, and split unsafe
-  overrides
-- [0.9.15](0.9.15.md) — exit-code 75 for lease/state.db contention,
-  `--require-engines` scheduled task templates, `--no-probe` cli-version
-  skip, thinking-control wire forms, embedding re-embed safety and
-  cross-rebuild vector salvage, launcher signal forwarding, a default
-  per-document embedding cap, and `extends` config inheritance
-- [0.9.14](0.9.14.md) — index v22-to-v23 derived-cache rebuild, lexical
-  fragments, and collapse-detector canary re-minting
-- [0.9.2](0.9.2.md) — task source v4 migration, workflow source IR v1 and
-  durable-v4-family `irVersion: 5`, command diagnostics, and strategy judgment
-  migration
+- [0.9.19](0.9.19.md) — Bundle-scoped improve planning, proposal reopen, and consolidate/distill guardrails.
+- [0.9.17](0.9.17.md) — Retire proposals, declared links replacing the LLM entity graph, and scoped improve planning.
+- [0.9.16](0.9.16.md) — Source-bound scheduler grants, local execution authority, and split unsafe overrides.
+- [0.9.15](0.9.15.md) — Lease/state.db contention exit code 75, scheduled-task engine requirements, and safer launchers.
+- [0.9.14](0.9.14.md) — Index v22→v23 derived-cache rebuild, lexical fragments, and collapse-detector canaries.
+- [0.9.2](0.9.2.md) — Task source v4 migration, workflow source IR v1, and durable-v4-family `irVersion: 5`.
+- [0.9.0](0.9.0.md) — 0.9 release-candidate and final-release migration notes.
+- [0.8.0](0.8.0.md) — CLI/storage break, improve-owned graph pipeline, config v2, and task assets.
+- [0.7.5](0.7.5.md) — Patch rollup for everything shipped on `main` after v0.7.4.
+- [0.7.4](0.7.4.md) — Publish-process-only patch release with no functional change from 0.7.3.
+- [0.7.3](0.7.3.md) — Stability improvements, security hardening, and UX refinements.
+- [0.7.0](0.7.0.md) — Last v1-cycle pre-1.0 release with the proposal queue and improve-loop groundwork.
+- [0.6.0](0.6.0.md) — v1 architecture refactor, stash rename cleanup, and sandbox/setup guidance.
+- [0.5.0](0.5.0.md) — Wiki, workflow, vault, and save command additions before the 0.6 architecture cut.
+- [0.3.0](0.3.0.md) — Fold the old `stash` and `kit` command groups into the top-level CLI.
+- [0.2.0](0.2.0.md) — User-facing `type:name` refs and early bundle conventions.
+- [0.1.0](0.1.0.md) — Rebrand from Agent-i-Kit to akm.
+- [0.0.13](0.0.13.md) — Initial public release.
 
 ## Adding notes for a new release
 
 1. Create `<version>.md` in this directory (e.g. `0.7.0.md`).
-2. Write plain text — the content is printed verbatim. Start the body
-   with a line like `Migration notes for akm v0.7.0`, then list the
-   automatic migrations, manual actions, publisher changes, etc.
-3. The file ships with the published package via `package.json` →
-   `files[]` and is resolved at runtime from either `src/` or `dist/`,
-   so no code change is required.
+2. Start the file with `# akm v<version> migration notes`, then list the
+   automatic migrations, manual actions, publisher changes, and any longform
+   guide links the terminal user may need.
+3. The file ships with the published package via `package.json` → `files[]`
+   and is resolved at runtime from either `src/` or `dist/`, so no code
+   change is required.
 4. Link to the longform guide in the last paragraph if one exists.
 
-Keep each note self-contained: it should tell a user everything they
-need to upgrade without requiring them to open a browser (the longform
-guide link is the last resort, not the first).
+Keep each note self-contained: it should tell a user everything they need to
+upgrade without requiring them to open a browser (the longform guide link is
+the last resort, not the first).