0.59.6

The page’s dev server no longer loads node:crypto

gui:dev failed to start the page because the page took ENDING through probe.ts, which pulls in node:crypto; the page now takes it from src/ending.ts (#105, on main as f6a9fbc).

Zen: a question that blocks an agent comes before a notice

In the 2026-11-06 box trial (trial14, 0.59.5) Zen showed the tower’s wait (MP-4219: Handle, Dismiss, Maybe later) when a question forwarded by a box arrived, kept it, and left the question behind it with nothing on the page to say so; the box’s agent stayed stopped. Boss decision 2026-11-06, 「Blocking first; untouched cards yield」 (Z-D18):

• Two ranks. Blocking items go first: a unit that waits or has a dialog, a project trust question, a question a box forwarded, and a teammate’s confirm (its tool call waits up to ten minutes). A tower’s wait, a pair request, and a memory proposal block no one and come after. Within a rank the order is today’s, oldest first. The table with the reason for each kind is docs/specs/2026-11-01-zen-view.md, Blocking first.
• A blocking question takes the screen from an untouched lower card, with the bowl, and the card that was there goes back in line: it is not put aside, so it returns after the answer and the 3 s pause. No count and no hint that it is waiting.
• A card the boss is touching is not interrupted; one the boss walked away from is. Boss ruling 2026-11-06, 「Touched expires after 20 s; draft kept」: a card is touched when its answer is on its way, or a tap, key, wheel, or input reached it in the last 20 s (the companion’s draft guard). An open reply box or a draft holds the screen only through that window; after it the question takes the screen (with the page’s reminder once, if the page is hidden), and the card that yielded goes back in line with its draft and its open box as they were, and shows them again when it returns. The console says the card on the screen is being answered while the question waits.
• The card that takes the screen is inert while the old one fades. The old card stays on the page for 1.3 s; a tap or a key aimed at it no longer lands on the question (a Dismiss on a wait was a Run it now, an Allow, or a Trust). The new card takes no tap, key, Esc, or focus for that long (0.5 s under reduced motion), then takes the focus as any card does (ZBF-F001). A Space pressed while it was inert and released after no longer picks the choice the focus lands on (Firefox clicks on a Space’s release), and a card that leaves inside the window stays out of Tab’s reach while it fades.
• Smaller fixes (ZBF-F003 to F006). Leaving Zen and coming back no longer reads the old card’s touch (a flash of the wait, then a swap); blocks ranks every kind of card and a kind nobody ranked blocks (a new kind fails the type check); a wheel on a card counts as a touch; the 500 ms look ends with the touch, when no blocking question waits, and when Zen is left.
• Unchanged: Standard’s and Geek’s dialog order; a question that arrives during the pause or an outcome waits for it; reduced motion; a hidden page reminds once for the question that took the screen.
• Demo. ?zen=blocking shows a tower’s wait with a box’s question arriving six seconds later (&box=<ms> sets the delay).

Design: docs/specs/2026-11-01-zen-view.md, Blocking first. Code: gui/zenmodel.ts (blocks, the preempt in settle), gui/zentouch.ts (the touched card), gui/zen.ts (the hook, the inert card, the parked card).

Merge train: an urgent fix-forward car may carry the author’s read

On main as 47b91ba: a car that fixes an integration branch’s latest red pipeline (an urgent fix-forward car) may carry the author’s read in its slip instead of a review report; the integrator checks the red pipeline, departs it alone once Load allows, and the train’s reviewer gives it its first full-depth review and returns it if it holds more than the fix. See docs/specs/2026-10-30-merge-train.md (car slip) and prompts/integrator.md.