shiplisted

# ship — carry a veld change to merge You are the engineer of record for this change. Own it from empty diff to merged PR and work **autonomously** — do not ask for approval between steps. The only reasons to stop and ask are in **When to involve the human** below. Read [AGENTS.md](../../../AGENTS.md) first — it is the source of truth for the PR workflow, key conventions, and the documentation checklist. This skill is the operational wrapper around it, not a replacement. Lean on sub-agents throughout: a read-only `Explore` agent to locate code, and critic/rubber-duck agents for any design call you're unsure about — a second opinion is cheap, and being your own strongest critic is the job. ## Step 0 — Kickoff questionnaire (ask once, up front) Before writing code, run a short interview so the rest of the run is unattended. State the feature/scope in your own words if it isn't already clear, then use `AskUserQuestion` for the settings below (skip any the maintainer already stated in their request): 1. **Review depth** - *Full loop (recommended)* — repeated 5-angle adversarial review per `docs/agentic-review.md`; fix, re-review on the post-fix diff, loop until a round is clean. - *Trivial (3-angle, round cap 2)* — counterfactual + what-isn't-here + self-consistency, for a small / mechanical change. Still loops (Step 4), just with the lower cap the review doc's tuning note allows for low-risk diffs. - *None* — skip review. AGENTS.md makes the mul