verifying-wave-completionlisted

# Verifying Wave Completion **Render before asking.** Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings **does not count as rendered** (the UI shows a compact card) — restate it in chat first. A passing wave-scoped probe is necessary but not sufficient. The wave is fully complete only when six invariants hold simultaneously. This capability skill runs that composite check after the existing wave-boundary steps (rebase + ff-merge, wave-scoped build, REFACTOR + MUTATE, wave-scoped tests, wave VERIFY) and gates advance-to-next-wave on the result. The check exists because the structured return contract makes false completion structurally hard at the *subagent* boundary, but the *wave* boundary is one level up — and pre-this-skill, the only gate there was a single probe pass. A flaky test, a dropped commit, or a subagent that exited mid-flight without writing its completion event could all slip through. ## When to Invoke `/ship-execute` Step 4 calls this skill as the final gate before advancing the wave counter, AFTER the existing in-line checks have all reported green. Job: confirm the composite picture matches the per-step verdicts. Other entry points: - `/ship-review` Stage 1 (sprint-level) may invoke this as a per-wave audit when re-running review on an archived sprint. - Manual invocation when a user wants to confirm a specific wave is truly