queen kanban: actor lanes, chips and task cards from actor_view.t27 over the actors feed #1589

The owner asked for the actors (BEAM-style pids, mailboxes, supervisors) and their messages on https://t27.ai/?lang=ru#/queen?tab=kanban, shown as tasks. The rules are in gHashTag/t27 master:

• specs/queen/actor_view.t27 (queen: actor_view.t27 -- actor lanes, chips, task cards and timelines for the board (Closes #8615) t27#8629, aligned in #8669). The reference passes 10 of 10 tests with 848 runtime asserts; t27b passes.
• The feed specs are spec(queen): actor_events.t27 - actor transitions on the event bus, and what anyone may read of them (Closes #8640) t27#8642 and #8652. The runtime is feat(queen): actor transitions on the event bus and a public delta feed - actor_events.t27, behind TRIOS_QUEEN_ACTOR_EVENTS=on (Closes #1744) trios#1750, in actors-next-2 behind TRIOS_QUEEN_ACTOR_EVENTS.

What the board needs:

• Paging. Read /queen/public-actors with since and cursor and handle resync. Pids are decimal strings; parse them as BigInt.
• Lanes. One lane per supervisor subtree, laid out depth first, parent before children, siblings by slot (layout_row, lane_of_pid). Messages to a dead incarnation still find their lane.
• Chips.
  • pid shown as slot.gen;
  • state: running, restarting or dead (chip_state);
  • mailbox depth against its cap, with the next deliver() verdict;
  • restarts used against max_restarts within period_seconds.
• Cards. A task-carrying deliver makes a card.
  • Its column is the task's A2A state from the tasks route (card_column); tasks.t27 has no rejected state, so there is no rejected column.
  • Its lane is the lane of the actor that last received the task.
• Timeline. Entries are ordered by the actors stream's seq, FIFO per (from, to) pair. An exit or DOWN joins the task it names.
• Filter. card_matches / actor_matches: tasks.t27's task_matches plus actor kind and supervisor.
• How the board runs the rules. gen-js lowers constants but not function bodies, so the board runs actor_view's functions through wasm, not hand-written TypeScript (only-t27 rule).
• Size. The view's tables are fixed at 8 actors, 32 events and 8 task rows. The 1000-actor runtime ring needs per-lane paging, or larger sizes in the spec, before it can be drawn whole.

Depends on #1588 (card height clamp and the fixture board in queen-viewport-contract). Chips add height, so the clamp lands first.

Demo data: ?replay=mvp. It serves a 24-row stand-in until the network MVP (gHashTag/t27#8648) exports its seeded trace.