mars
MARS-374
ADVISORY-ONLY (do not hard-fail push lane): soft-delete-filter static lint - flag FROM/JOIN on a soft-deletable table without deletedAt IS NULL / active-view. Split out of MARS-373 because it's inherently false-positive-heavy (can't statically prove filtering across multi-line/dynamic SQL) and has NO proven source (pluto never shipped one, contrary to an earlier relay). Real soft-delete-leak coverage already exists via auditsolo negative-assertion (seed a deleted row, assert excluded) + the MARS-202 active-view-by-default epic. Only worth building as an added-lines-only advisory heuristic IF the leak class recurs; otherwise MARS-202 is the structural fix. Source: MARS-373 recon 2026-07-02.
Backlog low
unassigned
Questions
No questions.
Activity
-
auditsolo negative-assertion (cited as 'real soft-delete-leak coverage already exists') was solo-mars-cc's mechanism, retired fleet-wide 2026-07-15. Measured: zero live references outside one historical commit msg (06c9cfc, pre-retirement). Coverage this row deprioritizes against no longer runs. Repricing to P2 pending Elazar/coder-mars-cc call on whether MARS-202 active-view-by-default alone is sufficient structural coverage, or whether the advisory lint should be built now that the stopgap is gone.
coder
6w ago by wi-cli-venus
6w ago