Skip to content

fix(context-panel): honest empty state, rebuild label, earlier range - #17355

Closed
chenmingwei23 wants to merge 2 commits into
kirodotdev:mainfrom
chenmingwei23:fix/15520-context-panel-wording
Closed

chenmingwei23 wants to merge 2 commits into
kirodotdev:mainfrom
chenmingwei23:fix/15520-context-panel-wording

Conversation

@chenmingwei23

@chenmingwei23 chenmingwei23 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The Context panel's wording says only true things: an empty panel says whether data will ever arrive, a mid-session rebuild is not labelled as the session's start, and the earlier-turns line adds up with what is on screen.

Three wording problems were left over from #15367 (items 1, 2, 3, 6 and 7 of #15520):

  1. The empty state promised data that never comes. With the crew log switched off, the panel said "No context breakdown recorded for this session yet." Nothing is recorded in that case, so "yet" was false. Deleting the word would have been wrong too: the other three ways to an empty list (a session recorded before the fold, no completed turn yet, every row outside the day window) all fill on the next turn, so for them "yet" is true.
  2. A mid-session rebuild read as the session's start. Every session-start row was labelled "Turn N · session start", so a context rebuild at turn 41 read as a session that began at turn 41.
  3. The hidden count left out the rows listed above the chart without saying so, and looked clickable. "44 earlier turns not shown" did not add up next to a chart starting at turn 46, because turn 41 is listed above. It also read like a control that could reveal turns the fold no longer keeps.

Why it matters

Anyone reading the panel is misled by all three. A user with recording off waits for data that will never arrive. A user reading a rebuild row thinks their session restarted. A user who adds up the numbers finds they do not match and cannot tell why. None of these is a wrong number; each is copy that says something untrue about a correct one.

Not a goal

What changed (motivation → approach → change)

  • Empty state. The panel cannot tell why a list is empty, so the payload now says: context_trace in src/kiro_crew/dashboard/handlers/usage.py returns recording, read through the existing crew_log_enabled(), the same reading the crew-log fold read already returns. The TS interface declares it optional, so a payload from an older gateway reads as recording. When recording === false the panel shows "Context breakdown is not recorded while the crew log is off. Remove KIROCREW_CREW_LOG from the gateway's environment and restart the gateway to record it." This follows the Crew Log panel's own off-state copy, so the user has a way forward. In every other case the existing "…yet" copy stays.
  • Start rows. These rows are session-start compositions, and a unit emits one per start or rebuild. Only turn 1 is the session's start, so only turn 1 keeps "session start". A later start row reads "Turn N · context rebuilt". The number is unchanged.
  • Earlier turns. The count is replaced by a range, as item 7 of Context panel wording: empty state promises data that never comes, rebuild rows read as session starts, hidden count unexplained #15520 recommended: "Turns 1–45 earlier". When some of those turns are listed above the chart, it adds "· 1 of them listed above". That wording is neutral, so it never points to a "session start" row when the row above is a rebuild. A range lines up with the first turn the chart draws, and it does not suggest the turns can be opened. With exactly one earlier turn it reads "Turn 1 earlier".
  • New strings are in all 12 translated locales, en-XA is regenerated, translator context is added to en.context.json, the plural key list is updated, and docs/system-specs/modules/metrics.md describes the new wording.
  • website/capture/context-panel-wording.* is an isolated capture entry and shoot script that render the real ContextBreakdownPanel from fabricated traces. They produced the screenshots below, which are attached to this description rather than committed.

Backwards compatibility

Compatible: the payload only gains an optional recording field. Readers that ignore it keep working, and the panel treats its absence as recording.

Reader: website/src/pages/ContextBreakdownPanel.tsx:earlier_hidden -- chat -- the only reader of the removed pages.contextBreakdown.earlier_hidden catalog keys; it now reads earlier_range / earlier_range_starts / earlier_single, pinned by ContextBreakdownPanel.test.tsx and the i18n key-refs gate (0 dangling).

