@sma1lboy/kobe 0.9.18 → 0.9.20

package/dist/skills/rove/SKILL.md

@@ -3,7 +3,7 @@ name: rove
 description: Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — `rove api send`, never a peer/MCP side channel.
 ---
 
-<!-- rove-skill-version: 35 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
+<!-- rove-skill-version: 36 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
 
 # Rove shell control
 
@@ -215,7 +215,7 @@ turn either. These five carry almost all traffic:
 add      --repo(REQ) --prompt --title --command --count --agents --activate
 send     --prompt(REQ) --task-id --tab --command --plain
 get-task --task-id(REQ)          list  (no flags)
-collect  --task-ids <csv> | --repo
+collect  --group <groupId> | --task-ids <csv> | --repo
 ```
 
 Four names that have actually been guessed wrong here: `add --vendor` is
@@ -277,7 +277,10 @@ rove api send --task-id <id> --tab new --prompt "<turn>"    # fresh engine tab
 rove api send --task-id <id> --tab new --command codex --prompt "<turn>"
 
 rove api get-task --task-id <id>
-rove api collect --task-ids <id1>,<id2>,<id3> --pretty
+# One read for the whole round — the groupId `add --count` returned. Never
+# hand-copy N task ids across turns: collect by group. Lost the groupId? Any
+# sibling task's `.groupId` in `list` output recovers it.
+rove api collect --group <groupId> --pretty
 rove api list --pretty
 ```
 
@@ -286,7 +289,13 @@ command, or content tab alone does not count.
 Omitting BOTH `--task-id` and `--tab` inside a task that has a dispatcher
 targets that dispatcher's tab (see the reply rule above); otherwise the
 target is the active task. Omitting only `--tab` targets a live engine tab
-(`tab-1` first, then any surviving engine tab). Only when the task has NO live session at all does `send`
+(`tab-1` first, then any surviving engine tab). **Trap: omitting only
+`--task-id` while giving `--tab tab-N` inside a dispatched task delivers to
+`tab-N` of the DISPATCHER's task** — the dispatcher's id fills in for
+`--task-id`, but an explicit `--tab` is kept, so your `send --tab tab-3`
+lands in the middle of another session's tab-3, not yours. Target your own
+task's tab with `--task-id "$ROVE_TASK_ID" --tab tab-N`. Only when the task
+has NO live session at all does `send`
 auto-start the canonical engine in the task's worktree (`started: true` in
 the result marks that fresh session). If live tabs exist but none resolves
 as an engine, it refuses with `NO_ENGINE_TAB` — address one with `--tab
@@ -330,18 +339,19 @@ logs, dashboards), don't scatter panes for work `add` should own.
 | `set-branch --task-id ID --branch B` | Rename its branch |
 | `set-command --task-id ID --command CMD` | Change the engine launch command for the next launch |
 | `set-status --task-id ID --status S` | Set lifecycle status |
-| `archive --task-id ID [--archived=false]` | Archive/unarchive; stops live sessions |
 | `pin --task-id ID [--pinned=false]` | Pin/unpin |
 | `set-active --task-id ID` / `--none` | Change shared active task |
 | `ensure-worktree --task-id ID` | Materialize without starting an engine |
-| `land --task-id ID [--strategy merge\|squash] [--delete-branch] [--then-archive] [--remove-worktree=false]` | Merge the task's branch into the base repo's current branch; the Worktree is removed by default (`--remove-worktree=false` keeps it). The branch always stays; dirty/self/base removals are refused, outcome in the result's `worktree` field |
+| `land --task-id ID [--strategy merge\|squash] [--delete-branch] [--remove-worktree=false]` | Merge the task's branch into the base repo's current branch; the Worktree is removed by default (`--remove-worktree=false` keeps it). The branch always stays; dirty/self/base removals are refused, outcome in the result's `worktree` field |
 | `delete --task-id ID [--force] [--delete-branch]` | Remove task + Worktree; the git branch stays unless `--delete-branch` (and `--force` never implies it) |
 | `discover-adoptable --repo PATH` | Find untracked Worktrees |
 | `adopt --repo PATH --worktree PATH` | Import a Worktree |
 
 Once a task's work is merged, `delete` is the normal cleanup — the branch is
-git's durable record and survives. `archive` remains as a manual "hide the
-row" override. `--delete-branch` (or a dirty-worktree `--force`) still needs
+git's durable record and survives. There is no "hide the row without
+deleting" verb anymore (`archive` was removed); a merged task you want out of
+the way is a `delete`, and its branch is still there if you need the history
+back. `--delete-branch` (or a dirty-worktree `--force`) still needs
 explicit user authorization.
 
 ## Issue tracker
@@ -462,15 +472,17 @@ After comparing attempts, finish the round instead of leaving tasks behind:
 ```bash
 # Land the winner: merge its branch into the base repo's CURRENT branch.
 # Verify the base checkout is on the intended branch first.
