Code Review

Blocking Conditions

Mark as blocking if:

• correctness is still ambiguous
• evidence does not prove root-cause closure
• financial or privacy-sensitive behavior changed without explicit verification

When blocked for ambiguity, require a human decision record only when ambiguity remains after applying the Spec-Clarity Gate (canonical definition in .github/copilot-instructions.md).

Reference: debugging-assistant escalation policy and qa-testing verification matrix.

Repo-Specific Review Risks

• Single-file userscript constraint: no module imports, no build steps, no file splitting, keep all helpers inside the IIFE.
• Financial calculations: guard zero division, use Number.isFinite(), preserve null vs 0, round only at display.
• API interception safety: clone responses before reading, match URLs precisely, avoid blocking the native response, prevent fetch/XHR loops.
• XSS prevention: never render user data via innerHTML, avoid inline event handlers, use textContent or DOM nodes.
• Storage key compatibility: keep key formats stable, encode separators, add migrations if any key shape changes.
• Sync/security boundaries: no data egress by default, encryption/auth flows unchanged unless explicitly intended and verified.

Output Format

• Summary
• Critical Issues
• Suggestions
• Testing

References

• Review guidelines and checklist