finishinglisted

# Finishing ## Overview **Core principle:** Landing work is a sequence: **prove the relevant tree is green → determine the authorized integration action → execute only that action → clean up.** If the user already chose, do not ask them to choose again. If no integration choice or authority exists, present the options. ## Step 1 — Prove It's Green (on the tree you'll integrate) Verify the actual code about to land, right now — at the breadth the **whole branch** earns, not the breadth its last commit earned. A green run from before your last change does not count (**evidence-before-claims**). Red → stop and fix, or surface it; don't land red. Scope the landing gate in this order: 1. **The repository's prescribed gate, if one exists** (`make check`, the CI job, a documented pre-PR command). A project that has declared its gate has already made this decision — run it. 2. **Otherwise, the union of every slice's blast radius** (**evidence-before-claims**), plus whatever the slices *compose* into. Per-slice verification proves each piece; it does not prove they work together, and integration seams are where branches actually break. 3. **Full suite regardless** when the branch touches build config, dependencies, shared interfaces, persisted formats, or security boundaries — or when it's long-lived, rebased, or larger than you can hold in your head. A one-commit branch that fixed a typo in a private helper does not need a 20-minute suite to land. Say what you r