-rove api land --task-id <winner> --then-archive
+rove api land --task-id <winner>
 
-# Archive the losers (non-destructive; branches survive).
-rove api archive --task-id <loser1>
-rove api archive --task-id <loser2>
+# Delete the losers: task + worktree go away, the git branch survives
+# (recoverable). NOT --delete-branch — that destroys history and needs
+# explicit user authorization.
+rove api delete --task-id <loser1>
+rove api delete --task-id <loser2>
 ```
 
 `land` refuses a dirty base checkout; on merge conflict it aborts cleanly and
-returns the conflicted files for manual resolution. `delete` removes a loser's
-Worktree but keeps its branch (recoverable); still don't use it — or
-`--delete-branch`, which destroys the history — without explicit user
-authorization.
+returns the conflicted files for manual resolution. `delete` removes a
+loser's Worktree but keeps its branch (recoverable); `--delete-branch`
+destroys the history and is never part of closing a round without explicit
+user authorization.

package/dist/skills/rove/references/api-flags.md

@@ -41,6 +41,7 @@ Four flag names that have actually been guessed wrong here, and what they are:
 
 | Gone | Now |
 |---|---|
+| `archive` | `delete` (task + worktree go; the git branch survives unless `--delete-branch`) |
 | `fan-out` | `add --count N` / `add --agents claude:2,codex:1` |
 | `task-list` | `list` |
 | `send-tab` | `send --tab tab-N` |
@@ -52,7 +53,7 @@ Seeing one of these in guidance means that guidance predates the rename —
 ## read
 
 ```text
-list          (none)                     every task, archived included
+list          (none)                     every task
 get-task      --task-id(REQ)             one task + .tabs[] — the read before `send --tab`
 collect       --task-ids <csv> --repo    comparison snapshot across tasks
 inspect       --task-id                  daemon activity + pty walk + tab snapshots
@@ -113,9 +114,8 @@ rename         --task-id(REQ) --title(REQ)
 set-branch     --task-id(REQ) --branch(REQ)
 set-command    --task-id(REQ) --command(REQ)      next launch only
 set-status     --task-id(REQ) --status(REQ)[backlog|in_progress|in_review|done|canceled|error]
-archive        --task-id(REQ) --archived(true)
 pin            --task-id(REQ) --pinned(true)
-land           --task-id(REQ) --strategy[merge|squash] --delete-branch --then-archive --remove-worktree(true)
+land           --task-id(REQ) --strategy[merge|squash] --delete-branch --remove-worktree(true)
 delete         --task-id(REQ) --force --delete-branch
 ```
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@sma1lboy/kobe",
-  "version": "0.9.18",
+  "version": "0.9.20",
   "description": "Rove — the agent multiplexer for your terminal. Run coding agents on parallel tasks with isolated worktrees and persistent sessions.",
   "keywords": [
     "terminal",