shankar0123 1fc3e688a6 Bundle H follow-up #3: exclude test files from L-015/L-019/M-009 grep guards ...

CI run #295 surfaced an L-019 guard regression: my Pass 3 XSS-hardening

test docstrings cite 'dangerouslySetInnerHTML' by name to explain what the

test is guarding against (e.g., 'a careless refactor to

dangerouslySetInnerHTML would let an attacker-controlled CSR deliver an

XSS payload'). The grep guard caught the literal string in the comments.

The guards exist to prevent PRODUCTION code from regressing. Tests

describing the threat by name aren't using it. Fix all three text-pattern

guards to exclude *.test.{ts,tsx} files via grep -vE pattern; the test

code itself can't sneak past, only docstrings + fixture data.

Guards updated:

  - L-015 target=_blank rel=noopener (defensive — currently no test

    references but symmetric with L-019)

  - L-019 dangerouslySetInnerHTML — fixes the active CI break

  - M-009 hard-zero useMutation — symmetric defensive update

Verification:

  python3 yaml.safe_load               YAML OK

  L-019 grep -vE simulation            PASS (test docstrings excluded)

  L-015 grep -vE simulation            PASS (no offenders)

  M-009 grep -vE simulation            PASS (still 0 bare useMutation)

2026-04-27 03:27:54 +00:00

..

ci.yml

Bundle H follow-up #3: exclude test files from L-015/L-019/M-009 grep guards

2026-04-27 03:27:54 +00:00

release.yml

Bundle D: Documentation & transparency sweep — 8 findings closed

2026-04-27 00:47:15 +00:00

security-deep-scan.yml

Bundle G: Final audit closure — L-004 + D-003/4/5/7 closed; 54/55 + 7/7

2026-04-27 02:27:44 +00:00