refactor(mobile): Phase 80 thin hubClient over shared SSOT

[DeliciousBuding]

Summary

Strangler thin of Mobile hubClient (~737 → ~342 LOC) without big-bang rewrite.

T80.1 Inventory (keep vs re-export)

Surface	Decision
REST methods + DTOs	Proxy / export * → @agenthub/shared/hubClient
async SecureStore token cache + 401 refresh	KEEP
getMobileSnapshot + fixture mapping	KEEP
createMockHubClient	KEEP
HubApiError / HubNetworkError	KEEP (test compat)
WS helpers + legacy event type names	KEEP

T80.2 Implementation

• wrapSharedAsMobileClient Proxy: all shared methods auto-withAuth except unauthenticated entry points + downloadAttachmentUrl
• Removed duplicate local DTO interfaces and hand-written method list / shared.request forks (paths already live in shared extended API)
• Header rule: do not add new REST on Mobile — add to shared first

T80.3 Boundary docs

• AGENTS.md: hubClient SSOT + Mobile Hub-only
• app/mobile-rn/README.md: Hub-only data plane + thin shell note

Issues

Closes #1337
Closes #1338
Closes #1339

Verify

• pnpm --filter agenthub-mobile-rn typecheck → exit 0 (main app tree)
• vitest run src/api/hubClient.test.ts src/api/hubContract.test.ts → 14/14 passed

Out of scope

• Mobile UI redesign
• Local Edge from Mobile

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

@DeliciousBuding, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 798c30ae-674a-4f80-b281-34c2e244b04a

📥 Commits

Reviewing files that changed from the base of the PR and between 4c222e0 and 11295cd.

📒 Files selected for processing (3)

• AGENTS.md
• app/mobile-rn/README.md
• app/mobile-rn/src/api/hubClient.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/p80-mobile-hubclient-thin

---

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.}