Repository navigation
fix(dashboard): explain silent Radar cells on hover and gate them - #12937
Merged
diegosouzapw merged 1 commit intoSep 10, 2026
Merged
diegosouzapw merged 1 commit into
diegosouzapw merged 1 commit into
Conversation
maxmad64bis
force-pushed
the
fix/batch12-radar-silent-cells
branch
from
September 7, 2026 10:53
117ab11 to
ec788d6
Compare
maxmad64bis
force-pushed
the
fix/batch12-radar-silent-cells
branch
from
September 10, 2026 11:50
ec788d6 to
cf14390
Compare
diegosouzapw
merged commit Sep 10, 2026
4c10baa
into
diegosouzapw:release/v3.8.51
9 of 16 checks passed
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…egosouzapw#12937) Validado numa worktree combinada com a onda de dashboard/monitoring desta leva sobre `release/v3.8.51`: typecheck:core limpo, check-api-typecheck OK (289), check-file-size OK após rebaseline, 130/131 nos testes focados — a falha restante é asserção de tempo de parede sob carga, verde 6/6 isolada. Sentinela que não se explica (`—`, `?`) faz o leitor inventar a razão. Explicar no hover é metade; o `check:radar-sentinels` é a outra — sem o gate, a explicação apodrece na primeira coluna nova.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Radar catalog table rendered absent data as bare sentinels: empty limits, unknown context windows, and unreported capabilities showed
—/?with no explanation. Each now explains itself on hover, and a newcheck:radar-sentinelsstep keeps it that way.(release/v3.8.51 not green at branch time; no new failures from this change — focused suites below are green).
Related Issues
Validation
npm run lint(targeted files only — full run in CI)Focused runs, all green: radar suite 21/21 (
tests/unit/dashboard/radar-catalog-table-limits-training.test.tsx),i18n:check-ui-coverage --threshold=65PASS,check:radar-sentinelsall-invariants-hold. ERR6 evidence: frmissing 10 → 13(+3 asserted) at--threshold=100, restore verified byte-identical (+3 lines only).Tests Added Or Updated
Coverage Notes
Reviewer Notes
radarPage.*UnknownHelp) inserted surgically (+3/-0 per locale, same__MISSING__:<EN>sentinel format as neighboring lines;i18n:sync-uideliberately NOT run — it reorders every locale to EN key order and backfills 7–10 unrelated pre-existing missing keys per locale). EN shown at runtime via fallback.trainsOnPrompts: false/absent intentionally still renders no badge (shipped feat(radar): show the rate limits and training disclosure the feed already sends #12320 contract, locked by test).