0.63.0

Blocks in documents and chat (todo #129, items 1 to 5; spec)

Agent-written blocks (form, options, suggest, table, checklist, review, cards, steps, stats, mindmap, diff, mermaid, GitHub alerts) are drawn with pi-better-show’s elements (0.1.2).

• Documents. A Markdown document card draws its blocks in the page itself, at the comfortable density, with no frame. An HTML document keeps its sandboxed frame. An invalid block shows its source as code. The alert callout of #128 is now pbs-callout.
• pi-better-show documents (contract v2). Documents shown by pi-better-show’s show_doc appear as cards beside those of pi-herdr-doc-review (still listened to until it is archived): a Markdown page with blocks, an HTML page in its sandboxed frame (forms answer, scripts do not run), and a text document. The server reads them from the owner’s own page server on this computer, never a path; a block’s answer reaches the owner as the package’s Answer.
• Chat. An agent’s message in the comms log draws its blocks on every surface (Standard, Geek, Zen, phone, a box’s unit). A submitted block is your message to that unit through the composer’s send route, held to the remote guards. A refusal shows its reason under the block and leaves it open. A chip or answer that is a ! or / line is never sent. A chip shows the text it sends, so you see what goes out under your name; a form or checklist whose outgoing text is not what is drawn (a picked choice’s value, a checklist item’s name, a question key that is prose rather than a plain identifier like store) shows the exact text first and sends it when you press Send.
• What goes out is what you saw. A suggest chip is drawn as the text it sends. A form or checklist whose sent text differs from what it shows (a choice’s value that is not its label, a checklist item’s name that is not its label, a question key that is neither a plain identifier nor its label) first shows the exact outgoing text, sent only when you press Send.
• Answered blocks are the server’s record, not the browser’s. What you answered is kept in answered.json beside the paired devices (mode 600, at most 2,000 answers, 90 days), so a block stays locked after a restart of the server, on your phone and your desktop alike, and under any address. A block is begun on the server before it is sent, so the same block is never sent twice, from any device; while an answer is on its way every drawing of the block is locked and says “Sending…”. If the record cannot be written nothing is sent and the page says so; if it cannot be read (a link, another account’s file, a broken or altered record) the blocks show a note instead of silently opening, the file is kept aside and never overwritten, and the note stays until the server restarts. A block shown as on its way opens again when the record drops it.
• Document answers go to the owner once per answer id (kept for 30 minutes whatever else is answered; a send that failed outright can be tried again) and only for Markdown documents of the pi-better-show package: the text is read from its owner first, so an answer for a text that has changed (or a block it does not have) is refused with a reason, and a Markdown document of pi-herdr-doc-review draws its blocks but takes no answers (the refusal says so; answer in the session). Over Wi-Fi access a Markdown document’s review images load with the paired device’s cookie. Image names in any script (圖.png) are accepted. Operate sessions still get no documents and no record.
• Look. Each view maps the elements’ --pbs-* tokens in its own sheet (Standard, Geek, Raven Keep, Zen; dark), and a block takes them from the view it is in; gui/pbs.css keeps only the wrapper’s layout, the note, and the 44 px touch rules, so one token has one source. Controls are 44 px on touch.
• Bundle. The elements are a lazy chunk (152 KB, 48 KB gzipped) loaded only when a message or document holds a block; no block code is in the eager bundle (122,703 bytes raw and 44,672 gzipped, the same as without the blocks). Mermaid shows its source (the diagram image needs a new server dependency).
• NOTICE.md now carries the notices of pi-better-show (MIT) and yaml (ISC), which the block chunk bundles.

Raven Keep’s status motion runs on the compositor

• The seal, the mist and the soul-fire move by transform and opacity over fixed masks and gradient layers, with no animated custom property: with 47 working units over 4 s, paints went from 3,464 to 137. The look is the one approved.