Tests

  • test/metrics/test_context_trace.py: new test_the_payload_says_whether_the_crew_log_is_recording checks that recording follows the switch, and the payload-shape test now includes the field. test/test_usage.py, test/metrics/test_usage_turns.py and test/test_source_pin_budget.py also pass locally (228 passed).
  • website/src/test/ContextBreakdownPanel.test.tsx: expectations updated to the range wording and the rebuild label. New tests cover the off state (names the way back), the "yet" state, a single earlier turn, and turn 1 "session start" next to a later "context rebuilt". With ContextBreakdownTab.push.test.tsx, SessionBreakdownTree.test.tsx and src/i18n/catalogParity.test.ts this is 141 tests, all passing.
  • node scripts/i18n-check.mjs against the base passes all 19 checks. tsc --noEmit and eslint on the touched files are clean.

Manual verification

Rendered the real panel for every variant with node capture/shoot-context-panel-wording.mjs (Vite plus Playwright on loopback, no gateway), in dark and light themes. The screenshots below come from that run.

Screenshots / video

Recording switched off, then recording on with no turn yet:

Recording off: says nothing is recorded and how to switch it back on

Recording on, empty: keeps the "yet" copy

Turn 1 "session start" next to a later "context rebuilt" row:

Turn 1 session start and Turn 4 context rebuilt

A rebuild at turn 41 with the chart from turn 46 (the case from the issue). It reads "Turns 1–45 earlier · 1 of them listed above":

Rebuild row above, earlier range naming it

Range with nothing listed above, and a single earlier turn

Turns 1–7 earlier

Turn 1 earlier

Related Issues

Fixes #15520

Follow-up: #17349 (items 4 and 5 of #15520).

Pattern harvest

Not generalizable: each of the three is copy that was true for the panel's state before #15367 and went stale when the panel switched to the usage fold. There is no code shape a rule could match.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

@chenmingwei23
chenmingwei23 requested a review from a team as a code owner October 6, 2026 11:29
@github-actions github-actions Bot added readiness: checking Automated validation is still running fork Pull request from a fork (external contributor) labels Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5, fork) — ✅ PASS

Premise-level review of a38610d6eed0b57d340c62d5894d05e2b788d10c via the fork AI-review pipeline — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Check that the start-row label rule, which treats only displayN === 1 as the session start, matches how units number a rebuild that follows a fold reset.

What this change ships

Inventory (6 items) — 6 justified

Intent: make the Context panel's copy state only true things about the empty state, rebuild rows and earlier turns. This is a FIX.

  1. When the crew log is off, an empty panel says nothing is recorded and how to turn recording back on, instead of "yet". — justified
  2. The context-trace payload gains an optional recording flag that reuses crew_log_enabled(), the same reading crew_log.py:415 already returns. The panel is its 1 consumer. — justified
  3. A start row after turn 1 reads "Turn N · context rebuilt" instead of "session start". — justified
  4. "N earlier turns not shown" becomes "Turns 1–N earlier", plus "· K of them listed above" when start rows are listed above the chart. — justified
  5. With exactly one earlier turn, the line reads "Turn 1 earlier". — justified
  6. A screenshot harness for the panel wording is added under website/capture/, which matches the 421 files already there. — justified

[FIRST-PRINCIPLES-REVIEWED] a38610d

Description read

[DESCRIPTION-READ] e32ba28d85a13477cd2a60f4e93fd935056d743c5d7f4f6a92d6649e39b11ac2

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5, fork) — 🔴 BLOCK (blocking)

Design-level review of a38610d6eed0b57d340c62d5894d05e2b788d10c via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: BLOCK

cannot evaluate: missing screenshots of the Context panel's new crew-log-off empty state, the "context rebuilt" row, and the earlier-turns range line.

Blockers

No rendered evidence of this revision for a reshaped panel surface
The diff adds a new empty-state mode to ContextBreakdownPanel (trace?.recording === false ? i18nT('pages.contextBreakdown.empty_off')). It also relabels the start rows (rebuild_row) and replaces the hidden-turn line with earlierText. The description promises screenshots "attached to this description rather than committed". The workflow's evidence list shows 0 attachments downloaded as images, 0 committed images and 0 transport failures, so the "[image removed]" entries are not evidence. Without them I can't judge how the panel looks. Open questions: how a two-sentence env-var instruction sits in an 11px centred muted empty state in a 320px side panel, and whether "Turns 1–45 earlier · 1 of them listed above" fits on one line or wraps badly.
Fix: run node capture/shoot-context-panel-wording.mjs and commit its output under temp-screenshots/context-panel-wording/, or re-attach images that download.
Clears when: the workflow's evidence list names at least the off-state, rebuild-row and range-with-rebuild images for this head SHA.

