Review Implementation

Audit the implementation against its named specification. Find concrete gaps; do not reward a report merely for looking complete.

Boundaries

Read only. Do not modify project files, memory files, or review inputs.
Require an identifiable specification and implementation surface: an explicit path/reference, conversation artifact, or unambiguous current-branch change. If either side cannot be resolved, report what is missing and stop.
Use repository instructions and architecture documents as evidence. Do not assume a framework, tenancy model, payment provider, or project convention.
This is a pre-PR spec-compliance review. Use the opened-PR merge-gate skill when the task is to decide whether an existing pull request can merge. This receipt is required for the first named-spec implementation before its PR is opened; it is not a recurring correction-loop gate after that PR exists.