mars
MARS-69
UX Friction (epic): reduce user pain points surfaced by toast/error telemetry
Done normal
unassigned
Sub-tickets — 1/1 done
Activity
-
Driving from MARS-70 map; coder-mars-cc started the #1 offender (600+ Seleccioná-la-pieza nags on /practicas/nueva) as root-cause-first behavior fix, orthogonal to MARS-97 Stage-3
-
Code live in 18b5ec4 since 2026-08-21. review-depth.sh 18b5ec4: DEPTH=deep CHECK=2c REASON=not provably inert src/app/(protected)/practicas/nueva/actions.ts SAMPLED=no. Under Elazar's MSG-309 ruling the coder now closes its own WIs, but a deep item cannot close without PASS:<sha>. audit-mars-ca was absent from the roster when this shipped; it is live again and the cold brief went out (tag coder-mars-cc-mt42amqq192k). Blocked on that verdict, NOT on remaining work.
-
Code live in 18b5ec4 since 2026-08-21. audit-mars-ca BLOCK:18b5ec4 P1 on the orphan-cleanup path; remediated under MARS-660 and cleared: PASS:032cdb5 deep, PASS:c01c17d deep. Live version 2.74.25 confirmed against the remote package.json on main at check time. Closing on the remediation chain, not on the blocked SHA.
-
BACKFILL written 2026-09-02 by coder-basquetwi-cc, authorized by the owning lane. Historical repair for the bug fixed in 526f6b0: closing a BLOCKED row directly to a closed status wrote only the 'unblocked' event and never the terminal one, and the close reason landed on that unblock event. The row was always correctly closed (closedAt stamped, questions closed, status correct); only the ledger was wrong, and its last word read 'unblocked' - which reads as still-open to anyone reconciling by event rather than by status. THIS EVENT IS NOT CONTEMPORANEOUS: its timestamp is the repair's write time, not the real close time, which is in closedAt. The original close reason has been left where the bug put it, on the unblock event, deliberately - it is the only artifact showing the bug's shape.
task
2026-06-09 by wi-cli-venus
7w ago
2026-08-22 07:44