Mobile Orca collaboration visibility: Worker list and progress

## Goal
Make Desktop Orca collaboration observable from Cindy Mobile while preserving the mobile read-only boundary.

## Current gap
Desktop already exposes Lead → Worker projection and worker/session push updates through device-link. Mobile currently hides `orcaRole=worker` sessions, renders only Lead-side collaboration message cards, and has no Worker list or progress surface.

## Scope
- Add a Mobile-only Lead detail surface showing Worker label/role, task summary, status, and last update.
- Reuse existing `maker:worker:list` / `local-db:orca-workflows:list-workers-by-lead` and existing `maker:orca:worker-changed` / `local-db:sessions:patched` updates where possible.
- Keep Worker sessions out of the global Mobile home list, but make them reachable from their Lead.
- Add a read-only Worker detail view in a follow-up step; sending messages, focus switching, archiving, and ending the team remain Desktop-only initially.
- Do not change Mobile native configuration, dependencies, Expo config, or runtime-fingerprint inputs.

## Proposed delivery
1. Mobile transport/store: Lead-scoped Worker projection, cache, push updates, reconnect reconciliation, and old-Desktop graceful fallback.
2. Mobile UI: compact Worker status section on the Lead page, progress summary, loading/offline/empty states, Light/Dark tokens, and read-only navigation.
3. Validation: focused Mobile tests, Mobile typecheck, device-link compatibility tests if protocol surfaces change, and manual multi-Worker reconnect/status checks.

## Related issues and PRs
- #2707 — 协同模式中补充后台任务状态并支持单独配置 Worker (OPEN): asks for mobile running/progress/completion visibility.
- #1888 — Make ongoing Orca collaboration visible after main-agent handoff (OPEN): asks for persistent execution visibility.
- #4059 — 协同子面板重启后首次加载失败 (OPEN): Desktop panel recovery context.
- #3338 — Mobile detail message cache/sync timing (DRAFT): related Mobile synchronization work; does not implement Worker projection.

## Constraints
- Follow `docs/dev-rules/mobile-development.md`, `remote-and-mobile-adaptation.md`, `orca-team-architecture.md`, `protocol-compatibility.md`, and Mobile design rules.
- Any new wire channel/push must be additive, default-deny allowlisted, topic-routed, and backward compatible.
- Close related issues only after their acceptance criteria are actually delivered; do not close them merely because this umbrella issue exists.

Start with docs/dev-rules/mobile-development.md, remote-and-mobile-adaptation.md, orca-team-architecture.md, and protocol-compatibility.md. Trace the existing maker:worker:list, local-db:orca-workflows:list-workers-by-lead, maker:orca:worker-changed, and local-db:sessions:patched surfaces, then run the focused Mobile tests and typecheck. Done includes Lead-scoped read-only Worker visibility, reconnect and fallback handling, compatible loading/offline/empty states, and the specified validation checks.

Written by the indexing model from the issue text.