opencode2-cow-worktree 0.2.0 → 0.3.0

package/README.md

@@ -148,7 +148,11 @@ clone (default `"none"`):
 - `"none"`: a request for `cow` produces a Deep clone or fails. Never a
   shallow worktree.
 - `"git"`: on a non-CoW filesystem the tool may build a regular `git`
-  worktree instead and report `mechanism: "git"`.
+  worktree instead and report `mechanism: "git"`. This works on opencode2
+  builds whose worktree create still accepts a `strategy` request
+  (2.0.2-era). From the projectID-era API onward (20260915 nightlies,
+  v2.0.3+) the create always runs the selected strategy and ignores the
+  field, so the non-CoW refusal surfaces and the fallback cannot engage.
 
 **`targetRoot`** — where `spawn_workspace` places the worktree. Unset (the
 default) means a sibling of the source, on the source's filesystem by
@@ -237,8 +241,10 @@ regardless of `fallback`. Only `spawn_workspace` consults the policy.
 - **"the target is on a different filesystem"** — set `worktree.directory` as
   shown above, or point `targetRoot` at the source's filesystem.
 - **`cow` fails on an ext4 or tmpfs project** — expected: that filesystem
-  cannot clone. Use the `git` fallback for tool calls, or let the project use
-  the built-in strategy.
+  cannot clone. On opencode2 builds from the projectID era (20260915
+  nightlies, v2.0.3+) the `git` fallback cannot be requested through the
+  create API, so the refusal is final; on 2.0.2-era builds the `fallback:
+  "git"` option produces a regular git worktree for tool calls.
 - **The plugin is stuck on an old version** — opencode2 caches the package
   under `~/.cache/opencode/node_modules/`. Remove the plugin's cache
   directory and restart: `rm -rf ~/.cache/opencode/node_modules/opencode2-cow-worktree`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode2-cow-worktree",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Copy-on-write worktree strategy for opencode2: a Deep clone of the whole working directory, ignored files included, so parallel agents start ready to run",
   "type": "module",
   "exports": {

package/src/plugin.ts

@@ -146,21 +146,27 @@ function liveDeps(
   return {
     probe: probeCowCapability,
     probeDevice: deviceOf,
-    listWorktrees: () => ctx.worktree.list(),
+    // The projectID-era API (20260915 nightlies onward) requires the project
+    // id on every worktree call and no longer accepts a `location` query, so
+    // all three seams derive it from the plugin's own location context.
+    listWorktrees: () => ctx.worktree.list({ projectID: ctx.location.project.id }),
     isDirectory,
     createWorktree: (input) =>
       ctx.worktree.create({
-        strategy: input.strategy,
-        name: input.name,
-        location: { directory: input.sourceDirectory },
+        projectID: ctx.location.project.id,
+        from: input.sourceDirectory,
         directory: input.parentDirectory,
+        name: input.name,
+        // Ignored by projectID-era binaries (the selected strategy wins);
+        // honored by the 2.0.2-era API, where the git fallback needs it.
+        strategy: input.strategy,
       }),
     createSession: async (directory, name) => {
       const session = await ctx.session.create({ title: name, location: { directory } });
       return session.id;
     },
     removeWorktree: (directory) =>
-      ctx.worktree.remove({ directory, force: true }),
+      ctx.worktree.remove({ projectID: ctx.location.project.id, directory, force: true }),
     // `ctx.session.get` exists on the v2 runtime but is untyped in the
     // installed beta; types/opencode2-worktree.d.ts declares the verified
     // `{ sessionID }` shape and the structural record slice the occupancy
@@ -179,9 +185,11 @@ function liveDeps(
  *
  * `setup` registers the `cow` Strategy through the worktree seam, and the
  * `spawn_workspace` and `list_worktrees` tools through the tool seam.
- * Registering the Strategy also selects it as the Location default; opencode2's
- * registry still lets a caller name the built-in `git` strategy explicitly, so
- * this module does not touch that behavior.
+ * Registering the Strategy also selects it as the default; the projectID-era
+ * create API has no per-request strategy field, so the selected strategy is
+ * what every create uses. The create call still carries `strategy` for
+ * 2.0.2-era binaries, where it is what lets the tool's opt-in `git` fallback
+ * name the built-in git strategy.
  */
 export default {
   id: "opencode2-cow-worktree",
@@ -252,7 +260,7 @@ export default {
             // the inventory and one stat per row, none of spawn_workspace's
             // other seams. (Option validation happens once in setup, so there
             // is no validation side effect to dodge either way.)
-            listWorktrees: () => ctx.worktree.list(),
+            listWorktrees: () => ctx.worktree.list({ projectID: ctx.location.project.id }),
             statEntry: stat,
           });
           const summary =