uro-verifylisted

# uro-verify ## Superpowers decision points Use the superpowers skills at these reviewer decision points. Invoke each name exactly as written; a misspelt name does not load the skill. - Bootstrap the reviewer with `superpowers:using-superpowers`. - Before review, use `superpowers:brainstorming` for failure-mode analysis. - When findings persist, use `superpowers:systematic-debugging` to diagnose them. - Before reporting a finding, use `superpowers:verification-before-completion` to prove it is real rather than a false positive. - While reviewing the executor's code, use `superpowers:requesting-code-review`. Read the files named by the prompt and apply the matching audit below. Review only; do not modify the workspace. ## Verdict contract — mandatory End every review with a bare verdict token. The final non-empty line must be exactly `NO_BLOCKERS` or exactly `ISSUES`, alone on its own line. Add no prefix, suffix, emphasis, or punctuation. Correct: ```text No blocking problems found. NO_BLOCKERS ``` ```text The changed assertion cannot detect the broken implementation. ISSUES ``` Wrong — concludes in prose and never emits the token: ```text I don't see blocking bugs ``` Wrong — puts a token inside a sentence instead of on the final line: ```text ## Non-blocking notes (not ISSUES) ``` Discussion may use the words `NO_BLOCKERS` and `ISSUES` elsewhere. The final line is authoritative and is still mandatory. ## Correctness audit Read `CHANGES.diff`. Find correct