Question
Bootstrap the separate iOS repo and move Phase-2 (iOS v1, online-only) tracking there.
This ticket tracks the iOS side from genug-da only until the dedicated repo exists (charting choice recorded on the map — a ticket here participates in the blocking graph, unlike a prose placeholder). Decided constraints: native Swift (map decision 9), separate repo consuming the generated swift-openapi-generator client (map decision 10), v1 strictly online-only (map decision 4), PAT + QR scan-to-connect as the sole auth (map decision 8), optimistic UI on direct entities but never on derived envelope totals (map decision 5).
Resolve by: creating the iOS repository, wiring it to consume the generated OpenAPI client, seeding its own issue tracking for Phase-2 scope (screens, app architecture, Swift stack — deliberately unspecified here), and linking the new repo in the resolution comment. After that, iOS work never lives in this tracker.
Question
Bootstrap the separate iOS repo and move Phase-2 (iOS v1, online-only) tracking there.
This ticket tracks the iOS side from genug-da only until the dedicated repo exists (charting choice recorded on the map — a ticket here participates in the blocking graph, unlike a prose placeholder). Decided constraints: native Swift (map decision 9), separate repo consuming the generated
swift-openapi-generatorclient (map decision 10), v1 strictly online-only (map decision 4), PAT + QR scan-to-connect as the sole auth (map decision 8), optimistic UI on direct entities but never on derived envelope totals (map decision 5).Resolve by: creating the iOS repository, wiring it to consume the generated OpenAPI client, seeding its own issue tracking for Phase-2 scope (screens, app architecture, Swift stack — deliberately unspecified here), and linking the new repo in the resolution comment. After that, iOS work never lives in this tracker.