ce-verifylisted

# Verify **Invocation input:** Journey to verify (optional): $ARGUMENTS Verify that the implemented features of a plan work together. This is the last link in the discipline chain: `plan ← spec ← implement ← verify`. Verify checks that the software **behaves** as specified; its sibling `/ce-review` checks **how the code is written** (correctness beyond tests, security, maintainability, conformance) — run both before handover. This workflow does **not redesign or patch code**. It runs the whole project's tests, walks the planned journeys end-to-end, checks bridges are retired, and facilitates stakeholder acceptance. When it finds a defect it **escalates** — never fixes — keeping `spec` and `implement` as the only path that mutates code. It runs in two modes: - **Milestone** (`/ce-verify <journey>`) — verify one journey once all its composing features are implemented. - **Pre-handover** (no argument) — verify the whole project. It can be run at any point during plan implementation; it operates on whatever features have been implemented so far. Under `/ce-auto-build` it runs as the **post-loop integration pass** — it captures the surface evidence and **defers its readability verdict to the end-review** (auto-build batches human judgment to the bookends, so this human-verdict skill is not spawned mid-loop). The *in-loop* surface-defect catch — parking a broken surface before dependents build on it — is auto-build's per-feature autonomous Surface Critique (`surface_findin