@agimon-ai/po-git 0.0.0-alpha.28 → 0.0.0-alpha.29

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agimon-ai/po-git",
-  "version": "0.0.0-alpha.28",
+  "version": "0.0.0-alpha.29",
   "description": "Git worktree sessions for Po: spawn an isolated worktree with its own session and manage it from the parent",
   "keywords": [
     "ai",
@@ -65,10 +65,10 @@
     "access": "public"
   },
   "dependencies": {
-    "@agimon-ai/po-core": "0.0.0-alpha.28",
-    "@agimon-ai/po-session": "0.0.0-alpha.28",
-    "@agimon-ai/po-web-components": "0.0.0-alpha.28",
-    "@agimon-ai/po-web-security": "0.0.0-alpha.28",
+    "@agimon-ai/po-core": "0.0.0-alpha.29",
+    "@agimon-ai/po-session": "0.0.0-alpha.29",
+    "@agimon-ai/po-web-components": "0.0.0-alpha.29",
+    "@agimon-ai/po-web-security": "0.0.0-alpha.29",
     "@deepseek-ai/cordis": "4.0.5",
     "@tanstack/react-store": "0.11.2",
     "@tanstack/store": "0.11.2",
@@ -76,9 +76,9 @@
     "typebox": "1.3.37"
   },
   "devDependencies": {
-    "@agimon-ai/po-build": "0.0.0-alpha.28",
-    "@agimon-ai/po-native-components": "0.0.0-alpha.28",
-    "@agimon-ai/vibe-lint-plugin-po-extension": "0.0.0-alpha.28",
+    "@agimon-ai/po-build": "0.0.0-alpha.29",
+    "@agimon-ai/po-native-components": "0.0.0-alpha.29",
+    "@agimon-ai/vibe-lint-plugin-po-extension": "0.0.0-alpha.29",
     "@babel/core": "7.29.7",
     "@earendil-works/pi-agent-core": "1.3.0",
     "@earendil-works/pi-coding-agent": "1.3.0",

package/src/prompts/po-use-git/SKILL.md

@@ -5,8 +5,10 @@ description: 'Use @agimon-ai/po-git: Git worktree sessions for Po: spawn an isol
 
 # Worktree sessions
 
-`run_worktree` creates a git worktree and starts a Po session inside it. The
-new session appears nested under the current one in the SESSIONS rail, so a
+In code mode the `worktrees` namespace creates a git worktree and starts a Po
+session inside it: call `discover({ namespace: 'worktrees' })` for the types,
+then `exec`. Without code mode the same actions are the `run_worktree` tool.
+The new session appears nested under the current one in the SESSIONS rail, so a
 parent can hand off a branch of work and keep its own checkout untouched.
 
 Worktrees live outside the repository, under `~/.po/git/worktrees`. That
@@ -22,35 +24,36 @@ or two features that touch the same files.
 Do not reach for it to parallelise work that shares a branch. Two sessions on
 one branch in two checkouts will fight, and git refuses the second worktree.
 
-The new checkout has no dependencies installed: `spawn_worktree` runs git and
+The new checkout has no dependencies installed: `spawn` runs git and
 nothing else, whatever language the repository is in. Install them in the
 worktree before building or testing there.
 
 ## Actions
 
-```
-run_worktree { action: 'spawn_worktree', branch: 'wt/fix-auth' }
-run_worktree { action: 'list' }
-run_worktree { action: 'status', id: 'a1b2c3d4' }
-run_worktree { action: 'merge', id: 'a1b2c3d4' }
-run_worktree { action: 'close_worktree', id: 'a1b2c3d4' }
-run_worktree { action: 'prune', dryRun: true }
-run_worktree { action: 'send', id: 'a1b2c3d4', message: 'Please report progress' }
-run_worktree { action: 'messages', id: 'a1b2c3d4' }
+```ts
+await worktrees.spawn({ branch: 'wt/fix-auth' });
+await worktrees.list();
+await worktrees.status('a1b2c3d4');
+await worktrees.merge('a1b2c3d4');
+await worktrees.close('a1b2c3d4');
+await worktrees.prune({ dryRun: true });
+await worktrees.send('a1b2c3d4', 'Please report progress');
+await worktrees.messages('a1b2c3d4');
 ```
 
-`spawn_worktree` takes `branch`, and optionally `baseRef` (defaults to the
-current branch), `name` for the rail, and `task` as the session's first message.
-Every other action identifies a worktree by the short `id` that `list` prints,
-never by path or branch. `list` and `status` label each record relative to the
-calling session: `parent` means you created the worktree, `child` means you are
-its worktree session, and `other session` means neither. To report to your
-parent from a nested worktree, use your own record labelled `child`, not the
-record for your parent's worktree. Use `parent` records to contact your own
-children. These labels do not grant permission to send, merge, or close another
-session's worktree.
-
-`send` delivers between a worktree session and its parent. A `spawn_worktree`
+Records come back as objects, so filter them in the script rather than reading
+printed text. `spawn` can be slow: pass a larger `timeoutMs` to `exec`. It takes
+`branch`, and optionally `baseRef` (defaults to the current branch), `name` for
+the rail, and `task` as the session's first message. Every other method
+identifies a worktree by its short `id`, never by path or branch. Each record
+carries a `relationship` relative to the calling session: `parent` means you
+created the worktree, `child` means you are its worktree session, and `other`
+means neither. To report to your parent from a nested worktree, use your own
+record with relationship `child`, not the record for your parent's worktree. Use
+`parent` records to contact your own children. These labels do not grant
+permission to send, merge, or close another session's worktree.
+
+`send` delivers between a worktree session and its parent. A `spawn`
 `task` is the first message to the new session. Both use durable Session delivery
 when available. A delivery error after the worktree is created does not remove
 the worktree. Do not spawn it again to retry the task.
@@ -64,17 +67,17 @@ itself failed, inspect the worktree and sender outbox before using `send` again.
 
 ## What it refuses, and why
 
-- **`close_worktree` on a dirty tree.** It names the uncommitted files and stops.
-  Pass `force: true` only after reading that list. The files are gone after.
+- **`close` on a dirty tree.** It names the uncommitted files and stops.
+  Pass `{ force: true }` only after reading that list. The files are gone after.
 - **`merge` when the parent checkout is dirty.** The merge lands in the parent,
   so uncommitted edits there would be folded into a merge commit nobody meant to
   make. Commit or stash first.
-- **`spawn_worktree` on a branch that already has a worktree.** Close the
+- **`spawn` on a branch that already has a worktree.** Close the
   existing one or pick another branch.
 - **`prune` never deletes a worktree holding uncommitted work**, and never
   touches a directory this tool did not create. It reports those instead.
 
-Run `prune` with `dryRun: true` first. The plan tells you exactly what would be
+Run `prune` with `{ dryRun: true }` first. The plan tells you exactly what would be
 removed, forgotten, and left alone.
 
 ## Notes
@@ -83,5 +86,5 @@ removed, forgotten, and left alone.
   own turn loop, and it does not report back when it finishes.
 - Closing the parent does not close its worktree sessions. They keep running and
   stay in the rail.
-- `spawn_worktree` needs the cockpit running, because the cockpit owns session
-  lifecycle. Without it the tool says so rather than half-creating anything.
+- `spawn` needs the cockpit running, because the cockpit owns session
+  lifecycle. Without it the call rejects with a message rather than half-creating anything.