0.58.3

Zen shows what Standard keeps in the Link notices

• A teammate’s confirm, a dialog a Straw Link box forwarded, a pair request, and a tower’s memory proposal are Zen cards. Until now Zen showed none of them: a teammate’s tower could wait on Allow while you sat in Zen. Each is one card in the same ink as the rest, with the same rules: one focus, no count of what else waits, and after your answer the next card or the breathing circle. Allow / Deny come with the tool’s full arguments; a forwarded dialog is the shared question panel (Send, Cancel, the same rules as Standard); a pair request asks for the four-digit number the phone shows, then Allow or Deny; a proposal is Confirm / Reject under the message it cites. Maybe later is Zen’s own rest; Esc is it.
• No view-specific send paths. Standard’s rows (the Link button, the forwarded dialog’s card, the Wi-Fi tab, the tower’s notices) and Zen’s cards call the same functions in gui/asks.ts, read the reply through the one outcome table, and send what they always sent. Standard and Geek look and behave as before.
• The server decides when a card is over. A request the server stops listing (you answered it at the computer, another controller did, it timed out) leaves Zen as Already answered elsewhere; after your own answer the card rests for 30 seconds so a snapshot that still lists it does not bring it back at once.
• A paired phone has Standard’s authority and no more. It can answer a confirm and a forwarded dialog and confirm or reject a proposal; the pair request is this computer’s to decide (the server answers a paired device local_only), so a phone in Zen is given no pair-request card. Every server-side check stays: the holder’s check that a confirm is still open, the dialog id and digest, the LAN number and its budget of three wrong numbers, the memory rev. The card does not put the focus on Allow or Confirm, so Enter cannot allow what you have not read.
• Not in Zen, on purpose: a join request (comparing the words both screens show is a trust decision made on Standard’s own page), a forwarded dialog no panel can draw, and the head tower’s questions.
• Demo: ?zen=link-confirm|link-dialog|pair|proposal, with &refuse for the server’s refusal (the pair number is 4821). Docs: the Zen spec’s Link cards (Z-D17), docs/how-it-works.md, and both READMEs with a new picture.
• Review fixes: link/confirm-answer now requires the request’s digest (a body without it is refused with “Look at the request again”; the holder’s own answerConfirm keeps the digest optional for its internal callers). The comments and docs say the check catches a changed digest, not changed arguments under the same digest, and the Zen spec, gui/zen.css and docs/how-it-works.md no longer describe the tinted box or the old confirm body.