Console Worktree Sessions

What it was. The Code tab's worktree option: a new session gets "its own isolated copy using Git worktrees", so "changes in one session don't affect other sessions until you commit them" (Claude Code desktop). The console's version would be a checkbox on the new-session form that has the host run git worktree add and open the session in it.

Why deferred. The repository the console mostly works is run in one shared checkout on purpose: a worktree per session costs a full pnpm i and the package builds each, plus a cleanup step, and the review queue already rejects it for exactly that (review collector). The sessions in that checkout commit by pathspec and never share a staged index, so the isolation a worktree buys is bought another way.

Revisit when: the console works a repository whose install is cheap enough for a worktree per session, or this repository's install and build become cheap enough that the review queue's rule changes. Either makes the option one form field and one host command.

Cheaper interim: the shared checkout with commits by pathspec, as the review queue works it.