feat(mobile): inspect and update providers by environment

[rynfar]

Mobile users can see saved environments but 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. It uses the selected environment ID for config, session, refresh, and update commands. Disconnected, unverified, and non-operate sessions cannot run maintenance. Update actions appear only when the server advertises an installed, enabled, actionable command. The UI uses readable built-in provider names and distinguishes succeeded, failed, unchanged, and pending outcomes; an RPC response alone never claims an install succeeded.

This partially adapts upstream 68fb7f4b850991ba0ca5bd0d7c4aa13d4e5d6bb7 (#13302). The upstream T3 release-index lookup and mobile server-update target picker are excluded because Pylon has no owned release lookup or target policy. The detail screen shows the Pylon server version and directs server updates to web/desktop. The upstream EAS environment-variable workflow hunk is excluded; this PR performs no build, release, or live update. The manage list is hidden in showcase mode to protect saved environment labels.

Validation: focused access/eligibility/result-state tests, mobile typecheck, scoped lint/format, and independent adversarial review passed after reconciliation with current pylon. In an isolated iPhone 16e simulator, I opened the new route, verified readable provider names and the Pylon server message, and refreshed provider status. I did not trigger a provider installation. Android device rendering was unavailable on this host.

Before	Environments with Manage updates	Provider detail

Tracks #736; no upstream review cursor change until merge disposition is recorded.

GPT-6 Sol via Codex in Pylon.

---

^{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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
pylon-marketing	Ignored	Preview	Sep 26, 2026 11:11pm UTC