Every declared AgentDeviceRunnerUITests method now belongs to a lane, and
the #if guard is the classification: AGENT_DEVICE_RUNNER_UNIT_TESTS alone
means a pure runner decision (runs on the macOS host on every PR — ci.yml's
existing compile job now executes the bundle it builds), '&& os(iOS)' means
runner/XCTest semantics (simulator lanes only). check:xctest-selection
evaluates the guards per platform, derives each lane's reach, and fails on
a flagged identifier that is undeclared or uncompiled on that lane, on a
declared test no lane reaches (found the two tvOS-only tests, dark since
birth — widened to os(tvOS) || os(macOS)), and on testCommand reaching any
lane. The host and nightly lanes assert executed == derived reach, so a
missing -D flag or a guard that compiles a file out reads red, not as a
smaller green. One duplicate test deleted (sparse-verdict assertions folded
into its twin).
* ci(ios): run the full XCTest suite nightly and check the PR test list (#1781 A7)
* fix(ci): skip the runner server entry point in the nightly and validate both test flags
* docs(ci): restate the nightly lane cost and timeout honestly
* docs(ci): stop quoting XCTest counts that drift between commits
* ci(ios): tighten the nightly timeout to the measured suite duration
Michał Pierzchała