pluto
PLUTO-495
Stats glossary: footnote + tooltip explaining stat abbreviations in user-facing text
Backlog normal
unassigned
Elazar 2026-07-03: user-facing text shows stat abbreviations with no explanation (example: 'p95 (d)'). Add a footnote + a hover/tap tooltip (tip) explaining what each stat means, everywhere such abbreviations appear (informes cards etc.). Solo: inventory every abbreviation used (p95, p50/median, (d)=días?, op/asist, desbalance, etc.), draft a plain-Spanish one-line definition for each, and send the definitions to PM for Elazar review BEFORE shipping — these are domain terms Elazar owns the wording on. Reuse an existing tooltip primitive (shadcn Tooltip), no one-off. Display-only.
Activity
-
coder-pluto-cc / coder
-
reassigned coder-pluto-cc <- solo-pluto-cc: assignee retired 2026-07-15 fleet-wide solo-agent retirement, work still wanted (Elazar CR, not obsolete) — §Scaffold-Time Retirement Check 7th-surface sweep (pmmaster ask, 2026-07-31)
-
Stage 1 done: inventoried 7 abbreviations across 5 files (latency-card:49-50, docente-productivity-card:54, op-asist-balance-card:41/54-56, informes/page:405, teacher-report:1272/1277). Draft plain-Spanish definitions + 2 open wording questions sent to pm-pluto-cc for Elazar ruling (tag coder-pluto-cc-msa9nbl51ax9). Found: 'Moda' cards named in the WI + PLUTO-121(b) no longer exist at HEAD — scope is 7 terms. Implementation held pending wording; plan = shadcn Tooltip on SortableTableHead label + per-card footnote, no new primitive.
-
Re-filed the wording ruling as eq#56 (topic informes-glosario-abreviaturas, ref_bwi 495) with the full Spanish text ALREADY DRAFTED for all 7 terms, so Elazar can approve rather than answer open questions. Reason for re-filing: the Stage-1 questions went to pm-pluto-cc on 2026-08-01 and no answer was ever recorded here - a question routed through pm is not on Elazar's pane unless it is eq_add'd. Only two things are left genuinely open: whether 'Flag' stays English (recommended: 'Alerta') and whether students see any of these cards, which sets the register. Implementation stays held on that answer; the plan is unchanged (shadcn Tooltip on SortableTableHead + per-card footnote, no new primitive).
-
Board hygiene per pmmaster 10:01: eight rows sat in inProgress at once, which reports nothing. Not actively worked this turn; PLUTO-718 is the single active row. Order: 718, then 688, then the rest.
-
unassigned
-
Unassigned and moved to backlog by pmmaster-evolutiva-cc 2026-09-12. The assigned agent did not exist: coder-venus-cc, db-venus-cc, coder-pluto-cc and db-pluto-cc are all absent from the hub roster and have no tmux pane, and venus and pluto currently have no staffed coder or db lane at all. A todo or inProgress row against an absent assignee reads as staffed-and-underway and is neither, so the status was a lie about this row rather than a claim about the work. The work itself is untouched and the priority is unchanged. Cause of the cluster, and it is a fleet-wide pattern rather than a bookkeeping slip: five auto-succession call sites plus resolvePm can leave a row pointing at an agent that has been deregistered, and nothing reconciles an assignee against the roster afterwards. Filed context: 178 rows across these four names, of which 23 carried a non-backlog status. Restaffing venus and pluto is Elazars decision, not a reassignment I can make.
cr
2026-07-04 by wi-cli-venus
4w ago