test(ui): prove TopFiles state and keyboard behavior in Chrome

[seonghobae]

Issue #340 browser-evidence owner. Exact head remains 7f178131ab1e75ddf325a93133eda4e8ca75ee54. Its Test 34527975282 is terminal FAILURE with the original authoritative real-browser RED: after 68/68 Vitest files and 271/271 tests passed, workflow-concurrency checks passed and Chrome launched, the rendered page failed at top-files-page-horizontal-overflow:375. Failure artifact npm-test-failure-34527975282-1 has digest sha256:08c52be6a457e2fa19d327f9f8d7949cb65363707ebfa44d7d085f0e922c9ee5. The root-only Chrome sandbox adaptation was therefore not the blocker.

That RED was carried forward without weakening its 375/768/1024 assertions. Successor #379 localized the overflow to long unbroken cleanup notice content and repaired it with component-local wrapping/intrinsic sizing. A separate browser teardown defect was then isolated as #388 and repaired with browser-level /json/version discovery, CDP Browser.close, launched-process exit proof, abnormal-only process-group fallback, and one-shot profile removal without retry widening.

Current successor #379 exact is 5b533ca665d12c4efbe9f633dc9a4055b11ad129 and exact Test 34572975401 is terminal SUCCESS. The unchanged-head Ubuntu rerun completed the Rust/backend/cloud/archive/npm/frontend/browser/build path, while Windows, macOS and real llama.cpp were also SUCCESS. Issue #388 is closed completed. This successor evidence proves the repaired current browser lineage; it does not change this historical #375 head from RED.

Dependent #380 exact 6b5b587b432b52ef3f47b0f2b95d621ff70b70b3 is ordinary/non-force stacked on #379 and differs semantically only by the deliberate TopFiles accessibility delta. Exact Test 34573067654 is terminal SUCCESS, including sequential keyboard reachability, visible focus, PageDown scrolling, fragment continuity and inherited responsive/state scenarios.

Issue #340 remains broader than Chrome responsive repair. Font fallback #390 exact 0930488ccd1f4945332a6616334663c4b26f5706 is terminal-GREEN for its slice, and localization foundations #392/#396/#398 are terminal-GREEN for versioned ledger, immutable resource admission and bounded Tauri projection respectively. Shipped localization still requires native SQLite persistence/cache population, actual stable screen-key rendering, locale-selection and explicit missing-message/fallback policy, realistic KO/EN/JA/ZH/VI/ES/DE/FR state/focus/long-copy/CJK expansion E2E, and Windows WebView2/macOS WebKit evidence. UI Delivery Gate remains FAIL.

Keep Draft as historical RED owner until the successor lineage and broader UI owner are normally integrated. No force-push, destructive rebase, source/SSR substitution for rendered-browser evidence, self-approval, broad sandbox disabling, global overflow clipping, teardown-error suppression, retry/tolerance widening, predecessor/child evidence transfer, or gate weakening.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}