shiplisted

# ship The standalone entry for shipping the current branch. Same flow as the pipeline's ship stage, reached directly: target from the checkout. ## Run Outside a pipeline this verb is its own run, so the console shows it and the Stop hook covers its pane. Skip this section when `RT_RUN_DB` is set and `rt runs snapshot` shows `run.status` = `running`: you were invoked from inside that run, you inherit it, `run.current_stage` is your stage, and you close nothing at the end. Otherwise, when a surface launched this pane (the `--spawned-by` case below), start fresh: another pane's live run is not yours to resume. Launched by hand, first the Resume offer: list `~/.mattstack/runs/<repo>/` (the `--repo` value in the flags block below) for runs whose `snapshot` shows `run.status` = `running` and `run.work_type` = `ship` (read each with `RT_RUN_DB` pointed at its `state.db`; never raw sqlite). Any found: gate `clarify`, one sentence naming each candidate's `spawned_by`, `started_at`, and `current_stage`, then the structured-question tool with one **Resume** option per candidate (recommended for a run this session started earlier; a run another live pane owns is not yours) / **Start fresh**; **Hold**. Resume: `export RT_RUN_DB=<its state.db>`, then `rt runs stage-start --stage ship` (a new attempt, which re-records this session) and `rt runs field set hold - --stage ship`; re-enter with the snapshot's decisions and do not re-ask a question it already answered. Each tool call is a fr