Watch

The rebuild label depends only on the turn number
turn.displayN === 1 decides "session start" vs "context rebuilt". Suppose a session's turn 1 is outside the day window or was recorded before the fold, and its first visible start row is a real session start at a renumbered ordinal. That row would now read "context rebuilt". The ordinals come from the fold, so this rests on the fold always numbering the true start as 1.
Clears when: a test or a fold-spec citation shows that a genuine session start always has ordinal 1 under the window and the pre-fold cases.

[DESIGN-REVIEWED] a38610d

Description read

[DESCRIPTION-READ] 55d3a66331335cd7bcb439482eac9411ab22c92fb3e90a24656078786408eaf0

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5, fork) — 🔴 BLOCK

UX-level review of a38610d6eed0b57d340c62d5894d05e2b788d10c via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: BLOCK

cannot evaluate: missing screenshots. The image list is empty, so none of the three reworded Context panel strings has been shown rendered.

Evidence gaps

  • Empty state with recording off (empty_off: "Context breakdown is not recorded while the crew log is off. Remove KIROCREW_CREW_LOG…"). This is a two-sentence muted text-[11px] block and no screenshot shows it. It needs a still of the panel with recording off.
  • Rebuild row label (rebuild_row: "Turn {{n}} · context rebuilt") shown next to turn 1's "session start". No screenshot shows it. It needs a still with both rows visible.
  • Earlier-turns line in its three forms: earlier_range "Turns 1–45 earlier", earlier_range_starts "… · 1 of them listed above", and earlier_single "Turn 1 earlier". No screenshot shows any of them. They need stills of each.
  • The description has six images, but each one reached the review as [image removed] and ux-attachments.txt lists no files. The images in the description therefore close none of these gaps. To close them, re-upload the images to the description as github.com/user-attachments assets, or commit them under temp-screenshots/.

Watch

  • "Turns 1–45 earlier" doesn't say what the turns are earlier than. Read alone, it's a sentence fragment, and in this muted text-[12px] line the chart is the only clue. Severity is low: the line shows every time older turns are hidden, but it causes friction, not a failed task. Smallest fix: "Turns 1–45 not charted".

Suggestions

  • empty_off: put the action first and keep it to one sentence, for example "Not recorded: the crew log is off. To record it, remove KIROCREW_CREW_LOG from the gateway environment and restart the gateway."

[UX-REVIEWED] a38610d

Description read

[DESCRIPTION-READ] af803e13d041d1e5ca21d17036005046b9e50ca2ec0409e6e06195c320cc4494

That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review (fork) — ✅ no blocking findings

Reviewed a38610d6eed0b57d340c62d5894d05e2b788d10c via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] a38610d

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review (fork) — ✅ no blocking findings

Reviewed a38610d6eed0b57d340c62d5894d05e2b788d10c via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] a38610d

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 6, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/15520-context-panel-wording branch from edc2438 to a7fdd93 Compare October 6, 2026 12:08
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026
Three wording problems in the Context panel, left over from kirodotdev#15367:

- With the crew log switched off, the empty state said "No context
  breakdown recorded for this session yet." Nothing is ever recorded in
  that case, so "yet" was false. The trace payload now says whether the
  gateway is recording (`recording`, the same reading the crew-log fold
  read already returns). With recording off, the panel says so and names
  how to switch it back on. The other three ways to an empty list keep
  the "yet" copy, because for them it is true.
- Every session-start row read "Turn N - session start", so a context
  rebuild at turn 41 read as a session that began at turn 41. Only turn 1
  keeps that label; a later start row reads "Turn N - context rebuilt".
- "44 earlier turns not shown" did not match the chart starting at turn
  46 (turn 41 is listed above), and it read like a control that could
  reveal turns the fold no longer keeps. It is now a range that names the
  rows above neutrally: "Turns 1-45 earlier - 1 of them listed above".

Copy in every locale, en-XA regenerated, translator context added, the
metrics spec updated, and a capture harness for the evidence screenshots.
Items 4 and 5 of the issue each need a decision first and moved to kirodotdev#17349.

