Dashboard 441 failures -> 0 across 65 files, worked by three agents. As in the
engine, core and CLI sweeps, the failures were mostly pointing at real
regressions and at behavior changes whose tests were never updated.
Two behavior changes account for the bulk of it. FN-054 made Chat list-first
(the transcript and composer render only inside an explicitly opened
conversation) and FN-9193 docked the conversation list beside the thread, which
deliberately removes the in-thread Back button. Between them they updated about
a dozen of their own tests and left roughly twenty suites asserting the old
navigation - the standing rule this session added, at scale.
The single largest file was not a navigation problem at all: useChat.test.ts's
80 failures were ONE unawaited async act. `stopStreaming()` returns a durable
cancellation promise, and two cases used a concise arrow, so React opened an
async act scope nobody awaited; the queue stayed installed and all 78 later
tests in the file saw a frozen hook. A sibling case already had the corrected
form.
Product defects found and fixed:
- register-chat-routes: FN-047 dropped the null-project branch from the send
path, so with no project selected a send began generation on a different
ChatManager than /cancel and /stream resolve - cancel was a silent no-op.
- ChatView: an imported GitHub link was seeded into a composer that was never
opened, so the operator landed on the conversation list with their link
nowhere on screen; and the thread anchor effect bailed on a missing container
WITHOUT recording state, so a conversation never anchored on open and the next
message growth force-anchored, yanking a reader who had scrolled up.
- NewTaskModal: an unguarded `.length` on an absent `repos` payload threw during
render and blanked the whole modal.
- styles.css: FN-9202's shared `.banner--chrome` referenced `--z-sticky`, which
nothing defined, silently resolving sticky banners' z-index to `auto`.
- The OrcaRouter startup-sync toggle shipped with no i18n catalog entry.
The register-model-routes family - 55 failures across 8 files - was one cause:
fake routers exposing only `get` after a `router.post("/models/refresh")`
registration was added, so every file died at setup.
Also deletes Column.drop-prompt-flags-arrival.test.ts, whose drop surface FN-051
removed, retargeting its late-arriving-flags invariant onto the surviving
context-menu move rather than dropping the coverage.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
c82e420ba0