akm-cli 0.9.2-alpha.5 → 0.9.2

package/CHANGELOG.md

@@ -6,8 +6,38 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.9.2] - 2026-08-29
+
 ### Fixed
 
+- **A blocked workflow run became permanently unresumable after `akm
+  workflow abandon` (#847).** Abandon correctly moved the run to `failed`
+  but left its current step `blocked`; the durable-spine validator then
+  rejected that honest abandoned shape as corruption before `resume` could
+  reopen the step. Failed-run validation now accepts the three legitimate
+  current-step states — `pending` for an abandoned active run, `blocked` for
+  an abandoned blocked run, and `failed` for an execution failure — and
+  `resume` normalizes each back to `pending` as promised by the CLI help.
+
+- **`akm task sync` could compute another bundle's real scheduler entries as
+  drift and try to remove them (#846).** Removal was scoped by a bundle
+  *display name* (`bundleName`/`--bundle` target) — a value derived from a
+  directory basename that two unrelated bundles can legitimately share (an
+  unconfigured bundle's name is deduped only against its own config's
+  bundles, never against other bundles actually installed on the machine).
+  A primary/unconfigured-bundle sync now additionally confirms a
+  name-matching installed entry's *resolved bundle path*, recovered from
+  that entry's own scheduler-context descriptor, before treating it as
+  eligible for reconcile — and refuses (rather than assumes) when that path
+  can't be established. **Backward compatibility:** every entry installed by
+  this codebase already carries a scheduler-context descriptor (the
+  `--scheduler-context` file used to restore the scheduled process's
+  environment), so existing installations resolve correctly with no user
+  action required. An entry whose descriptor is missing, unreadable, or
+  owned by a different OS user is never assumed to belong to the invoking
+  bundle; such an entry is simply left untouched by sync (it will not be
+  auto-repaired or removed) until it is reinstalled or removed by hand.
+
 - **Scheduled tasks on Windows ran but recorded no output.** A task fired by
   Task Scheduler logged `exit_code=0` with an empty log: the command really
   ran, but nothing it printed was captured. Captured runs asked for their own

package/dist/commands/tasks/tasks.js

@@ -337,18 +337,34 @@ export async function akmTasksSync(deps = {}, bundleTarget, options = {}) {
     }
     const inspection = await sched.inspectBindings({ rebind: options.rebind === true });
     const rawEntries = [...inspection.installed];
-    const allEntries = rawEntries.map((entry) => ({
-        ...entry,
-        ...(entry.nativeId !== undefined ? { nativeId: entry.nativeId } : {}),
-        ...(entry.invocation !== undefined ? { invocation: Object.freeze([...entry.invocation]) } : {}),
-        binding: "binding" in entry ? [...entry.binding] : [],
-        contextPath: "contextPath" in entry ? entry.contextPath : "",
-    }));
+    const allEntries = rawEntries.map((entry) => {
+        const contextPath = "contextPath" in entry ? entry.contextPath : "";
+        // #846: recover the resolved bundle path this entry was installed
+        // under from its own scheduler-context descriptor. Any failure (no
+        // descriptor, unreadable, corrupt, owned by another user) leaves
+        // ownerBundlePath unset — belongsToBundle must never treat that as
+        // "mine".
+        const ownerBundlePath = contextPath ? resolveInstalledOwnerPath(contextPath) : undefined;
+        return {
+            ...entry,
+            ...(entry.nativeId !== undefined ? { nativeId: entry.nativeId } : {}),
+            ...(entry.invocation !== undefined ? { invocation: Object.freeze([...entry.invocation]) } : {}),
+            binding: "binding" in entry ? [...entry.binding] : [],
+            contextPath,
+            ...(ownerBundlePath !== undefined ? { ownerBundlePath } : {}),
+        };
+    });
     const nativeArtifacts = inspection.artifacts;
     const common = {
         sourceRoot: stashDir,
         adapterId: resolved.source.adapterId ?? detectAdapterId(stashDir),
         bundleName: resolved.source.name,
+        // #846: only meaningful for a primary/unconfigured-bundle sync. A
+        // `--bundle <target>` entry's scheduler-context descriptor records the
+        // invoking process's OWN primary AKM_BUNDLE_DIR, not the targeted
+        // bundle's directory, so path-scoping stays gated on the case it's
+        // actually valid for (see belongsToBundle).
+        ...(syncTarget === undefined ? { bundlePath: path.resolve(stashDir) } : {}),
         ...(syncTarget ? { bundleTarget: syncTarget } : {}),
         backend: sched.name,
         installed: allEntries,
@@ -773,6 +789,15 @@ function groupInstalledBindings(entries, invocation) {
     }
     return [...groups.values()].map((group) => ({ ...group, taskIds: group.taskIds.sort() }));
 }
+/** Best-effort recovery of an installed binding's owning bundle path (#846). */
+function resolveInstalledOwnerPath(contextPath) {
+    try {
+        return validateSchedulerContextDescriptor(contextPath).environment.AKM_BUNDLE_DIR;
+    }
+    catch {
+        return undefined;
+    }
+}
 function inspectInstalledBinding(entry, invocation) {
     const status = [];
     const binding = entry.binding;

package/dist/tasks/scheduler-sync.js

@@ -478,6 +478,21 @@ function installOptionsFor(input, current) {
     return input.installOptions ? Object.freeze({ ...input.installOptions }) : undefined;
 }
 function belongsToBundle(entry, input) {
+    if (input.bundlePath !== undefined && entry.target === input.bundleName) {
+        // Path-scoped (#846), primary/unconfigured-bundle sync only: the name
+        // already matches, but a display name derived from a directory
+        // basename is not an identity — two unrelated bundles can legitimately
+        // share one. Require the entry's own scheduler-context descriptor to
+        // additionally confirm the resolved path. An entry whose owning path
+        // cannot be established is never assumed to be ours — that silent
+        // assumption is exactly what let an isolated/foreign bundle's sync
+        // reach for another bundle's real scheduler entries. (`bundlePath` is
+        // only set for a primary sync — a `--bundle <target>` entry's
+        // descriptor reflects the invoking process's OWN primary directory,
+        // not the targeted bundle's, so it is not a meaningful signal there;
+        // that case keeps relying on config-name uniqueness below.)
+        return entry.ownerBundlePath !== undefined && entry.ownerBundlePath === input.bundlePath;
+    }
     if (entry.target === input.bundleName || entry.target === input.bundleTarget)
         return true;
     return false;
@@ -487,8 +502,13 @@ function assertNoForeignIds(desired, input) {
     const foreign = input.installed.find((entry) => wanted.has(entry.id) && !belongsToBundle(entry, input));
     if (!foreign)
         return;
-    const where = foreign.target ? `bundle ${JSON.stringify(foreign.target)}` : "the default bundle";
-    throw new UsageError(`Scheduler id ${JSON.stringify(foreign.id)} is already scheduled from ${where}; desired source ids must not collide across bundles.`, "RESOURCE_ALREADY_EXISTS");
+    const where = foreign.ownerBundlePath
+        ? `the bundle at ${JSON.stringify(foreign.ownerBundlePath)}`
+        : foreign.target
+            ? `bundle ${JSON.stringify(foreign.target)}`
+            : "the default bundle";
+    const mine = input.bundlePath ? ` (this sync is scoped to ${JSON.stringify(input.bundlePath)})` : "";
+    throw new UsageError(`Scheduler id ${JSON.stringify(foreign.id)} is already scheduled from ${where}${mine}; desired source ids must not collide across bundles.`, "RESOURCE_ALREADY_EXISTS");
 }
 function assertUniqueDesiredIds(desired) {
     const seen = new Set();

package/dist/workflows/runtime/plan-classifier.js

@@ -122,8 +122,11 @@ export function assertWorkflowSpineMatchesPlan(plan, run, rows) {
     }
     else if (run.status === "failed") {
         // `workflow abandon` marks the run failed while intentionally leaving its
-        // current step pending so `resume` can reopen the same work.
-        if (!current || (current.status !== "failed" && current.status !== "pending"))
+        // current step unchanged so `resume` can reopen the same work. An active
+        // run leaves a pending step; a blocked run leaves a blocked step; and an
+        // execution failure already carries a failed step. All three are honest
+        // failed-run spines that `resumeWorkflowRun` normalizes back to pending.
+        if (!current || (current.status !== "failed" && current.status !== "pending" && current.status !== "blocked"))
             corruptSpine(run.id, `${run.status} status does not match the current plan step`);
     }
     else if (run.status === "completed") {

package/docs/migration/README.md

@@ -2,7 +2,7 @@
 
 Upgrade guides and per-release migration notes.
 
-- [v0.9.1 -> v0.9.2 migration guide](v0.9.1-to-v0.9.2.md) -- Task-v2/task-v3 to task source v4 conversion, the single durable-v4 workflow boundary, and release behavior changes
+- [v0.9.1 -> v0.9.2 migration guide](v0.9.1-to-v0.9.2.md) -- Task-v2/task-v3 to task source v4 conversion, the durable-v4-family workflow boundary at executable `irVersion: 5`, and release behavior changes
 - [v0.9.2 release note](release-notes/0.9.2.md) -- Self-contained terminal upgrade summary shipped for `akm help migrate 0.9.2`
 - [v0.8 -> current v0.9 migration guide](v0.8-to-v0.9.md) -- Package upgrade with fresh current config/state and explicit task conversion
 - [v0.7 -> v0.8 migration guide](v0.7-to-v0.8.md) -- Task schema and 0.8-era changes

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

@@ -8,7 +8,8 @@ live one level up in `docs/migration/`.
 ## Available notes
 
 - [0.9.2](0.9.2.md) — task source v4 migration, workflow source IR v1 and
-  durable v4, command diagnostics, and strategy judgment migration
+  durable-v4-family `irVersion: 5`, command diagnostics, and strategy judgment
+  migration
 
 ## Adding notes for a new release
 

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

@@ -17,7 +17,7 @@ in place is not.
 - old `index.db`, `workflow.db`, task-history JSONL, or legacy lock/cache
   layouts;
 - old ref grammar or old workflow/task execution paths;
-- in-flight pre-v4 workflow plans.
+- in-flight workflow plans older than `irVersion: 5`.
 
 Those formats are not compatibility inputs to the current runtime. Keep an
 archive if you need historical inspection; do not place it in the live 0.9
@@ -108,9 +108,9 @@ existing scheduler entry.
 ## Workflow boundary
 
 Current Markdown and GitHub-shaped YAML workflows compile to the same source
-IR and freeze durable plan IR v4. Durable v4 is the only executable stored
-plan. Do not copy an old workflow database expecting old runs to resume; start
-new runs from current authored sources.
+IR and freeze the durable plan v4 family's executable `irVersion: 5` format.
+That is the only executable stored plan. Do not copy an old workflow database
+expecting old runs to resume; start new runs from current authored sources.
 
 ## Recovery
 

package/docs/migration/v0.9.0-troubleshooting.md

@@ -109,13 +109,13 @@ backup over a file while a task sync or scheduler process is running.
 
 ## A workflow will not resume
 
-Only durable plan IR v4 executes. Pre-v4 stored plans are rejected rather than
-decoded by a compatibility runtime. Start a new run from the current Markdown
-or YAML workflow source.
+Only the durable plan v4 family's `irVersion: 5` executes. Pre-`irVersion`-5
+stored plans are rejected rather than decoded by a compatibility runtime.
+Start a new run from the current Markdown or YAML workflow source.
 
-For a v4 run, a missing or changed authored source is not a resume blocker: the
-run uses its frozen plan. A plan-hash or schema failure is durable-state
-corruption and must fail closed.
+For an `irVersion: 5` run, a missing or changed authored source is not a resume
+blocker: the run uses its frozen plan. A plan-hash or schema failure is
+durable-state corruption and must fail closed.
 
 ## A stale transaction journal is reported
 

package/docs/reference/configuration.md

@@ -147,8 +147,9 @@ defaults at the layer that selected it; explicit sibling fields and nearer
 layers still win. The resulting request carries the exact model ID and merged
 inference object. Engine lowerers consume that exact selection and never run
 alias resolution again. New workflow starts persist the exact request and
-symbolic runner selection in durable plan v4; resume consumes that frozen
-material without resolving aliases again.
+symbolic runner selection in the durable plan v4 family's executable
+`irVersion: 5`; resume consumes that frozen material without resolving aliases
+again.
 
 Copy the complete installed starter into the user configuration directory when
 you want to customize all fields:

package/docs/reference/workflow-schema.md

@@ -1021,16 +1021,17 @@ a committed *value*, so it cannot carry "whatever this build agent's
 Values passed through this way are **not** redacted from the command's output
 the way `env:` binding values are, so never list a credential here.
 
-#### Durable v4 forbids `inherit_env`
+#### Durable v4 (`irVersion: 5`) forbids `inherit_env`
 
-Every new workflow start freezes a durable v4 plan. V4 rejects
-`inherit_env: true` and any other request for whole-process inheritance; use
-exact named environment bindings and `pass_env:` instead. Both mechanisms are
-dispatch-significant, keep the visible environment surface bounded, and form
-part of the unit's input hash.
+Every new workflow start freezes the durable plan v4 family's current
+executable format, `irVersion: 5`. It rejects `inherit_env: true` and any other
+request for whole-process inheritance; use exact named environment bindings
+and `pass_env:` instead. Both mechanisms are dispatch-significant, keep the
+visible environment surface bounded, and form part of the unit's input hash.
 
-The historical `inherit_env` spelling is unsupported. Pre-v4 stored plans are
-rejected; they are never upgraded or replayed through a second runtime.
+The historical `inherit_env` spelling is unsupported. Pre-`irVersion`-5 stored
+plans are rejected; they are never upgraded or replayed through a second
+runtime.
 
 ### What `akm show` reports for an exec step
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-cli",
-  "version": "0.9.2-alpha.5",
+  "version": "0.9.2",
   "type": "module",
   "description": "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 Cursor.",
   "keywords": [