akm-cli 0.9.0-rc.8 → 0.9.0

package/docs/migration/v0.7-to-v0.8.md

@@ -120,13 +120,13 @@ default was ON.
 akm improve
 
 # Opt in to legacy whole-batch auto-accept:
-akm improve --auto-accept=safe        # or --auto-accept=90
+akm improve --auto-accept=safe        # or --auto-accept=90 — doclint:ignore (0.8.0-only flag, removed in 0.9.0)
 
 # Opt in to a stricter threshold (no-op until confidence scoring lands):
-akm improve --auto-accept=95
+akm improve --auto-accept=95          # doclint:ignore (0.8.0-only flag, removed in 0.9.0)
 
 # Explicit OFF (matches the default; useful for self-documenting scripts):
-akm improve --auto-accept=false
+akm improve --auto-accept=false       # doclint:ignore (0.8.0-only flag, removed in 0.9.0)
 ```
 
 Review any scheduled `akm improve` tasks, agent prompts, or CI invocations
@@ -138,15 +138,15 @@ them before upgrading.
 The migration script is the canonical upgrade path. It is idempotent — safe to
 run more than once.
 
-The `akm-migrate-storage` binary ships alongside `akm` in the global install
+The `akm-migrate` binary ships alongside `akm` in the global install
 (both npm and prebuilt-binary distributions). Developers working from a
-source clone can run `bun scripts/migrate-storage.ts` instead — both invoke
-identical code.
+source clone can run `bun scripts/akm-migrate.ts storage` instead. The npm
+launcher requires Bun >= 1.0; the prebuilt migration binary is runtime-free.
 
 **Step 1 — preview:**
 
 ```sh
-akm-migrate-storage --dry-run
+akm-migrate storage --dry-run
 ```
 
 The dry run prints every file move and database import it would perform without
@@ -157,7 +157,7 @@ environment variables (see [New XDG directory layout](#new-xdg-directory-layout)
 **Step 2 — apply:**
 
 ```sh
-akm-migrate-storage --yes
+akm-migrate storage --yes
 ```
 
 The script performs these steps in order:
@@ -343,7 +343,7 @@ the old format:
 
 ```yaml
 schedule: "@weekly"
-command: akm improve --auto-accept=90 --limit 25
+command: akm improve --auto-accept=90 --limit 25  # doclint:ignore (0.8.0-only flag, removed in 0.9.0)
 enabled: true
 name: Weekly improve cycle
 description: Runs the improve pipeline against the full stash.
@@ -418,7 +418,7 @@ enabled: true
 **Step 3 — validate the new file:**
 
 ```sh
-akm tasks show weekly-review
+akm tasks show weekly-review  # doclint:ignore (0.8.0-era subcommand; inspection moved to `akm search`/`akm show` by 0.9.0)
 ```
 
 This command parses and prints the task. Any YAML errors or missing required
@@ -427,7 +427,7 @@ fields are reported here before the task is registered with the scheduler.
 **Step 4 — register with the OS scheduler:**
 
 ```sh
-akm tasks sync
+akm tasks sync  # doclint:ignore (`tasks` was renamed to singular `task` in 0.9.0)
 ```
 
 `akm tasks sync` scans all `.yml` files, installs tasks that are not yet
