review-against-intentlisted

<what-to-do> Load the active intent from `intent.md` in the project root — the file is bound to this repository, which makes it the authority on what governs this diff. If `PATHMODE_API_KEY` is set and the file's frontmatter carries a cloud id, also fetch that intent's execution bundle (`get_agent_prompt` with the id) to pick up what the file cannot hold: open PM change requests, findings, handoff notes, and authorization state. Never let `get_current_intent` choose an intent for a repository review: "current" is a workspace heuristic, not a repo binding. If the repository has no `intent.md`, stop and ask for an explicit `intentId` or inline spec instead of guessing. If the execution bundle reports an open PM change request, or says the current repository revision is pending, rejected, or stale, stop before reviewing the diff as delivered work. Name the exact request/revision blocker and direct the agent through `preflight`: a requested spec change must be applied with request-bound `intent_save`, then a signed-in product manager must authorize that exact resulting revision. Never approve code against the superseded or unauthorized spec. Identify the changed files using git diff against the base branch (or staged changes if no base specified). For each outcome in the intent, check whether the changes actually deliver it — with specific file/line evidence. For each constraint, check whether the changes respect it. For each edge case, check whether it's handled. Report: -