Objective (M1 / P1)
One hardware day that resolves the open iOS connectivity cluster with device evidence and produces the iOS half of M1's mobile picture. Deliverable: a report in docs/research/ with verdicts that close or convert the member issues.
Member issues (all assigned to M1)
Additional questions beyond the member issues
- Silent-push budget reality: measured delivery rate of budgeted silent pushes across a day of normal use (foreground/background/killed) — bounds how much wake-dependence can be engineered away vs must be tolerated.
- Suspension vs live P2P: how long does a direct QUIC session survive backgrounding before iOS kills the socket, and does the resume path re-establish direct or degrade to relay circuits?
- NSE wake paths: does an alert-push NSE invocation give enough runtime for a mailbox drain over the relay vs a direct catch-up, and which is actually attempted?
Method
Two iPhones + the existing device protocol docs (docs/ios-device-protocol-2026-07.md Sections C-E as the base), relay with fresh push budget, diagnostics snapshots per scenario.
Output
docs/research/ios-cellular-p2p-2026-08.md; #73/#74/#77 closed or converted to implementation issues; iOS rows in the M1 KPI table.
Objective (M1 / P1)
One hardware day that resolves the open iOS connectivity cluster with device evidence and produces the iOS half of M1's mobile picture. Deliverable: a report in
docs/research/with verdicts that close or convert the member issues.Member issues (all assigned to M1)
Additional questions beyond the member issues
Method
Two iPhones + the existing device protocol docs (
docs/ios-device-protocol-2026-07.mdSections C-E as the base), relay with fresh push budget, diagnostics snapshots per scenario.Output
docs/research/ios-cellular-p2p-2026-08.md; #73/#74/#77 closed or converted to implementation issues; iOS rows in the M1 KPI table.