fix(mobile): refresh Git status after reconnect

[juliusmarminge]

After a long background, the mobile Git status stayed stale on resume. This corrects a freshness regression made visible by #16305; it is not a performance change. Before #16305, the idle refresh loop in the Git sheet happened to refresh status after a reconnect. With the loop gone, the selection refresh only ran when the thread or cwd changed, so a reconnect kept showing the server's cached status. In the release simulator, adding a file while backgrounded and then resuming issued no vcs.refreshStatus, and the More sheet showed 1 file changed while the header menu still said Clean.

The quiet selection refresh in useSelectedThreadGitActions is now also keyed on the environment being connected, and it is skipped while the environment is away. A long background makes the supervisor reset, the connection goes through connecting/reconnecting back to connected, and each mounted consumer of the hook sends one quiet refresh. This is one refresh per mounted hook, not one global refresh: with the More sheet open, the thread route and the sheet each send one.

Verification

Release simulator (iPhone 17 Pro, iOS 27, Hermes, no Metro). Isolated fixture workspace on a plain 300-message synthetic thread. Background for more than 16 s, change the workspace, resume. Counts come from server RPC trace spans.

Bundle	refreshStatus on resume	Header Git menu
Before: 6e13d8f, no patch	0	Clean (stale)
This PR alone (521c10fc…)	1	Clean (still stale; the iOS header needs #16330)
This PR + #16330 (068d9912…)	1	1 changed, then Clean after deleting the file

On the combined bundle, with the More sheet left open across the resume, the trace shows two refreshes (one per mounted hook) and the open sheet updates to 1 file changed.

Evidence: git-reconnect-evidence.json has the aggregate counts, bundle hashes and method. Raw traces are private and not published.

use-selected-thread-git-actions.test.tsx has 4 tests: no self-loop, refresh on selection change, a single refresh after reconnect, and waiting for the first connect. Reverting the hook change fails both reconnect tests. Mobile typecheck and targeted lint pass.

Not claimed: CPU, battery, or latency impact; physical-device or Android runs. With this layer alone, the iOS header menu still shows the stale status; #16330 fixes that.

Opus 5.5 via Claude Code in T3 Code.

🤖 Generated with Claude Code

---

[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	—	5.0 KiB	—	6.8 KiB	✅
Codex	Thread snapshot wire	—	3.8 KiB	—	4.9 KiB	✅
Codex	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Codex	Live turn WebSocket decoded	—	20.9 KiB	—	29.3 KiB	✅
Codex	Live turn messages	—	2	—	8	✅
Claude	Total thread wire	—	5.0 KiB	—	6.8 KiB	✅
Claude	Thread snapshot wire	—	3.8 KiB	—	4.9 KiB	✅
Claude	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Claude	Live turn WebSocket decoded	—	21.2 KiB	—	29.3 KiB	✅
Claude	Live turn messages	—	2	—	8	✅

Baseline: unavailable · PR result: 600d35b · 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: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 584c331

Macroscope's review found this PR approvable — This is a focused mobile bug fix that refreshes existing Git status once after an environment reconnects while avoiding requests during disconnection. The production change is isolated and supported by tests covering reconnect behavior and render-loop prevention.

No code changes detected at 600d35b. Prior analysis still applies.

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

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: 59424a59-c57c-4402-829a-c6b13fdaaba5

📥 Commits

Reviewing files that changed from the base of the PR and between 4aaad54 and 600d35b.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: 5f9c505b-72e4-4cb7-bdc1-9ed16ff85e33

📥 Commits

Reviewing files that changed from the base of the PR and between 3eb1c7a and 584c331.

📒 Files selected for processing (2)

• apps/mobile/src/state/use-selected-thread-git-actions.test.tsx
• apps/mobile/src/state/use-selected-thread-git-actions.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The selected-thread Git status refresh now checks the selected environment’s connection state. It waits while the environment is disconnected and refreshes when the environment connects or reconnects. Tests cover connection changes, thread and cwd changes, and rerenders.

Changes

Selected-thread Git status refresh

Layer / File(s)	Summary
Connection-aware refresh and validation apps/mobile/src/state/use-selected-thread-git-actions.ts, apps/mobile/src/state/use-selected-thread-git-actions.test.tsx	The hook reads the selected environment runtime and skips the status refresh unless the environment is connected. Tests check refreshes on connection, selected-thread, and cwd changes, and verify that rerenders do not cause repeated refreshes.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 584c3

Git status refreshes when the selected environment connects. No actionable issue remains before merge.

🚥 Pre-merge checks | ✅ 4

✅ 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 and concisely describes the main change: refreshing Git status after reconnect in the mobile client.
Description check	✅ Passed	The description explains the stale-status problem, the reconnect-based refresh change, detailed verification results, test coverage, limitations, and agent attribution. It does not use separate Proble…

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

[juliusmarminge]

Reviewed the docstring-coverage warning. The hook already explains why connection transitions trigger a refresh; the tests describe the observable behavior they protect. Adding documentation that repeats the test helpers or effect wiring would conflict with the repository guidance, so no code change is needed for this advisory warning. CodeRabbit reports no actionable correctness findings.

Dismissing prior approval to re-evaluate 584c331