Closed
Labels
ready-for-agentSettled scope eligible for dispatchSettled scope eligible for dispatch
Description
Part of #21. From the Spec review of #21 (Spec 6).
Outcome
Users of a SlipJay project can find out from the user docs that each new thread gets its own SlipJay workspace, what the composer strip shows, and how Land works and reports.
Problems found
docs/usersays nothing about automatic workspaces, the strip, the landing state, Land, or Git actions being absent in Jujutsu and colocated repositories.- The Settings row text still says "new worktree threads", although every thread in a SlipJay project now allocates a workspace.
Acceptance
- One concise section in the relevant
docs/userguide, following the AGENTS.md documentation rules: what happens, how to start, and the unintuitive parts. For example, Land removes the landed workspace, and it needs a SlipJay runner location. - The Settings text matches the behaviour.
Metadata
Metadata
Assignees
Labels
ready-for-agentSettled scope eligible for dispatchSettled scope eligible for dispatch
Activity
docs: SlipJay workspaces and Land for users
pechhe commentedon Oct 15, 2026
Landed in c80c7f0: source control guide explains Jujutsu checkouts, SlipJay workspaces, the composer strip and Land; the Settings Workspaces row describes each provider.