On the PicoCalc the main menu's middle chip, Quit?, opens the quit
confirm, and the confirm's own lane was empty, so leaving took a move
to the Quit button and Enter. The confirm now carries Quit! on that same
F3, sending the same quit, which with the question up is the leaving, as
a second ^Q is. A button dialog can take a lane for that one case; every
other prompt keeps its empty one.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A ── Label ── heading drawn in the border's own colour read as part of
the frame it sits in. Grouped lists' headings and the chat's day
dividers now wear their own theme style, heading: a bold dark grey on
the desktop, slot 8 on the PicoCalc. The frame keeps the accent.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The message paths' fan already gave its legend's row to the list below
a 16-row viewport. The node detail page's routes, the packet viewer and
a record's Route tab now do the same, so on the Cardputer's 11 rows no
path graph spends one on the key. The PicoCalc and a desktop terminal
keep it. Tests that paint these screens record a viewport first, as the
frame does.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Beside its square the shorter word is unmistakable, and it brings the
whole key to 52 cells, so the legend under a path graph or the contacts
table is one line on the PicoCalc and the Cardputer instead of two. The
type's name stays room server everywhere else, the CLI's answers
included.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Arrowing down the device list on the PicoCalc stalled on every keystroke. The
time was not in the list: at 53 columns the full-size mark does not fit, so each
paint sent load_logo back to the disk for every size until one did, parsed and
measured each, and decoded every row again to centre it. None of that changes
between paints, and the splash paints on every keystroke and every idle tick.
compose_startup now asks _fitted_banner, a one-slot memo keyed by the banner and
the width, dropped on a platform switch with the other composition memos since
the fold bakes the theme in.
Measured on the desktop under the picocalc platform, splash at 53x26, ↓/↑
alternating: 31.1 ms a paint before, 2.3 ms after. The logo was nine-tenths of
the frame; the list itself is under 0.1 ms. 108 frames across 53x26, 53x40,
72x24, 100x30, 40x20 and 53x12, with and without a footnote, picocalc then
regular then picocalc again, come out byte-identical before and after. Not yet
timed on the device, which was unreachable; A/B it with profile-picocalc.
The splash's live rescan (f9e9271) was the first suspect and is not the cost:
a serial poll's device ids are stable, so it repaints only when a device comes
or goes, and the enumeration itself runs in a thread.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
meshterm.net/map and www.example.org are links now, as surely as their
https forms: a host starting www., or ending in a top-level domain IANA
has delegated, read from the registry itself, kept verbatim in
assets/tlds.txt. So file.txt stays text, txt being no TLD, and so do a
decimal, an abbreviation, an address, and a path. A scheme-less link
opens, and its QR code encodes, as https://. Link finding moves out of
the chat screen into core/links.py.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Its 14 rows can't spare a code under every message that carries a link,
so it keeps url_codes off and reaches a link's code the desktop's way,
on the share screen. Its braille code is small enough that a link and its
code share the panel. A test pins all three: no code under the message,
QR on the lane's Shift bank, and the share screen inside 53x14.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A URL too long for a message's hanging lane steps out to the timestamp's
column on a line of its own, whole, since a terminal opens a link, and a
reader copies one, only while it sits on one line. Only a URL wider than
the screen still folds. ^U on a picked message opens its links on the
share screen, one code at a time, and with several, the arrows step
through them, the URL line flanked by a lit or dim arrow each way. On the
PicoCalc the lane carries it as QR, behind Day down.
CLAUDE.md also states the shortcut rule: a bare letter only on a screen
that takes no typing, a Ctrl chord everywhere letters are text.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The bordered frame pads its body one column in from each side border,
which is air for a row of text and two columns of drawing given up on
the map. A screen can now be flush (Screen.flush), and the map is: its
body is cols - 2 wide on the desktop, base_body_size agrees through the
shared panel_inset, and the braille edge scrub drops to the one border
column. The borderless platforms already drew the full width.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The bordered frame pads its body one column in from each side border,
which is air for a row of text and two columns of drawing given up on
the map. A screen can now be flush (Screen.flush), and the map is: its
body is cols - 2 wide on the desktop, base_body_size agrees through the
shared panel_inset, and the braille edge scrub drops to the one border
column. The borderless platforms already drew the full width.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Two shots on 2026-10-01, the login console and MeshTerm's Public channel,
came out upright, unmirrored, and in the right colours (the header's
yellow count and the teal wordmark would trade places with red and blue
swapped), so the untested note goes.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 90ae2d56af)
Two shots on 2026-10-01, the login console and MeshTerm's Public channel,
came out upright, unmirrored, and in the right colours (the header's
yellow count and the teal wordmark would trade places with red and blue
swapped), so the untested note goes.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Piped rather than shown in a console, Python on Windows writes stderr in
the legacy code page, so the em dash in "can't reach the PicoCalc" came
out as a replacement character.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 3c050bc44c)
Piped rather than shown in a console, Python on Windows writes stderr in
the legacy code page, so the em dash in "can't reach the PicoCalc" came
out as a replacement character.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
It reads the device's framebuffer, so the picture is exactly what the
panel shows, whatever is on the console, and saves it as a PNG in the
Downloads folder (2x by default, so it stays crisp when shared). The
device half asks the framebuffer driver for its size and colour layout
instead of assuming them; the desktop half needs only Python's standard
library. Connection details come from .dev.env.
Written while the PicoCalc was offline and tested against a simulated
framebuffer; the skill says so until a real run confirms it.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit fea0875210)
It reads the device's framebuffer, so the picture is exactly what the
panel shows, whatever is on the console, and saves it as a PNG in the
Downloads folder (2x by default, so it stays crisp when shared). The
device half asks the framebuffer driver for its size and colour layout
instead of assuming them; the desktop half needs only Python's standard
library. Connection details come from .dev.env.
Written while the PicoCalc was offline and tested against a simulated
framebuffer; the skill says so until a real run confirms it.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Every URL in a channel or direct message, any scheme (a meshcore://
share as surely as a web link), now gets a braille code under the
message, hung at the body's indent. Several sit side by side and wrap
onto a new band when the line is full, so a link read on the handheld
opens on a phone instead of being typed out. Platform.url_codes keeps
it to the PicoCalc: half-block codes would swamp a desktop transcript,
and the Cardputer's 14 rows can't spare 9 under every link.
A picked message now keeps its whole block in view, codes included,
rather than only its first row, so walking the pick down onto a link
no longer leaves its code below the fold.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Every URL in a channel or direct message, any scheme (a meshcore://
share as surely as a web link), now gets a braille code under the
message, hung at the body's indent. Several sit side by side and wrap
onto a new band when the line is full, so a link read on the handheld
opens on a phone instead of being typed out. Platform.url_codes keeps
it to the PicoCalc: half-block codes would swamp a desktop transcript,
and the Cardputer's 14 rows can't spare 9 under every link.
A picked message now keeps its whole block in view, codes included,
rather than only its first row, so walking the pick down onto a link
no longer leaves its code below the fold.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The console host now draws every braille cell over Terminus's dotted
ones as solid 3x3 tiles, the same tiles as the PicoCalc's font build,
so the map and the charts draw unbroken lines and Platform.solid_braille
holds here too. Every QR code is then braille, one module a dot: the
share screen fits the 14-row frame instead of being cut, a channel
share with its link under it, a contact card with its link a page down.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Braille was a fallback for codes too big for half blocks; on the
PicoCalc it is now the grid every code is drawn on, eight modules to a
cell, share screens and page fences alike. A channel share is 23 cells
by 12 rows there, a contact card 29 by 15, each with its link under it.
The regular platform keeps half blocks, its fonts' braille being dotted.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Now that the PicoCalc's fonts draw braille as solid tiles, a braille
cell is a true 2x4 pixel grid, so it can hold a QR code at half the
module size. The fit ladder tries every half-block fit first (a lighter
error level and a narrower quiet zone cost a camera nothing on a
screen), then the same fits in braille. That puts the contact card on
the 53x26 panel whole: the standard code in 29 cells by 15 rows, with
its link under it, where half blocks had to send the link a page down.
Platform.solid_braille says where braille is solid; desktop fonts draw
it dotted, so the regular platform never offers it. Codes are cached
per (data, error level) since the share screen refits every paint.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
MeshTerm only ever draws braille as pixels (charts, the map, meters), so
each dot is now a solid tile of its share of the cell: 3x3 at 6x12, 3x2
at 6x8. A run of lit dots reads as one continuous mark instead of a
dotted one. Both fonts take it from the shared generator.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Key caption, nine cells a chip, two between, at the same columns (JP); only the
captions, F4-F8 in both banks, and the colours are the Cardputer's own.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Unset, the viewport reads as one row, which is now a short frame that leaves the
graph's caption out, and the caption is what these two check.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Message paths and the mesh walk keep their list's rows on the Cardputer instead of
spending three on a key to marks that mean the same thing everywhere; the rule is
widgets.short_frame, the same one that draws a tab strip on one row. The message
paths budget also counts the key's real height, which wraps to two lines at 53
columns and had been counted as one.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Below sixteen viewport rows the boxed strip's three rows become one, the active
tab standing on the rule between tees and every label held where it was. On the
Cardputer that puts the node page's actions and a record's whole Info list back
on screen. The node page's location preview steps aside when it can't have its
five-row floor, rather than scrolling the header and actions away.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The row of air a floating box keeps above and below is a platform setting now,
like its side gutters. At 24 rows it is what makes a box read as floating; at the
Cardputer's 14 it was a fifth of what a dialog could show, and the gutters already
say it floats, so its dialogs get ten rows between their borders instead of eight.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The stock image gives an app no text console, so MeshTerm draws its own: the TUI
runs in-process with prompt_toolkit's output feeding a small VT parser, the cells
are drawn in Terminus 6x12 with MeshTerm's marks over it, and keys go in through a
pipe in xterm's spelling. The front end is the only part that differs: framebuffer
and evdev on the device (written ahead of the hardware), a Tk window on the desktop.
Each handheld's glyph inventory is now named by Platform.font, which replaces
ascii_fold; the render-boundary fold derives its accents, emoji, and fallback from
that inventory and quantizes colour only where truecolor is off.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Same hard width gate as the PicoCalc, the lane checked through the platform's own
deck, and no emoji in a handheld's output. Rows stay ungated, since a body scrolls;
the screens that are cramped at 14 rows are a judged worklist instead.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Same hue as the fn key's print, darkened in OKLab at constant chroma: white
on #e34b0f holds 4.0:1 where the print's #ff6633 held 2.9:1.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A lane's keyboard-bound half is now a LaneDeck named by Platform.lane_deck: which
keycodes drive the slots, where the chips sit, how they are drawn, and which of a
screen's lane definitions it reads. Screens define picocalc_lane; cardputer_lane
follows it until a screen overrides it, so the two can part ways one screen at a
time. The Cardputer deck is Fn+4..8, Shift with them as F16-F20, eight-cell chips
centred over their keys in the fn key's orange-red and the Shift blue.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
With Esc inert at the main menu, the PicoCalc had nowhere to say how to
leave. Its title bar now ends on ^Q quit there (Esc clear while a filter is
typed), and the menu's F-key lane puts Quit? on F3, which asks first, with
Quit! behind it on F8 to leave without asking. Follows up issue #22.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Esc-mashing back to the menu used to land on the quit confirm, and ^Q, one
key from ^W, quit with no question at all. Now Esc at the main menu only
clears a typed filter, and ^Q floats the same quit confirm the Quit row
opens, from anywhere and without stopping what runs underneath; a second
^Q while it asks leaves at once. The main menu's hint names ^Q quit, the
only place the chord is shown. Option D from issue #22.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Over Bluetooth every command is a write-with-response, and a companion that
restarts on the reboot command can drop the link before acknowledging the
write. The write then hung until the link supervision timeout, holding the
reboot dialog back by a second or more. The reboot now returns once the
write has had a quarter second to fail, and leaves the rest to the teardown
that follows.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The reboot flow used to send the command and then wait for a liveness poll
to see the link drop. A quick reboot behind a port that never goes away
(a USB-UART bridge) was never seen, so the app went on sending commands to
a board mid-restart. Sending the reboot now declares the link down itself:
the session watcher wakes on the announcement, the Device rebooting dialog
takes over, and the first reconnect attempt waits a moment for the board to
actually begin restarting.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Those firmwares guard only the UART write characteristic, so the
refusal arrives on the handshake's first write, which meshcore's send
swallows. The empty handshake read as "not a MeshCore companion", and
the PIN pairing, the stale-bond repair and the macOS Passkey wait never
ran. The write is now wrapped to keep its refusal, and an empty
handshake behind one raises it, so both firmware shapes take the same
pairing path.
bleak no longer gets the PIN on Windows either: its WinRT pair() is
Just Works only, and after a mistyped PIN it left Windows holding an
unauthenticated bond that the next, correct attempt reused and was
refused over.
Verified against a T-Deck on MeshOS 1.3.0: a planted Just Works bond
heals in one run, and an unbonded connect without a PIN now says the
device needs one.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
s (F2 on the PicoCalc) steps all → unscoped → each region heard in the window
A–Z → unknown scope, beside w's window cycle. A narrowed page charts that
scope's floods per day (per hour at 24 h), their time-of-day rhythm, and its
own ledger; nodes per day and arrivals leave, being read off adverts, which
carry no scope. A window's stored floods are read once (Repository.flood_frames)
and resolved against the known region names for the page's life.
The node and own-node pages offer no cycle: a node's page is its adverts and
telemetry, and what we send is traces, which go direct.
The ring's order, words and chip move to ui/scopering.py, shared with the
dashboard.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
