verification-before-completionlisted

# Verification Before Completion ## Checklist - Requirement or user request is satisfied. - Changed files are scoped to the task. - No placeholders, dead references, stale names, or broken links remain. - Tests, build, browser checks, or static validation were run where appropriate. - Failed or skipped verification is explicitly reported. - Residual risk and next steps are clear. - If the current role is delegated, the handback includes `task_id`, `current_stage`, `status`, `summary`, `artifacts`, `risks`, `uncovered_items`, and `recommended_next_stage`. - If a delegated handback uses `status=NEEDS_CONTEXT`, it also includes `clarification_request` and `pm_action: "pm_clarify"`. - If the current role is the top-level session or PM/coordinator and is about to end the turn, native closeout or continuation evidence exists unless the latest user message already came from that native gate and chose to end. - Follow the Specialist Ask Boundary and Native Ask Contract from `core-workflow-contract`. - If the task exposed a reusable workflow weakness, include an `evolution_signal` instead of silently moving on. ## Native Closeout UI Hard Gate - A final prose response is allowed only after verification evidence is ready and closeout/continuation state is valid. - Follow the **Native Ask Contract**, **PM Trigger Guidance**, and **Specialist Ask Boundary** from `core-workflow-contract`. All trigger types — review fan-in, verification results, `NEEDS_USER_INPUT` handbacks, branch/work