pmo-build-reviewlisted

# pmo-build-review ## Purpose Confirm that implementation evidence is ready for review or QA. ## Trigger Use after build work, before review/test, or when checking a PR or patch against requirements. ## Required Inputs Task source of truth, changed-file summary, relevant requirement/design references, test evidence, and configured contracts from `pmo-config/context-map.json`, `pmo-config/policy.json`, and `pmo-config/reference-types.json`. ## Allowed Context Read only work items and code/design artifacts relevant to the change. Use source docs only for disputed requirements. ## Mode Behavior Use `pmo-config/policy.json` for valid statuses, review stages, evidence statuses, and strict triggers. Use `pmo-config/reference-types.json` for reference shape; do not accept free-text evidence where a configured reference is required. ## Execution Steps 1. Map changed work to delivery item IDs. 2. Check acceptance criteria and test checklist evidence. 3. Compare implementation reality with approved Scope, BUILD-SPEC, acceptance cases, Mode, and execution-contract boundaries. Record a candidate Change Request when they differ; do not silently edit a contract to absorb the deviation. 4. Identify possibly omitted affected artifacts as candidate findings; do not claim automated impact discovery is exhaustive. 5. Identify missing review stage or unresolved blocker. 6. Recommend the next gate or corrective action without approving any human-owned gate. ## Output Contract Return review