feat(mobile): fade working threads and match web's status labels

[juliusmarminge]

On mobile, a working thread looked as loud as one waiting on approval, input or an unread completion, so it was hard to tell at a glance which threads needed you. The status labels were also thin, plain text, much easier to miss than web's.

This brings web's sidebar treatment to the mobile thread list:

• Working threads recede. Working and waiting rows fade to 55% opacity and their title drops to regular weight. The selected row never fades. The rule lives in shouldRecedeThreadRow, which mirrors web's shouldRecedeSidebarThread and has a small test.
• Status labels match web. Each label gets its web icon and bold text: dashed circle for Working, check circle for Done, shield for Approval, question bubble for Input, alert circle for Failed and Limited. Android uses the same Tabler icons as web. iOS uses the nearest SF Symbols; for Approval that's exclamationmark.shield, since iOS has no shield with a question mark.
• Rows that need you keep a medium-weight title. I used font-t3-medium because font-t3-semibold isn't defined in the mobile CSS and silently renders at regular weight.

Before / after (Android, same data)

Before	After

A running thread fades while the rows that need attention stay at full strength:

Verification

• vp test run apps/mobile/src/features/threads/thread-row-emphasis.test.ts
• Mobile tsc --noEmit and lint on the changed files
• Checked on the Android emulator. Not checked on an iOS simulator; the SF Symbol names typecheck against the symbol map.

🤖 Generated with Claude Code (Claude Opus 5.5)

---

[macroscopeapp]

Approvability

Verdict: Approved at b04d3e2

Macroscope's review found this PR approvable — This is a self-contained mobile thread-list presentation change: status icons/labels are improved and non-selected background work is visually subdued. It introduces no schema, persistence, navigation, security, or deployment impact, and the new emphasis rule has focused test coverage.

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

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.9 KiB	0 B (0.0%)	29.3 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	+24 B (+0.5%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	+24 B (+2.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.2 KiB	+41 B (+0.2%)	29.3 KiB	✅
Claude	Live turn messages	1	2	+1 (+100.0%)	8	✅

Baseline: 393ff4c · PR result: b04d3e2 · 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.