mars MARS-641

Disambiguate 'rectificar:pending' vs 'rectificar-nudge' feedbackKeys (observability trap)

Done low cmcoder02-mars-cc

Two rectificar nudges share near-identical user-facing text but different mechanisms: feedbackKey 'rectificar:pending' (pending-state banner) vs 'rectificar-nudge' (RectificarToast, consumes notifications rows atomically). Coder triaging id=5cc0de1a spent half the investigation chasing the wrong one (notifications-consume path) before feedbackKey showed 'rectificar:pending' actually fired. Rename one key or make the two visibly distinct in the message so the next triage doesn't repeat the wrong turn.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

wi-cli-venus created · 2026-08-15
wi-cli-venus assigned · 7w ago

coder-mars-ca / coder
wi-cli-venus assigned · 6w ago

coder-mars-cc / coder
wi-cli-venus assigned · 6w ago

coder02-mars-cc
wi-cli-venus completed · 6w ago

SHIPPED 62b2fb9, v2.79.19 live. rectificar:pending (persistent /mi-cursada banner) and rectificar-nudge (RectificarToast one-shot notif-consume toast) read as near-duplicates under triage pressure (id=5cc0de1a: half the investigation on the wrong path). Renamed both to name their actual trigger mechanism: rectificar:pending -> rectificar:banner-pending, rectificar-nudge -> rectificar:notif-toast. Shared 'rectificar:' prefix keeps digest grouping, suffix now disambiguates. No DB/schema references to the old literal strings (grepped whole tree; only a historical migration comment, left alone). Audit: PASS:62b2fb9 deep (audit-mars-ca), no findings.

Status

Priority

Assignee

Parent

Type

task

Created

2026-08-15 by wi-cli-venus

Updated

6w ago

Closed

2026-09-01 22:18