[mottihoresh]

Part of fix-track chunk 4 (#133). It covers the items X6 / R8, R6, N4, R9 / R10 and C5, as decided on 2026-10-16. The new-board state and event-log items (D1 / X3 / R2, S6, X8 / C6, D8 / S5 / C4) are in a separate PR. Nothing else changes.

1. X6 / R8: one fault order

	Today	After
Order	The Log listed a board's own flags as bus-off, error-passive, degraded, overheat. The Cockpit listed them as bus-off, fault, overheat, error-passive.	The Cockpit's order everywhere: bus-off, fault, overheat, error-passive.
Owner	Three hand-written sequences (views.ts, panels.ts, adopt.ts) and the log's walk over STATUS_FLAGS.	nodes/faults.ts NODE_FLAG_ORDER and its helpers (raisedNodeFlags, nodeFlagWords, nodeFlagChips, NODE_FLAGS). The log (node-events.ts), the tile and Attention (views.ts), the status boxes (panels.ts) and the Adopt evidence (adopt.ts) all read them.
Vocabulary	events/status-flags.ts STATUS_FLAGS was an ordered list.	It is now a record keyed by flag, with no order. gateway-health.ts looks labels up by key and keeps its own documented Gateway order.

The PDU flag text in faults.ts was written out twice: once for the Cockpit and once for the log, in the same order. The Cockpit now reuses the log's tables, so its output is unchanged.

2. R6: Add all can't double-run

	Today	After
Dialog	Add all had no busy flag, so a double click sent it twice. done was set from a stale closure.	One busy flag for the whole dialog, lifted into AdoptDialog. A ref refuses a second click before React re-renders. While Add all or Adopt runs, Add all, Later and Adopt / Add to cockpit are all disabled. done updates are functional.
Main	addAllInTurn could run again while one was running.	mapping-sequence.ts MappingSequences (NodeHub and the component mock) ignores a second Add all, or a second Un-hide all, while the same one is running. It answers { ok: true, done: [] }. The two sequences don't block each other.

3. N4: Un-hide all goes on and reports

	Today	After
Main	It stopped at the first board it couldn't un-hide and never tried the rest.	Every board is tried. The refused case of NodeBatchResult gains failed: every refusal, in order. nodeId and error are still the first. Add all still stops at its first refusal, with one entry.
Settings › Hidden boards	It showed the one error.	The existing error line (set-err) lists each failure: Couldn’t un-hide #8 Right_Radar: <reason>. A single Un-hide still shows main's error alone. No new UI element.

The API guard header (ipc.compat.test-d.ts) records the change to the type.

4. R9 / R10: the dialogs show the current board and count

	Today	After
Reset… review	It fetched the preview again on every nodes:model push (roster polls, PDU pages), with no stale guard.	It fetches again only when the inputs change. The key is settings-view.ts resetPreviewKey: the mapping as the snapshot shows it (each board's name, console, PDU and source, the hidden ones, and the differing count). An answer that a newer fetch superseded is dropped.
Adopt count	The header counted every listed row ("6 boards…"), while the button that opened it said "New on the bus · 3".	The header reads attention.newCount, the same field as the button.
Adopt board	A new request to open the dialog (a cog, or Connection's "›") while it was open kept it on the board it was showing.	Each request remounts the dialog (key) on the board asked for, as the latest push has it.

5. C5: an older snapshot never wins

• Main. NodeHub stamps a rising rev on every model it pushes (NodeModel.rev, optional). The nodes:get answer carries the rev of the last push.
• Renderer. nodes/store.ts drops a nodes:get answer or a nodes:model push that is older than the model it holds. It also drops a cockpit:snapshot whose rev is older than the one it holds.
• The mock stamps revs the same way NodeHub does.
• The other consumers. useNodesPulled uses its own pull only as a "data arrived" signal and writes nothing, so no change there. The mapping intents' model answers aren't read by the renderer. Everything the screens show comes from the snapshot, which is now rev-guarded.

Tests changed on purpose

Test	Was	Now	Why
events.test raises and clears bus-off, error-passive (with TEC), overheat	bus-off, error-passive, overheat	bus-off, overheat, error-passive	X6 / R8
mapping-sequence.test unhideInTurn … stops at the first refusal	stops at #30, #41 not tried	goes on, lists #30 and #52 in failed	N4
mapping-sequence.test Add all refusal	no failed	failed: [{ 7 }]	N4 (the shape of the result)
node-hub.test Add all / Un-hide all	no failed; read-only un-hide stopped at #1	failed added; #2 is tried after #1	N4
T10 lists every new board…	"6 boards this computer hasn’t added yet"	"3 boards…", the same as "New on the bus · 3"	R10

New tests

• nodes/faults.test.ts: a board with several flags. The log rows, the status boxes, the Adopt evidence and the tile chip all come out in the one order.
• nodes/mapping-sequence.test.ts: MappingSequences ignores re-entry, is free again after it finishes or after a refusal, and the two sequences are independent.
• nodes/mapping-sequences.seam.test.ts (via makeServices, which gained the add-all and unhide intents):
  • two Add all invokes in flight: the second is ignored and each board is adopted once;
  • Un-hide all with a refused id in the middle: the others are un-hidden and the refusal is listed.
• node-hub.test: every model pushed carries a rising rev, and nodes:get answers the last push's rev.
• T11: a double click on Add all runs it once, and the dialog is busy until it lands.
• T12: Un-hide all with one board failing un-hides the rest and lists the failure.
• T30: the review asks main again only when the mapping changes.
• T10: a request to open another board while the dialog is open lands on that board.
• ipc-adapter.test: a pull answered behind a newer push is dropped, and so is an older Cockpit snapshot.

How verified

• npm run lint, npm run lint:deps, npm run typecheck and npm test all pass (1409 tests).
• Each new renderer and store test was run against the code from before its fix, and failed there:
  • T11 failed with the old AdoptDialog;
  • T30 with the old ResetDialog / CockpitSection;
  • both R10 tests in T10 with the old Cockpit.tsx;
  • both C5 cases with the old store.ts.
• The fault-order test fails against the old STATUS_FLAGS walk.
• Not run on hardware. The fix: chunk 4 — new boards, event log and cockpit actions #133 hardware checklist items "fault order matches", "double-click Add all runs once" and "Un-hide all with one failing board" are still to do.