Fixes kirodotdev#15520
@chenmingwei23
chenmingwei23 force-pushed the fix/15520-context-panel-wording branch from a7fdd93 to 508b425 Compare October 6, 2026 15:35
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording fixes look right: recording comes from crew_log_enabled(), so the empty state only says "yet" when data can still arrive, and a mid-session rebuild is no longer labelled the session start. One blocker: this branch commits six PNGs under temp-screenshots/context-panel-wording-15520/. This is a same-repo PR, so screenshots should be attached to the description (gh pr edit --attach or drag-and-drop) instead. Once merged, committed binaries stay in main history for good. Please drop those six files from the commit and attach them to the description. The capture script under website/capture/ is fine to keep.

buluoray
buluoray previously approved these changes Oct 7, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE (code). @iamwhatever's committed-screenshot block is still valid and still unaddressed at 508b4259df, so the PR should not merge until it is resolved.

What it brings: the Context panel stops misleading users in three places. With the crew log off it says nothing will ever be recorded and how to turn recording back on, a mid-session rebuild is no longer labelled as the session's start, and the earlier-turns line now matches the turn where the chart begins.

Reviewed head 508b4259df848151c3eee8763b85e3e9d1002d7e (single commit on merge-base ea7e91c8e6). CI on this head: 96 pass, 8 skipping, 0 failing, 0 pending. Sensitive Change Review passed. Auto-merge is off.

Blocking

None in code logic.

Prior human review: iamwhatever CHANGES_REQUESTED (on 508b4259df)

  1. Six PNGs committed under temp-screenshots/context-panel-wording-15520/. Not fixed: all six are still in the head commit. The review's wording is slightly off: the head is chenmingwei23/KiroCrew, so this is a fork PR, not a same-repo one. The substance still holds, though. The repo allows committed media only for contributors without write access (.gitignore:113-119, .github/PULL_REQUEST_TEMPLATE.md "WITHOUT write access…", docs/ci/ci-and-reviews.md §"What happens to committed evidence at merge"). chenmingwei23 has admin permission on kirodotdev/KiroCrew (collaborators/chenmingwei23/permission), so gh pr edit --attach works for them and that exception does not apply. The First Principles bot's "force-added … as .gitignore:116 tells authors to do — justified" leaves out the write-access condition. This is a repo-hygiene finding rather than a code-logic defect, so it does not change my code verdict. It remains a gate: drop the six files and attach them to the description instead.

Non-blocking follow-ups

  1. start_note contradicts the new rebuild label. Real issue, please fix in this PR if you can. The UX Review flagged this as CONCERNS and the Design Review called it out too. ContextBreakdownPanel.tsx:685 still renders pages.contextBreakdown.start_note ("The session-start turn is shown above the chart so later turns stay readable.", en.json:6874) whenever starts.length > 0. In the issue's own case, a session whose only row is "Turn 41 · context rebuilt", the footnote calls that row the session-start turn, which is the misreading this PR set out to remove. It is not a truthfulness regression against main, where both strings said "session start". It is, however, an incomplete fix within the PR's own stated goal. Smallest fix: neutral wording that covers both kinds of row (e.g. "Turns that load the full context are listed above the chart…"), or pick the copy based on whether any listed row has displayN !== 1. Either way, update the 12 locales and en.context.json.
  2. "Turns 1–N earlier" never says those turns are left off the chart (UX Review suggestion). This is a matter of taste. "Turns 1–N not in the chart" would keep the range and stay non-clickable while saying why the turns are missing. Optional.
  3. Legacy rows with no ordinal. displayN falls back to turn.ordinal || i + 1 (ContextBreakdownPanel.tsx:570). For rows recorded before ordinals existed, and with the day window dropping the true first turn, the first visible start row gets index 1 and is labelled "session start" even if it was a rebuild. The case is narrow and the label behaves exactly as it did on main. Noted only.
  4. The First Principles bot's check ("is turn 1 always the session's real start?"): yes for ordinal-bearing rows. ordinal is the session's own turn position (usage.py:745-747, :861), so a start composition at ordinal 1 is the session start and any later one is a rebuild. The legacy fallback in item 3 is the only exception.

