mirror of
https://github.com/zeronsh/comet.git
synced 2026-11-16 18:57:19 +00:00
zgx: a chat knows its Cloud machine, and can move it to a bigger one
A chat on Cloud only ever said "Can't reach {host}", even of a machine asleep
or one that could never wake, and a machine that filled its disk just died.
The composer's deck now says its machine's state as a notice (asleep with Wake,
waking and how far), and one alert at a time: can't wake (it needs N GB, opening
to every size), failed with the real reason, disk filling (dismissable until the
level worsens), files going soon, and files gone (a fresh machine on the same
repository and branch). Nothing opens itself: each waits in the pill. Settings ->
Cloud picks the size new chats start on.
The sizes are a grid under the alert, one set of column lines for every row: name,
vCPU, memory, disk, credit rate, then a trailing slot with the pick, why it's out
of reach, or Current. Short of room the columns go from every row at once, memory
first and disk last. An alert alone in the deck leaves its glyph to the tab's; with
others, or still working, it keeps its own.
The deck gains that much as data (an alert's body, note, choices and grid); what's
said and offered is pure functions (screens/chat/cloud_machine) over the sessions
account/cloud reads, and screens/chat/cloud_tray's bind draws nothing. Sessions are
read every 60 s (3 s while one settles), and a read that changed nothing sets
nothing, so nothing redraws at rest.
The wire types and engine client are zeron/cloud-durable's own text, so the two
merge in either order. Zeron v2's composers get the same wiring.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
3a6c7aa3fd
commit
08f0679617
27 changed files with 3162 additions and 30 deletions
Loading…
Add table
Add a link
Reference in a new issue