Review in layers
First check app and package identity, then data ownership and field types. Review operation admission separately from read policy: a caller who can invoke a command does not automatically gain broad reads. Confirm guards are ordered before effects, child and external work have clear ownership, and retries cannot repeat a business outcome. Review pages as projections of existing authority, never as security barriers.
Ask the agent to make a focused change, run the source check and relevant real workflow checks, and report the exact commands and scope. Treat successful compilation as syntax/type evidence, not proof of business correctness or deployment success. Do not accept invented language constructs, CLI commands, providers, or generated code changes without checking the grammar and build lifecycle.