Upgrade impact

  • New gateway with an old SPA: the payload only gains recording, and older readers ignore it.
  • Old gateway with a new SPA: recording is absent, so trace?.recording === false is false and the panel shows the existing "…yet" copy. That is main's behaviour.
  • Catalog: earlier_hidden_* is removed from every locale and from pluralKeys.json. Its only reader was the panel, which now reads earlier_range* / earlier_single (grep finds no remaining earlier_hidden under website/src).
  • Crew log off with turns already on disk: the list is non-empty, so the old data still renders and the off copy appears only when the list is empty. Nothing that works on main is newly refused. No new prompt and no new config.
  • Intended changes: only copy changes. Every number, ordinal and the hidden-turn arithmetic (hidden at :600, which gates whether the line appears) is unchanged.

Error paths

  • recording reads the same crew_log_enabled() as crew_log.py:415. Because that function treats an unrecognised value as off, a typo'd opt-out reads recording: false, which is accurate. Fail-closed, and the copy stays truthful.
  • A missing or older payload falls back to the "yet" copy, matching main. Fail-closed.
  • An empty trace caused by an unreadable fold still shows "yet" (test_an_unreadable_fold_reads_as_nothing_folded), as on main. Not a new path.

What I verified

Verified against source at the head SHA: the diff end to end, crew_log_enabled() semantics (constants.py:148-163), the crew-log fold's matching recording field, the spec update in docs/system-specs/modules/metrics.md (it now describes the range wording, the rebuild label and the off state, so it is not stale), the start_note contradiction (:685 / en.json:6874), and the author's permission level.

Baseline: test/metrics/test_context_trace.py 58 passed; website/src/test/ContextBreakdownPanel.test.tsx 40 passed.

Mutations (each applied alone; file restored afterwards; git status --short clean):

# Mutation Reddens
M1 usage.py:907 "recording": True TestContextTrace::test_the_payload_says_whether_the_crew_log_is_recording
M2 ContextBreakdownPanel.tsx:548 off-branch condition → false does not promise data while recording is switched off
M3 :474 displayN === 1 → true labels only turn 1 as the session start and a later start row as a rebuild, lists a regenerated start turn once, from its newest attempt, announces the start row by its TRUE ordinal, matching what the row displays
M4 :607 startsBeforeFirstShown > 0 → false counts a regenerated turn once when two session-start rows share its ordinal
M5 :613 lastEarlier === 1 → false names a single earlier turn without a range

Each new branch is covered by at least one named test. Not checked: I did not run the full suite, tsc -b or the i18n gate locally (CI is green on this head), and I did not open the six screenshots.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

@iamwhatever thanks, done.

  • The six PNGs under temp-screenshots/context-panel-wording-15520/ are removed by a second commit, a38610d6ee. The capture script stays, as you said.
  • The screenshots are now in the description. They're hosted on a separate evidence branch on the fork, pinned to commit 3b04998673, so nothing image-related is in this PR's final tree.
  • One note: this is a fork PR (chenmingwei23:fix/15520-context-panel-wording), not a same-repo one. To keep the PNGs out of main's history, the first commit 508b4259df still contains them, so please squash-merge this PR; a merge or rebase merge would carry them into main.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running labels Oct 7, 2026
@github-actions github-actions Bot added the readiness: action required A blocking check or review needs attention label Oct 7, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

@iamwhatever thanks for the review. Where it stands on the screenshots:

  • The Design and UX review lanes only collect evidence from user-attachments links in the description or from images the PR commits under temp-screenshots/. The fork-branch links I used after your review left them with nothing to evaluate, so both lanes blocked.
  • Per the maintainer rule, review-lane evidence is committed under temp-screenshots/<issue>/, a path CI ignores. So the six PNGs are back in the PR, rather than attached: they're now under temp-screenshots/15520/ in their own second commit. The fix commit contains no images, and the capture script stays, as you suggested.
  • The fix continues in fix(context-panel): honest empty state, rebuild label, earlier range #17734, an upstream branch rebased onto current main with the same change. I'm closing this fork PR in favour of it.

Could #17734 be squash-merged, so it lands as one commit?

@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Context panel wording: empty state promises data that never comes, rebuild rows read as session starts, hidden count unexplained

3 participants