shiplisted

# ship — certify and move the intended delivery boundary Read `delivery-methodology`, the repo's `AGENTS.md`/`CLAUDE.md`, and linked delivery/testing/merge docs first. Determine the actual PR base and choose one mode before running gates. ## Modes ### Direct candidate A complete independently shippable task branch targeting the release branch. Freeze one commit, run the complete affected lane and one official review on that SHA, then push/open the PR. ### Lift slice A bounded delta targeting a declared controlled lift. Require focused checks and a base/head review receipt. Push/open the slice PR and merge it into the lift with a real merge commit when the human-approved lift plan authorizes internal slice merges. It does not enter the release merge queue or rerun the cumulative main-based affected lane by default. ### Lift promotion The frozen lift targeting the release branch. Require: no open dependent slice; current release base merged into the lift; conflict/uncovered delta receipted; ordered receipt coverage verified; complete affected lane plus required integration/migration evidence on the frozen SHA; and one composition-oriented official review. ## Exactly one official review path For a direct candidate or lift promotion, prefer local `codex review`; otherwise use the runtime's PR-based `code-review`, never both. Run the affected lane and local official review concurrently when practical. Unknown/partial results are not passes. A PR-based-only reviewer may