You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d4b1282
Browse filesBrowse the repository at this point in the historyBrowse files
fix: round-7 review polish — threat normalization in review lane + fail-closed partials
- Review runner: composite `safety.threats` are normalized before joining
review issues — engine severities (`critical`/`high` → error, `medium` →
warning, `low` → info) and the byte-tuple `location` dropped, so the
quality lane classifies threats as errors instead of suggestions.
- `check --checks safety`: a `success:false` envelope now appends the
fail-closed error finding even when partial sub-error threats were
returned — `--fail-on error` can no longer pass a crashed scanner.
- Semantics tool: abstentions (`validation_errors`) set
`metadata.success: false` so telemetry records the soft failure
(consistent with query-pii); contract test updated accordingly.
- Shared `byteRange()` helper replaces the duplicated inclusive-range
formula in `runSafety`/`runGrade`.
- `pii-detector-e2e.test.ts` defers the pii-detector import until after the
NAPI-availability guard (static import defeated the guard).
- Fixture cleanup: stale `matched_pattern`/comment from the old OR 1=1
payload removed; new fail-closed partial-threats test.
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments