refactor(mobile): share file header actions and search configuration

[juliusmarminge]

File preview and browsing routes maintained separate native and Android header markup.

Declare local FilesBrowserHeader and FileHeader components in ThreadFilesRouteScreen.tsx. Both configure the shared ScreenHeader API, which selects the platform renderer. File modes and actions have one menu definition; search and Android hardware-back handling belong to the core. File loading, preview state, and navigation handlers remain in the route. This PR changes one existing file.

Validation:

• Mobile workspace typecheck and targeted lint passed. Lint reports existing warnings in the route bodies.
• Mobile unused-file and unused-dependency checks passed.
• 81 tests in the focused header, navigation, file, terminal, archive, and review suite passed.
• Both production platform exports succeeded. Source maps verify the matching core renderer and platform hooks.
• Integrated-stack simulator verification is recorded below.

Stacked on #12389.

Runtime verification on September 18, 2026: the integrated stack at 47a3dcb was tested on an iPhone 17 Pro simulator (iOS 27.0) and T3Code_API_36_1 emulator (Android 16.0), one at a time. Compatible development clients were built and installed from this checkout, then connected to a disposable environment with seeded Git projects. Coverage included Home/list rendering, thread navigation, file search and word wrap, terminal menus and session selection, review diff selection, archive menus, and Settings Add Environment / scanner open and close. Temporary connections were removed and the devices and test servers were stopped. Tablet layouts, QR decoding, and Live Activity start/update/stop were not exercised. Screenshots use seeded demo content; any test counts in demo messages or terminal output are fixture text, not validation results.

Both searches found environmentPresence.ts in the seeded project. Android autofocus was observed, and hardware Back closed search, cleared the query, and kept Files open; another Back returned to chat. File actions toggled word wrap, reopening the menu showed the updated label, and the original setting was restored.

iOS file search	Android file search

The pre-existing iOS archive keyboard issue and stale-connection loading limitation are recorded with comparison evidence in #12399.

Prepared with Codex.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ No successful main baseline artifact is available yet. This run establishes the initial measurement.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	—	13.5 KiB	—	15.1 KiB	✅
Codex	Thread snapshot wire	—	7.1 KiB	—	7.3 KiB	✅
Codex	Live turn WebSocket wire	—	6.5 KiB	—	7.8 KiB	✅
Codex	Live turn WebSocket decoded	—	56.3 KiB	—	66.4 KiB	✅
Codex	Live turn messages	—	10	—	21	✅
Claude	Total thread wire	—	13.5 KiB	—	15.1 KiB	✅
Claude	Thread snapshot wire	—	7.1 KiB	—	7.3 KiB	✅
Claude	Live turn WebSocket wire	—	6.5 KiB	—	7.8 KiB	✅
Claude	Live turn WebSocket decoded	—	57.1 KiB	—	66.4 KiB	✅
Claude	Live turn messages	—	10	—	21	✅

Baseline: unavailable · PR result: 2b4526a · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 114.0 KiB
• Claude decoded thread snapshot: 114.6 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at 6ce292b

Macroscope's review found this PR approvable — The PR consolidates existing file-browser and file-preview header behavior behind the shared ScreenHeader API while preserving search, refresh, navigation, pane, and file-action flows on both platforms. Its runtime impact is limited to localized header presentation and wiring, with no schema, infrastructure, security, billing, or static-analysis changes.

No code changes detected at 2b4526a. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: aff26c9c-fd50-4da3-9254-23b9d3a0d6ce

📥 Commits

Reviewing files that changed from the base of the PR and between 10e095b and 6ce292b.

📒 Files selected for processing (1)

• apps/mobile/src/features/files/ThreadFilesRouteScreen.tsx

Limit details: You’ve used all 10 included reviews currently available.

---

📝 Walkthrough

Walkthrough

The mobile file route replaces platform-specific native headers and menu wiring with shared FilesBrowserHeader and FileHeader components. Search, refresh, navigation, inspector controls, preview actions, and file actions now pass through the shared headers.

Changes

Shared mobile file headers

Layer / File(s)	Summary
Header contracts and shared implementations apps/mobile/src/features/files/ThreadFilesRouteScreen.tsx	Removes native header dependencies and adds shared browser and file-detail header wrappers.
File browser header integration apps/mobile/src/features/files/ThreadFilesRouteScreen.tsx	Routes project, search, refresh, and back-navigation behavior through FilesBrowserHeader.
File detail header integration apps/mobile/src/features/files/ThreadFilesRouteScreen.tsx	Routes file metadata, inspector support, navigation, and file actions through FileHeader.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Refactor

Suggested reviewers: chrisdeeming

Merge Risk: ⚪ Minimal · up to 6ce29

No actionable regression remains in the reviewed change.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 11 functions across 5 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly describes the main change: sharing file header actions and search configuration in the mobile app.
Description check	✅ Passed	The description explains what changed, why the shared ScreenHeader API is used, validation results, runtime coverage, limitations, and UI changes with screenshots. The template checklist is not reprod…

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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

Dismissing prior approval to re-evaluate 3e72d4d

Dismissing prior approval to re-evaluate 6ce292b