diff --git a/domains/perps/skills/recipe-cook/skill.md b/domains/perps/skills/recipe-cook/skill.md
index 6795b1a0..cd6d430a 100644
--- a/domains/perps/skills/recipe-cook/skill.md
+++ b/domains/perps/skills/recipe-cook/skill.md
@@ -92,14 +92,14 @@ For `qa`, read `references/qa.md` after materialization; read `references/qa-exa
 
 ## Finish
 
-If a required runtime claim remains unproved, keep repairing it. Use `./mark blocked` only for missing credentials, a product decision the ticket does not settle, or a farm/device failure outside the checkout. A checklist's "or BLOCKED" branch does not authorize `complete` or a `fixed` disposition. Apply the Mainnet rule for network-gap exceptions. When the harness records `awaiting-review` for captured visual proof, prepare any explicitly requested local PR draft below and return that pending status. Never approve the criterion, weaken its proof kind, or complete the task to bypass review.
+If a required runtime claim remains unproved, keep repairing it. Use `./mark blocked` only for missing credentials, a product decision the ticket does not settle, or a farm/device failure outside the checkout. A checklist's "or BLOCKED" branch does not authorize `complete` or a `fixed` disposition. Apply the Mainnet rule for network-gap exceptions. When the harness records `awaiting-review` for captured visual proof, prepare any explicitly requested local PR draft below, then finish with the terminal mark: the run gate hands those criteria to an authorized reviewer after completion, so never hold the task pending for that review. Never approve the criterion or weaken its proof kind.
 
 1. `artifacts/pr-description.md` (or `artifacts/no-change-report.md`) + `artifacts/learnings.md`. The PR description follows the repository PR template headings and carries the proof summary (what changed, root cause, validation, evidence paths). `qa` writes the single human `artifacts/report.html`; static `review-pr` writes its declared review outputs. The frozen `inputs/worker-terminal-contract.json` is authoritative for required artifacts. When the request explicitly asks for PR evidence or a PR description, also write `artifacts/pr-description.md` on a no-change outcome, stating that the product is unchanged and preserving proof gaps. When a recipe exists, also write:
    - `artifacts/recipe-coverage.md`: proof target -> node -> evidence.
    - `artifacts/evidence-manifest.json`: strict visual selection only. Example: `{"version":1,"preferred_mode":"screenshots","standalone":[{"label":"AC1","covers":["AC1"],"file":"after-ac1.png"}]}`. For state-only proof: `{"version":1,"summary":"No visual evidence required."}`.
    - If `artifacts/recipe-quality.json` is absent, apply the quality section from the task harness's `help --json`, write `artifacts/recipe-quality-input.json`, then run `mm-harness recipe-quality build`. Never hand-author the final artifact.
 2. An explicit request for PR evidence or a PR description selects `/mms-recipe-pretty-pr` for local packaging. Once the retained run and quality report are ready, read that installed skill, apply its evidence gate, and run its package script before the terminal mark, including no-change and `awaiting-review` outcomes. Keep pending human review explicit in the draft; packaging does not approve claims or authorize publication.
-3. `./mark complete --mark-last` (or `./mark no-change --reason "..."`) only when the task checks permit it. Otherwise return the pending review status and local draft paths without completing the task.
+3. `./mark complete --mark-last` (or `./mark no-change --reason "..."`) only when the task checks permit it; criteria awaiting review go to the run gate with the completed task. Otherwise return the failing check and local draft paths without completing the task.
 
 ## After task completion