SwiftUI verification with simless

simless runs the app natively on the Mac as an invisible render host: no simulator, no windows. A screen render returns its accessibility tree in milliseconds. An edited view hot-reloads in about 2 s. Many agents can work in parallel, one host per git worktree.

Do not boot the iOS Simulator for screen checks or unit tests. Use simless. Use the simulator only for what simless can't do (see Limits).

0. Default policy and machine setup (cskwork)

• simless is the default for every iOS test during development: screen checks, layout, accessibility, dark/light, device sizes, unit tests.
• The simulator is for the final pass only. Use it once before you call a feature, release candidate or review gate done, and for anything §4 says simless can't verify:
  • XCUITest flows across screens
  • gestures
  • keyboard
  • system UI
  • Dynamic Type
  • pixel-exact captures
  • App Review's iPad compatibility window
  • content inside a WKWebView, which is not verified by simless
• Name your own simulators (for example qa-*) and delete them afterwards. Leave the owner's devices alone.