error-tier toast/error-shown rows would page despite mig 074 mute (warn-only scope)
error-tier toast rows (category=toast, level=error/fatal) would page uncondtionally per mig 074's applog_notify_error_trg (only the warn branch has a category IS DISTINCT FROM toast carve-out) - but this is UNREACHABLE through the sanctioned write path (feedbackTier() in feedback-core.ts is a closed info/warn mapping, category=toast has exactly one writer, feedback-actions.ts:95, fed only by feedbackTier's output). DECIDED 2026-09-11 (coder-mars-cc): this is an intentional bypass-detector, not a gap. Do NOT widen the mute. If a category=toast row ever arrives at error/fatal tier, that means a caller bypassed feedbackTier() entirely, and paging on it is the correct and only signal that would catch it. Left open as documentation of the invariant, not as pending work.
Activity
-
3
-
Nuanced 2026-09-11: migration 074's page trigger has no category=toast carve-out on error/fatal levels (only the warn branch has 'category IS DISTINCT FROM toast' - applog_notify_error_trg, db/migrations/applied/074). That gap is real and unenforced at the DB level. But currently UNREACHABLE through the sanctioned write path: feedbackTier() (feedback-core.ts:126-128) is a closed mapping - severity==='warning' -> warn, else info - it can never emit error/fatal, and category='toast' has exactly one writer fleet-wide (feedback-actions.ts:95), fed only by feedbackTier's output. So a category=toast,level=error row can only arise from a caller bypassing the sink entirely (a contract violation, not a feedback-path bug). This is a PM call, not an implementation gap: (a) widen mig 074's mute defensively to cover error-tier toast too, or (b) treat current behavior (paging on that shape) as an intentional detector for a sink-bypass and leave it as-is. Left open pending that call, priority 3.
-
4
-
was: Surfaced from VENUS-325 alert-rail measurement (coder-mars-cc, 2026-07-30): mig 074's friction mute (mig 074) is scoped to level=warn AND category=toast only. Mars's error/fatal DB-trigger branch has NO category test at all, so an error-tier toast/error-shown row would page today if one occurred — a live exposure with a quiet history, not a closed issue. category=toast/error-shown is mars's LARGEST admitted alert class (695 rows/29 routes), currently all warn-tier (last row 2026-06-06, looks fixed upstream by a level change) but the gate does not enforce that. Decide: widen mig 074's mute to cover error-tier toast rows too, or confirm error-tier toast is intentionally pageable and accept the exposure.