2048-ios-development

2048 iOS development

Read AGENTS.md and the native sections of docs/architecture.md. Keep rules and persistence orchestration in GameViewModel.swift; keep adaptive presentation in SwiftUI views. Preserve deterministic injection used by tests and production randomness used by the app.

Use SF Symbols for controls, accessibility labels and identifiers for interactive elements, native confirmation and sheet patterns, safe-area-aware layout, Dynamic Type resilience, and reduced-motion behavior where animation exists. Do not replace system icons with text glyphs.

Never place the board inside a ScrollView. A scroll view's pan is a UIKit recogniser and outranks the board's SwiftUI DragGesture, so vertical swipes stop reaching the game entirely — and neither .highPriorityGesture nor .scrollBounceBehavior changes that. The layout is sized to fit, with ViewThatFits(in: .vertical) as the fallback; if you add vertical content, keep the static branch fitting and confirm app.scrollViews stays empty.

Add focused XCTest coverage for rules/state changes and XCUITest coverage for user-visible flows. Optional cloud code lives in Game-2048/Cloud/ — keep it additive, never put the board in a scroll view to make room for it, and add new Swift files to the Xcode project. CloudViews.swift is excluded from the coverage gate (same posture as Android's CloudUi); cover CloudAPI / CloudController / CloudStore with fake-transport unit tests instead. Run make test-ios; set IOS_SIMULATOR_ID when a specific simulator is required. make ios-run builds, installs, and launches on a resolved simulator without opening Xcode. Inspect launch, gameplay, help, restart, win, and game-over states for visible changes.