ship

<objective> Execute a locked upstream spec end to end. ship consumes EITHER a finalized brief folder or an Accepted propose, builds a dependency DAG straight from the artifact, locks a definition-of-done contract, implements it on a capability-detected engine, and emits a verification bundle the USER runs plus a trace ledger that survives context reset. ship authors zero product or spec work and never runs build/test toolchain by default. </objective> <parameters> | Flag | Long | Description | |------|------|-------------| | `-h` | `--help` | Show usage guide (references/help-text.md) and exit | | `-a` | `--auto` | Skip non-safety confirmations, auto-pick Recommended (DB/destructive ops still ask) | | `-e` | `--economy` | Force solo tier, no fan-out, save tokens | | `-r` | `--resume` | Resume from an existing trace.md (stepsCompleted) | | `--yolo` | | After listing the commands and how they run, ship may run the SAFE verification commands itself to completion (destructive/DB/deploy stay user-only) | | `-m <tier>` | `--mode <tier>` | Force engine tier: `teams` / `subagents` / `solo` (overrides the probe) | **Parsing:** Defaults from `steps/step-00-init.md`. Flags override. Remainder of input = the artifact path (a `docs/brief/<slug>/` folder OR an `PROPOSAL.md`). </parameters> <state_variables> | Variable | Type | Set by | |----------|------|--------| | `{triage_mode}` | enum(brief,propose,inline) | step-00-triage | | `{artifact_path}` | string\|null | step-00-triage | | `{...