Module issue 

rk issue start: one command from an issue to the branch the forge named, seated the way the recorded mode says.

Not a worktree verb, because the worktree verbs are mode-free by design and starting from an issue is not: branches mode has no worktree to add. The order of the run is what makes the refusals cheap — the local reads and the reference check come first, the forge-CLI gate next, and the network last — so every failure but a forge outage costs one local process and leaves the clone untouched.

Functions

run

Dispatch the issue surface.