max / goingson

Compose gets a window of its own, and the description asks for it Finishes 3fb2526a. The screen has been built since f8eab8d and attachments since 9b37c84; what was left was the second mount, and the reason it was left is that nothing could ask for one. WHAT WAS MISSING WAS A WORD, NOT A WINDOW. Frame { verbs, status } landed in quasi 0.54 and says what a mount puts around a screen. Nothing said how anything asks for the second mount, so the only ways left were a bespoke branch in host.js or a menu item no screen can see -- both of which put the compose window outside the description, where no other renderer could ever have one. Max ruled (b) 2026-08-22: grow the vocabulary. That is Action::elsewhere, quasi 0.55.0, and this is its first consumer. A SECOND SCHEME, BECAUSE A PROTOCOL IS ONE RENDERER. quasi_tauri::Protocol is a scheme, a router, a state and one renderer, and a renderer is where the frame lives, so two frames is two schemes. compose://localhost/compose/{id} shares quasi::router() -- the same description, which is the entire point. Two things differ and both are the mount's: compose_shell has no nav and no running-timer band, and the frame reports. THE FRAME OFFERS NO VERBS, and that is deliberate rather than unfinished. Queue, Queue later, Discard and Take it back are on the screen, so both mounts get them from one place; a frame carrying them too would draw each verb twice in this window. Frame::verbs is for what a mount adds, and this mount adds a place to speak rather than something to press. WHICH CLOSES THE MEASURED TABLE. 3fb2526a found five divergences between the shipped modal and the shipped window. Four were gone before this commit: the attachments bar became a header row, progressive disclosure dissolved with Eudora's shape, and the verb placement and reply indicator were the accident rather than the answer. The fifth is where a mount says what happened, and Frame::holds is now what decides it -- a banner rests in the status line here and floats in the main window, from one description. open_compose_window comes back, aimed at an address rather than at compose.html, and its ComposeContext does not: a described route carries its reply context as a path and a query, so the three fields that struct existed to marshal are one string. The string is checked, because it arrives from the frontend and the frontend is where rendered email content is displayed -- joined onto the scheme so `..` resolves before the check rather than after, and refused unless it lands under /compose. Same reasoning as open_external_url one function down. A window is labelled per address, so two drafts are two windows and pressing the verb twice raises the one that is open. HOST.JS TAKES A SECOND JOB and its own rule survives, because the job is the same one in a different coat: a webview cannot put up a window any more than it can open a file dialog. What makes it not the thing that file forbids is that it answers a described word rather than inventing a behaviour. The test for a third job is written down beside it. Six tests. The two that would rot silently: that the verb carries the address and no transport (an href or an hx-get opens the screen in the window the control is already in), and that both mounts serve the same screen -- if this description ever learns which window it is in, it is back to the two code paths the measurement found. Takes quasi 0.55.0. Closes goingson 3fb2526a.