feat: integrate Orchestrator v2 and native Pi

[aaditagrawal]

Integrates upstream main through db898a3062 and Orchestrator v2 through 060756de5a and adds native Pi RPC support while preserving the fork's provider drivers, per-instance settings, usage monitoring, Hermes gateway, and desktop/mobile identities.

The v2 runtime imports legacy conversations into a separately backed-up statev2.sqlite database. Fork migration IDs remain intact, and incompatible upstream preview databases fail before mutation. Existing Pi ACP instances retain their instance IDs and configuration; native Pi receives a separate instance when needed. A persisted migration marker prevents newly created native Pi instances with default settings from being reclassified as ACP, and migrated IDs appear only once in the provider list. Native Pi requires CLI 0.80.5 or newer. Legacy providers use a tested v2 adapter with restart/history fallback, durable requests, tool output, and stale-event filtering.

Shared provider sign-in flows and credential bindings now protect session startup while credentials change. Provider compatibility advisories and bounded session-open retries follow the refreshed upstream implementation.

The web and mobile clients use the v2 command/event model. Custom provider permissions, rate-limit UI, title-generation errors, and guarded project deletion remain available. Hermes notifications append already-produced output without starting an unintended model run. Release workflows retain fork packaging and disable upstream-owned AUR/EAS publication; hosted web deployment requires explicit fork domains.

Validation includes workspace formatting/lint and typechecks, native mobile lint, focused migration/provider/adapter/client/packaging regressions, license and unused-code gates, and release smoke checks. Integrated verification used a real Codex run in a disposable project, checked replay after reload and live usage limits, and paired the Android development build to the same environment.

Builds on merged #292. Keep merge ancestry when merging so future upstream synchronizations recognize both upstream branches. Upgrade the server and clients together for the v2 wire protocol; preserve the old state database for rollback.

[aaditagrawal]

• feat: integrate Orchestrator v2 and native Pi #293 👈 (View in Graphite)
• chore: sync upstream main through September 22 #292
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

⚠️ The thread fixture changed, so impact percentages are not directly comparable to the main baseline.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Codex	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Codex	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Codex	Live turn WebSocket decoded	—	20.4 KiB	—	29.3 KiB	✅
Codex	Live turn messages	—	2	—	8	✅
Claude	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Claude	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Claude	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Claude	Live turn WebSocket decoded	—	20.8 KiB	—	29.3 KiB	✅
Claude	Live turn messages	—	2	—	8	✅

Baseline: 5031d44 · PR result: 88acf0b · 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: 106.1 KiB
• Claude decoded thread snapshot: 106.4 KiB

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