[futurepaul]

Test-only: shell-ui's sidebar_live check ("the rows shown before are the same elements (patched in place)…") now names each row it lost when it fails. That's every row shown before that was drawn again with the same words, with its HTML when marked and now. Before, the failure said only "kept 14 of 15".

Why

• It failed in CI between 02:43 and 03:31 UTC: the Fix #743's leak: a client that goes closes the runtime's connection whole #794 and stub: a rule is a word said, never text inside one #795 queue runs, search/service, Settings: Add agent (a name and a role), and each agent's role #763 and shell: delegation threads, a line each over the chat an agent asked from #779. That's the window when master carried devstack: a local node's port is a front door past wrangler's proxy #743's front-door leak, which dropped connections and WebSockets under load. shell: delegation threads, a line each over the chat an agent asked from #779's run logged "Network connection lost" inside the check's window.
• Since then it has passed 5 times in CI on this branch (the run plus 4 reruns of its shell-ui shard), and locally.
• So the cause was probably a list socket dropping mid-check and its reconnect redrawing an unchanged row, and Fix #743's leak: a client that goes closes the runtime's connection whole #794's fix may already have removed it.
• If it fails again, its detail names the row and what changed in it. The fix then goes to that row's cause in the product.

Not changed: the check's expectation, and any product code.

Complexity ledger: two more things kept per row in the check's page script (its HTML), and a lost list in its failure detail. No product change.

🤖 Generated with Claude Code

[alexlwn123]

Pass at 92a2d4e17306e4a40a8785b674cbc231826cd4e3.

This adds actionable diagnostics to sidebar_live without changing its assertion: missing rows are named, and unchanged rows whose elements were replaced include their before/after HTML. I traced the returned detail through Browser::eval and Suite::ok to the failure log. The small, test-only change is appropriate for the purpose; I found no blocking regression.

CI check and all four e2e shards passed. Local validation: git diff --check passed; e2e was not rerun locally. The referenced external engineering-style file was unavailable on this machine.