feat(mobile): inspect and update providers by environment

[rynfar]

Mobile users can see their saved environments, but they cannot inspect provider update status or request a supported provider update for a specific environment. This adds a Pylon-branded detail route from Settings → Environments. The route uses the selected environment ID for config, session, refresh and update commands; disconnected, unverified and non-operate sessions cannot run maintenance. Provider update actions appear only when the server advertises an installed, enabled, actionable update command. Returned update state distinguishes succeeded, failed, unchanged and pending results, so an RPC response alone never claims an install succeeded.

This is a partial adaptation of upstream 68fb7f4b850991ba0ca5bd0d7c4aa13d4e5d6bb7 (#13302). The upstream T3 release-index lookup and mobile server-update target picker are excluded: Pylon has no equivalent owned release lookup, and guessing a target could install the wrong product/channel. The detail screen shows the Pylon server version and directs server updates to web/desktop. The upstream EAS environment-variable workflow hunk is also excluded; Pylon preview already verifies Connect config, and this PR performs no EAS build, release or live update. The new manage list is hidden in showcase mode to protect saved environment labels.

Validation: 3 focused access/eligibility/result-state tests, mobile typecheck, scoped lint/format, frozen install and diff check passed. Independent review passed on final HEAD. No simulator/device interaction or real provider update was run; those remain acceptance limits. The source remains pending and partially adapted until this PR is merged and the release-policy dependency is resolved.

Tracks #736. No upstream review cursor change.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

Deployment failed for project pylon-marketing with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/pylon-code?upgradeToPro=build-rate-limit

[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	14.0 KiB	14.0 KiB	−17 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.2 KiB	7.2 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.8 KiB	6.8 KiB	−16 B (−0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.0 KiB	58.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	14.0 KiB	14.0 KiB	−17 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.2 KiB	7.2 KiB	−15 B (−0.2%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−2 B (−0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	58.9 KiB	58.9 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	10	9	−1 (−10.0%)	21	✅

Baseline: 7ed3f71 · PR result: a84564a · 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: 115.6 KiB
• Claude decoded thread snapshot: 116.3 KiB

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