chore: advance TopFiles owner onto current scan/navigation owner

[seonghobae]

Current-lineage TopFiles accessibility integration parent. Exact head remains 7011c2c330d8ea20bf5a5520f43bf4338ee4c3ed. Predecessor da079fe365c2189e9d12df556114939bf9f6eaeb, Test 34439672546, is terminal SUCCESS; that historical evidence does not transfer automatically to descendants.

This parent rejected the earlier focus-outline-only hypothesis after review showed visible focus geometry alone did not explain document horizontal overflow. Browser owner #375 exact 7f178131ab1e75ddf325a93133eda4e8ca75ee54, Test 34527975282, supplied the realistic buyer RED: 68/68 Vitest files and 271/271 tests passed, Chrome launched, then top-files-page-horizontal-overflow:375 failed.

The downstream responsive lineage repaired that RED without weakening assertions. Current child #379 exact 5b533ca665d12c4efbe9f633dc9a4055b11ad129 contains component-local long-token/intrinsic sizing fixes plus the separate #388 browser-lifecycle repair: /json/version browser CDP, Browser.close, launched-process exit wait, abnormal-only process-group fallback, and one-shot profile removal without retry widening. Exact Test 34572975401 is terminal SUCCESS on that current child. Issue #388 is closed completed.

Dependent #380 exact 6b5b587b432b52ef3f47b0f2b95d621ff70b70b3 is ordinary/non-force stacked on #379 and has only the deliberate TopFiles accessibility delta relative to it. Exact Test 34573067654 is terminal SUCCESS: Ubuntu Rust/backend/cloud/archive/npm/frontend/browser/build, Windows, macOS and real llama.cpp are GREEN, and the browser diagnostic reacquired sequential keyboard reachability, visible focus, PageDown scrolling, fragment continuity and inherited responsive/state scenarios. These downstream exact-head successes do not convert this #373 head into independently tested GREEN.

Broader issue #340 remains open after the Chrome lineage repair. #390 exact 0930488ccd1f4945332a6616334663c4b26f5706, Test 34585802287, is terminal SUCCESS for explicit CJK/root font fallback. #392/#396/#398 are terminal-GREEN for the versioned translation ledger/cache foundation, immutable bundled-resource admission, and bounded fixed-resource Tauri projection. DiskSage still lacks native SQLite translation persistence/cache population, actual screen-wide stable-key rendering, locale-selection and explicit missing-message/fallback policy, realistic KO/EN/JA/ZH/VI/ES/DE/FR normal/loading/empty/error/permission + keyboard/focus + long-copy/CJK expansion acceptance, and Windows WebView2/macOS WebKit native-shell evidence. UI Delivery Gate remains FAIL.

Keep Draft. No force-push, destructive rebase, self-approval, global clipping, tolerance widening, source/SSR substitution for real browser evidence, teardown-error suppression, keyboard-access removal, downstream 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.}

[seonghobae]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review skipped: 177 files exceed the limit of 100.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.