@@ -447,13 +447,13 @@ rm ~/akm/tasks/*.md
 
 ```sh
 # All tasks appear with expected schedules
-akm tasks list
+akm tasks list  # doclint:ignore (0.8.0-era subcommand; inspection moved to `akm search`/`akm show` by 0.9.0)
 
 # Each task resolves without errors
-akm tasks show <id>
+akm tasks show <id>  # doclint:ignore (0.8.0-era subcommand; inspection moved to `akm search`/`akm show` by 0.9.0)
 
 # Scheduler entries are in sync
-akm tasks sync
+akm tasks sync  # doclint:ignore (`tasks` was renamed to singular `task` in 0.9.0)
 ```
 
 If a task that was registered on 0.7.x is now missing from the scheduler,
@@ -551,13 +551,13 @@ names are removed with no compatibility aliases.
 
 ```sh
 # Before (0.7.x inconsistent forms — removed in 0.8.0)
-akm remember "note" --stash team-stash
-akm wiki stash my-wiki ./page.md --source team-stash
+akm remember "note" --stash team-stash  # doclint:ignore (pre-0.8.0 flag spelling)
+akm wiki stash my-wiki ./page.md --source team-stash  # doclint:ignore (pre-0.8.0 flag spelling; `wiki` also removed in 0.9.0)
 
 # After (0.8.0)
-akm remember "note" --target team-stash
+akm remember "note" --target team-stash  # doclint:ignore (0.8.0 flag spelling; renamed --bundle in 0.9.0)
 akm import ./page.md --target team-stash
-akm wiki stash my-wiki ./page.md --target team-stash
+akm wiki stash my-wiki ./page.md --target team-stash  # doclint:ignore (`wiki` command family removed in 0.9.0)
 ```
 
 ### Config-dir fallback removed
@@ -594,7 +594,7 @@ context-hub`:
    your stash list. This is the same shape used by any other git source:
 
    ```sh
-   akm add github:andrewyng/context-hub --name context-hub
+   akm add github:andrewyng/context-hub --name context-hub  # doclint:ignore (historical — pre-0.9.0 command spelling)
    ```
 
 3. **Verify with `akm list`.** The output should show `context-hub` as a
@@ -608,12 +608,12 @@ disable in 0.8.0.
 
 ```sh
 # Before (0.7.x and earlier — silently no-op after 0.6.0)
-akm enable context-hub
-akm disable context-hub
+akm enable context-hub  # doclint:ignore (retired toggle, pre-0.6.0 command)
+akm disable context-hub  # doclint:ignore (retired toggle, pre-0.6.0 command)
 
 # After (0.8.0 — explicit error; replace with regular stash management)
-akm add github:andrewyng/context-hub --name context-hub
-akm remove context-hub          # if you previously disabled it
+akm add github:andrewyng/context-hub --name context-hub  # doclint:ignore (historical — pre-0.9.0 command spelling)
+akm remove context-hub          # if you previously disabled it  # doclint:ignore (historical — pre-0.9.0 command spelling)
 ```
 
 ## `akm improve` no longer accepts `--format`
@@ -688,7 +688,7 @@ If you have cron jobs or scripts that call `akm index --enrich` (or
 
 ```sh
 # Before (0.7.x)
-akm index --enrich
+akm index --enrich  # doclint:ignore (pre-0.8.0 flag, removed)
 
 # After (0.8.0)
 akm improve         # slow LLM maintenance work
@@ -713,7 +713,7 @@ refreshes graph extraction against the post-improve corpus state, so a single
 
 ```sh
 # Before (0.7.x)
-akm index --enrich              # also refreshed memories + graph
+akm index --enrich              # also refreshed memories + graph — doclint:ignore (pre-0.8.0 flag, removed)
 
 # After (0.8.0)
 akm improve                     # refreshes memories + graph as part of maintenance
@@ -754,13 +754,13 @@ from `akm wiki ingest`.
 
 ```sh
 # Before (0.7.x — print-only or --execute)
-akm wiki ingest my-wiki > workflow.md
-akm wiki ingest my-wiki --execute
+akm wiki ingest my-wiki > workflow.md  # doclint:ignore (`wiki` command family removed in 0.9.0)
+akm wiki ingest my-wiki --execute  # doclint:ignore (`wiki` command family removed in 0.9.0)
 
 # After (0.8.0 — agent dispatch is the only mode)
-akm wiki ingest my-wiki                          # uses defaults.agent
-akm wiki ingest my-wiki --profile opencode-cli   # explicit profile
-akm wiki ingest my-wiki --model opus --timeout-ms 600000
+akm wiki ingest my-wiki                          # uses defaults.agent — doclint:ignore (`wiki` command family removed in 0.9.0)
+akm wiki ingest my-wiki --profile opencode-cli   # explicit profile — doclint:ignore (`wiki` command family removed in 0.9.0)
+akm wiki ingest my-wiki --model opus --timeout-ms 600000  # doclint:ignore (`wiki` command family removed in 0.9.0)
 ```
 
 ## `config.agent.processes["task"]` and `improve.schedule` removed
@@ -785,7 +785,7 @@ file to set `mode` / `profile` / `timeoutMs` at the top level:
 ```yaml
 # <stash>/tasks/nightly-improve.yml
 schedule: "@daily"
-command: akm improve --auto-accept=90 --limit 50
+command: akm improve --auto-accept=90 --limit 50  # doclint:ignore (0.8.0-only flag, removed in 0.9.0)
 profile: opencode-cli   # was config.agent.processes.task.profile
 timeoutMs: 7200000      # was config.agent.processes.task.timeoutMs
 enabled: true
@@ -888,9 +888,9 @@ update it to use `akm events [--tail]` or query `state.db` directly:
 tail -f ~/.cache/akm/events.jsonl | jq .
 
 # After
-akm events --tail
+akm events --tail  # doclint:ignore (0.8.0-era spelling; renamed `akm log` in 0.9.0)
 # or for scripted consumption with cursor:
-akm events --since-offset <last-row-id> --format json
+akm events --since-offset <last-row-id> --format json  # doclint:ignore (0.8.0-era spelling; renamed `akm log` in 0.9.0)
 ```
 
 ### 2. Reset byte-offset event cursors
@@ -949,8 +949,8 @@ Then run the post-upgrade checklist:
 ```sh
 akm info --format text                          # 1. version 0.8.x
 akm config list --format json | head -40        # 2. stashes[] populated
-akm list                                        # 3. your sources resolve
-akm events --limit 5 --format json              # 4. event log readable from state.db
+akm list                                        # 3. your sources resolve  # doclint:ignore (historical — pre-0.9.0 command spelling)
+akm events --limit 5 --format json              # 4. event log readable from state.db — doclint:ignore (0.8.0-era spelling; renamed `akm log` in 0.9.0)
 akm workflow list --format json | head -20      # 5. active workflow runs intact
 akm search "<a query you know works>"           # 6. indexed content still matches
 ```
@@ -959,7 +959,7 @@ If step 4 returns zero events after a known-active installation, the migration
 script may not have imported the JSONL file. Re-run:
 
 ```sh
-akm-migrate-storage --yes
+akm-migrate storage --yes
 ```
 
 The import step is idempotent: each `(event_type, ts, ref, metadata_json)`
@@ -981,7 +981,7 @@ The migration script imports events in append order. If the JSONL file was
 corrupted or truncated, some rows may have been skipped. Run:
 
 ```sh
-akm-migrate-storage --dry-run
+akm-migrate storage --dry-run
 ```
 
 and look for import warnings. You can also inspect `state.db` directly:
@@ -995,7 +995,7 @@ Check that `$DATA/akm.lock` exists. If only `$CONFIG/akm.lock` exists, the
 migration script may not have run. Run:
 
 ```sh
-akm-migrate-storage --yes
+akm-migrate storage --yes
 ```
 
 **Tasks show no history.**
@@ -1025,7 +1025,7 @@ the command. Convert the file and run `akm tasks sync`.
 The `--stash` flag was removed in 0.8.0. Use `--target` instead:
 
 ```sh
-akm remember "note" --target team-stash
+akm remember "note" --target team-stash  # doclint:ignore (0.8.0 flag spelling; renamed --bundle in 0.9.0)
 ```
 
 ## Rolling back
@@ -1160,25 +1160,25 @@ opt-out instruction, and the preview command:
 To preview the migration without writing (shows what would change):
 
 ```sh
-akm config migrate --dry-run
+akm config migrate --dry-run  # doclint:ignore (0.8.0-only config-schema-rewrite subcommand, not present in 0.9.0's `akm migrate`)
 ```
 
 To preview with a full unified diff of old vs new config:
 
 ```sh
-akm config migrate --dry-run --print-diff
+akm config migrate --dry-run --print-diff  # doclint:ignore (0.8.0-only config-schema-rewrite subcommand, not present in 0.9.0's `akm migrate`)
 ```
 
 To apply:
 
 ```sh
-akm config migrate
+akm config migrate  # doclint:ignore (0.8.0-only config-schema-rewrite subcommand, not present in 0.9.0's `akm migrate`)
 ```
 
 To apply and see a unified diff of what changed:
 
 ```sh
-akm config migrate --print-diff
+akm config migrate --print-diff  # doclint:ignore (0.8.0-only config-schema-rewrite subcommand, not present in 0.9.0's `akm migrate`)
 ```
 
 `akm config migrate` acquires a file lock (`<config-dir>/.akm/migrate.lock`)
@@ -1279,9 +1279,9 @@ configurations that used to silently misbehave are now rejected.
    — error messages that referenced them were misleading. Now:
 
    ```sh
-   akm config validate         # check the on-disk file against the schema
-   akm config migrate           # migrate legacy shape to 0.8.0 in place
-   akm config migrate --dry-run # preview the migration without writing
+   akm config validate         # check the on-disk file against the schema — doclint:ignore (removed in 0.9.0; load-time schema checks already reject an invalid config)
+   akm config migrate           # migrate legacy shape to 0.8.0 in place — doclint:ignore (0.8.0-only subcommand, not present in 0.9.0's `akm migrate`)
+   akm config migrate --dry-run # preview the migration without writing — doclint:ignore (0.8.0-only subcommand, not present in 0.9.0's `akm migrate`)
    ```
 
 8. **`defaultWriteTarget` validation tightened.** It must name a configured
@@ -1375,4 +1375,3 @@ Supported tokens: `{timestamp}`, `{date}`, `{time}`, `{scope}`, `{refs}`,
 
 Add `--no-sync` to any `akm improve` invocations in scripts or automation, or
 set `sync: { enabled: false }` in your custom improve profile.
-