basquetWi + New ticket
venus VENUS-275

Telemetry-quality: advisory-only log rows mislabeled as error-shown, inflate friction digest

Done normal cvcoder-venus-cc

Found during EVO-62/VENUS-274. Non-blocking, log-only advisories (antecedente-sin-hijos; historically complicaciones-intra pre-removal) write category=toast/action=error-shown despite showing the user NOTHING (no toast, no submit block) — these inflate the friction digest with non-friction rows. Fix: give advisory-only logs a distinct action (e.g. 'advisory-logged') or a detail flag the digest query can exclude, so category=toast/action=error-shown stays true user-facing friction only.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 2026-07-18
  • wi-cli-venus assigned · 5w ago
    coder-venus-cc
  • coder-venus-cc completed · 1w ago
    FIXED BY 932b75a (VENUS-11, v1.17.36 line), no new commit. The only advisory-only error-shown producer, practica.antecedente-sin-hijos, was removed there and replaced by the BLOCKING practica.antecedente-sin-subopcion. Enumerated every remaining emitter (grep logGuardrail, src minus tests): practica-form.tsx:703 (submit blocked, scroll+focus), practica-evaluacion.tsx:57, add-participant-box.tsx:51, practica-detail.tsx:633 - each sets a visible error and returns before the action. The other D3-5 advisory code practica.complicaciones-intra-incompleto is registered in guardrail-codes.ts:71 with NO emitter in src or scripts. Prod (SELECT, 60d toast/error-shown): last antecedente-sin-hijos row 2026-09-20 23:09Z (30 rows total, historic, not backfilled). NOT EXERCISED: log-error route still accepts a registered advisory code if a future client emits one - nothing structurally separates advisory from blocking codes; a new advisory producer would reintroduce this.
task
2026-07-18 by wi-cli-venus
1w ago
2026-10-06 06:58