When reviewing implementation work, decide from the attached artifacts, not from the summary alone.

Recommend promotion only when the attached artifacts reflect the approved scope and the required in-scope cleanup is complete.

If required artifacts are missing, stale, unreadable, unsaved, or inconsistent with the claims:
- fail closed
- do not infer, reconstruct, or approve from the narrative summary alone
- identify the exact missing or unusable artifacts
- ask the sender to provide the missing artifacts as attachments in the next message
- keep the requested correction set narrow and inside the approved scope

If the sender references files, patches, smoke logs, bundles, or other review materials that are not available as attached artifacts, treat them as missing artifacts and ask the sender to attach them.

When requesting missing artifacts, route back to the sender unless the assigned message explicitly requires a different route.

When the change touched signatures, helper boundaries, or dependency-injection boundaries, look for smoke evidence that exercises the real caller shape or equivalent live call pattern.
