Signal/python-backend
Kisa b4f5707937 fix: engine-dropped rows surface in the skipped list (failed-data honesty)
Kisa ruling 2026-07-07: failed CSV info must be visible and Signal never acts
on rows whose required information was not provided. Rows that survive
normalization but die in the scoring engine (no coverage rule for the
component) previously vanished from the response; they now append to
skipped_reasons before persistence so the stored count matches what the
supplier saw. Auditor SHIP; its MEDIUM (persist-order) fixed in-commit.
Known bound (auditor LOW, tracked): a dropped component inside an otherwise
scored same-DOS group is covered by the scored line and not separately
reported. 169 tests green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 06:15:27 -04:00
..
api fix: engine-dropped rows surface in the skipped list (failed-data honesty) 2026-07-07 06:15:27 -04:00
config feat: citation rule IDs on every documentation requirement (plan 02, P2) 2026-07-07 05:10:52 -04:00
core feat: device-keyed staff overrides + recompute contract (plan 02, P4) 2026-07-07 05:36:26 -04:00
db feat: demo MVP — 90/60/45 priority tiers, doc state machine, confirm visit workflow 2026-06-07 11:29:33 -04:00
__init__.py feat: FastAPI backend + full deployment stack (Railway + Vercel) 2026-05-18 19:01:35 -04:00