akm-cli/docs/migration/release-notes/0.7.5.md

akm (Agent Knowledge Manager) — a portable, local-first capability library for AI agents. Discover, load, share, and improve reusable skills, scripts, workflows, and knowledge across any shell-capable coding agent, including Claude Code, OpenCode, and Cur

Migration notes for akm v0.7.5

0.7.5 is a patch release that rolls up all changes shipped on `main` after v0.7.4.

- **Workflow runs are now workspace-scoped** — ref-based workflow commands (`workflow next`, `workflow status`, `workflow list`) now resolve runs within the current project/worktree/directory instead of sharing one global active-run pool across every repo and local sandbox. This fixes cross-repo blocking and leakage for workflow refs such as `workflow:github-issues-parallel-implementer`. Direct run-id commands still target the exact run.
- **Workflow help/docs now explain scope semantics** — CLI help, operator docs, and workflow-facing hints now describe the current-scope behavior so teams know that ref-based run resolution is local to the current workspace.
- **`show` now prefers fresh index state** — stale index reads auto-refresh instead of silently falling back to a raw filesystem path, reducing search/show drift.
- **External agent + LLM parsing is more defensive** — reflect/propose and related local-model JSON parsing paths are hardened against malformed or partial output.
- **Reflect temp-file handling is safer** — draft files for reflection flows now live in OS temp space instead of the stash.
- **Memory inference respects token budgets** — long inputs are now trimmed to the configured LLM budget.
- **Vault and save follow-ups landed** — vault path/run flows and named git stash selection in `akm save` received targeted fixes and regression coverage.
- **Release/migration packaging is tighter** — published static files, changelog resolution, and rerunnable release automation received follow-up fixes.

No manual migration is required for most users, but note these operator-facing details:

1. If you were relying on ref-based workflow runs being globally shared across repos or directories, that behavior is gone. Use direct run IDs when you intentionally need to resume a specific run created elsewhere.
2. Existing older workflow runs created before the new workspace scope key was introduced are still accessible by direct run ID, but ref-based commands now prefer runs created in the current scope.
3. `akm help migrate latest` now resolves to 0.7.5 and uses the published `CHANGELOG.md` path.

Full changelog: https://github.com/itlackey/akm/blob/main/CHANGELOG.md