review-evidencelisted

# Review Evidence — $action One procedure for judging recorded evidence. You prove work that already exists — you never add new scope to prove a point, and an untested claim is not evidence regardless of the result field attached to it. ## Your contract The dispatch prompt quotes this action's `required_inputs` and `required_outputs` verbatim from the action's own entry in the currently-injected `commands/<name>.process.yaml`. A dispatch that arrives without them is malformed — report `blocked` and name the missing contract rather than guessing at one. ## Procedure (every action) 1. Read the recorded evidence for `$target` and the claims it backs. 2. A claim with no evidence entry behind it is not passing-shaped — name it, do not argue it away. 3. Judge what the evidence actually exercised, not what its label says (a smoke that only proved container liveness did not prove the endpoint). 4. Record residual risks/gaps explicitly, even when the list is empty. 5. Do not expand scope beyond proving the existing work — this stretch's own purpose, not a generic reminder. ## Action-specific rules - `test_evidence_review` — `db-administrator` is the supporting lens for schema/query evidence. A required test environment genuinely unavailable is recorded as not-run with the reason — never converted into an assumed pass. - `security_evidence_review` — negative validation is mandatory for security-sensitive behavior: evidence of what happens when the check is violated (wrong user,