lukaszraczylo c23b09cc09 fix(v0.6.4): rollback removes the proposal's ab-tracking entry ...

adam-rollback.mjs's docstring always claimed it "removes the ab-tracking entry
(so it doesn't re-trigger)", but executeRollback() never did. Consequence: a
rolled-back proposal kept being re-detected as `regressed` on every subsequent
/reflect, which triggered endless `not_found` rollback attempts (the applied
file is already gone) and noisy ## Regressions sections.

executeRollback now deletes the matching ab-tracking.jsonl row by proposal_id
after the move, preserving all unrelated rows. Surfaced by running ADAM's own
/reflect loop a second time (two zombie regressions: 2026-05-16-002 and
2026-05-22-001).

Tests: 138 -> 140 (rollback purges the entry by id; an unrelated entry is
preserved).

2026-05-29 13:50:38 +01:00

..

adam.md

fix(v0.6.4): rollback removes the proposal's ab-tracking entry

2026-05-29 13:50:38 +01:00