@staff0rd/assist 0.451.0 → 0.453.0

package/README.md

@@ -129,10 +129,10 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
 
 - `assist backlog [--dir <path>]` - Open the backlog tab in the web dashboard (same as `backlog web`). `--dir` overrides the directory used to resolve the current repository's git origin
 - `assist backlog list [--status <type>] [-a, --all] [--all-repos] [-v]` - List backlog items with status icons (alias: `ls`). Defaults to the current repository's todo/in-progress items; `--all` includes done/wontdo, `--all-repos` lists items across all repositories. Also available as the top-level shortcut `assist list` / `assist ls` with the same flags
-- `assist backlog add` - Add a new backlog item interactively (prompts for type: story/bug)
-- `assist backlog add --name <n> --type <t> --desc <d> --ac <criterion...>` - Add a backlog item from CLI options
+- `assist backlog add` - Add a new backlog item interactively (prompts for type: story/bug). Human CLI use only: an agent invocation errors out and points at `assist backlog propose`, so an agent-authored item cannot skip the preview
+- `assist backlog add --name <n> --type <t> --desc <d> --ac <criterion...>` - Add a backlog item from CLI options (same agent restriction)
 - `assist backlog propose --json <file|->` - Review a complete agent-authored backlog item before it is created, from a JSON payload read from a file or stdin (`name`, `type`, `description`, `acceptanceCriteria`, and `phases` of `{ name, tasks, manualChecks }`). In a web session it slides the rendered item — plan included — into the preview pane and blocks: approval writes the item and every phase in order (plus any configured sub-tasks, and a bug's default `Fix` phase when no phases were given) and prints its id, while rejection exits non-zero with the reviewer's reason and each inline comment so the caller can revise and re-propose. Outside a web session it prints the rendered item and creates it. Used by `/draft` and `/bug`; the payload is strict, so an unknown key is an error. See [docs/backlog-item-preview.md](docs/backlog-item-preview.md)
-- `assist backlog add-phase <id> <name> --task <t...> [--manual-check <c...>] [--position <pos>]` - Add a phase (appends by default; `--position` inserts at a 1-indexed position)
+- `assist backlog add-phase <id> <name> --task <t...> [--manual-check <c...>] [--position <pos>]` - Add a phase to an existing item (appends by default; `--position` inserts at a 1-indexed position). An agent invocation in a web session previews the phase in the pane first and writes it only on approval; a human invocation, or an agent outside a web session, writes it directly
 - `assist backlog add-subtask <id> --title <t> [--desc <d>]` - Add a sub-task (status `todo`) to a backlog item. Sub-tasks listed under the `subtasks` key (each `title` and optional `description`) in `assist.yml` and `~/.assist.yml` are auto-applied to every newly created item (stories and bugs); the global and project lists are combined
 - `assist backlog edit-subtask <id> <idx> [--title <t>] [--desc <d>] [--status <s>]` - Edit a sub-task by its 1-based index from `backlog show`; updates any combination of title, description, and status (omitted fields are left unchanged). `--desc` supports Markdown and `\n` line breaks (pass `--desc ""` to clear it); `--status` must be one of `todo`, `in-progress`, `done`
 - `assist backlog remove-subtask <id> <idx>` - Remove a sub-task by its 1-based index from `backlog show`; the remaining sub-tasks are re-indexed so they stay contiguous
@@ -318,6 +318,8 @@ Concurrent sessions in one repo can be isolated with native git worktrees instea
 - `worktree.enabled` (parallel work) — spill concurrent sessions into adjacent `<clone>-N` worktrees. Off means every session on the repo shares its single working copy, exactly as before.
 - `worktree.trunk` (trunk-based) — on, a spilled worktree's branch tracks `origin/<trunk>` so commits land on the mainline. Off (the default, branch-workflow) it starts off the remote default branch with no mainline tracking, leaving the session to raise its own branch and PR.
 
+Drafting, filing a bug and refining change no code, so with parallel work on they still run in the clone's own working copy — even while a coding session holds it — and cost no worktree, no dep install and no teardown gate when closed. Set `worktree.includeDrafts` (default off) to give them their own `<clone>-N` like any other session. When an exempted card chains into `assist backlog run <item>` on Auto-run, the run is placed then: it stays in the clone if nothing else holds it, otherwise it moves into a fresh seeded worktree and waits for the install before starting.
+
 Every live session card carries an **add-agent** button (👥): submitting a prompt there starts a second agent inside that session's own workspace instead of allocating a new one, so both work on what is already in progress there. Starting a session the ordinary way still gets a fresh isolated stream. While several agents share a workspace, only the last one to leave triggers teardown — closing any other simply removes its card, and a card reaching done keeps the workspace for the agents still working in it.
 
 Neither flag leaves permanent state on the clone: nothing writes to the clone's `.git/config` (`assist commit` derives its push refspec from the current branch's upstream instead of relying on `push.default`), so turning parallel work back off leaves the repo as it was.

package/claude/commands/refine.md

@@ -69,6 +69,8 @@ assist backlog remove-phase <id> <phase>
 assist backlog add-phase <id> "Phase name" --task "Task 1" --task "Task 2"
 ```
 
+In a web session this slides the phase into the preview pane and blocks until the user approves it. On rejection the command exits non-zero with the reason and each inline comment and writes nothing — revise the phase and run it again.
+
 ### Phase design rules
 
 When adding or restructuring plan phases, follow the same rules as /draft: