v0.2.4
2
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
5db0c6adb9 |
The tables that are a contract opt out of the formatter
Groundwork for the whole-repo `ruff format` sweep, kept separate so that sweep can be a commit with nothing in it but layout. An audit of `ruff format --diff` found the sweep is mechanical where it counts — 152 of 153 files come out AST-identical, the suite passes on the formatted tree, and `meshterm specimen` is byte-identical on both platforms — but it found three things worth handling first. One is a defect. `test_a_contact_the_device_never_held_is_still_removed_here` opens its docstring on a quote character, so the formatter breaks up the run of four quotes by inserting a space, and that trips `D210`. A straight sweep would therefore have taken `ruff check .` red — the one commit whose entire point is that both gates pass. The quoted phrase becomes curly quotes, which is already how the rest of the tests spell a quotation, and the collision goes away. One is readability. `sparkline` ends on a subscript of a call that no longer fits, and the formatter's answer is to hang `[` newline `0` newline `]` off the end. Naming the intermediate says the same thing in two plain lines. The rest are fences. Six tables in this codebase are hand-packed on purpose: the glyph map and the fold table read as two columns because that is how you check a substitution; `FONT_RANGES` is a device-verified inventory that a reader scans in rows; `_RAW_ROW_SKIP` groups its fields by which part of a packet they came from; `_NODE_SLOT_HEXES` runs the wheel in 60-degree steps with the angle in the lane. The formatter's layout is all-or-nothing — one line, or one item per line — so it would turn `FONT_RANGES` into two hundred lines and flatten every grouping into an undifferentiated list. `# fmt: off` says these are data laid out to be read, not code that happens to be wide. `test_theme16`'s heat ladder is fenced for a stronger reason: it pairs two steps per row under one comment naming the band, so exploding it would leave "under 5 minutes — white" attached to the second half of its own pair and the first half unlabelled. That is not alignment loss, it is a comment that starts lying. Not fenced: the `heat.*` ladder inside `MESH_THEME`. It wants the same treatment and cannot have it — ruff honours `# fmt: off` for a statement, and those rows are elements inside a dict inside a call, where the marker is simply ignored. It loses its aligned comment column in the sweep, along with about ninety other lanes across the repo. Each comment stays on its own entry, so nothing there starts lying; if the column is wanted back it needs the whole `Theme(...)` call fenced, which is a bigger decision than this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|
|
84caae53f8 |
P3 rework: the PicoCalc visual language, done properly
The first P3 (a84abf3) ran on the wrong model and its palette never reached the TUI: MESH_THEME_16 was written in 256-colour cube indices instead of the 16 VT slots, and the platform theme pick was wired into the scripted-CLI console while the real rasterizer stayed hardcoded to truecolor. Replace it end to end: - theme._VT_SLOTS: the canonical slot->RGB design (conventional hue families kept; slots 5/6 become the track/faint slates), MESH_THEME_16 rewritten against color(0..15) with the VT's bold-as-brightness and dim-bank-background rules pinned by tests. /etc/vtrgb + a boot oneshot install it (console-font script), OSC fallback when kbd is absent. - platforms.on_platform: set_platform now re-runs registered bindings, so theme, rasterizer and widgets swap implementations once per switch and hot paths read module globals - no per-call get_platform(). - The render-boundary fold (theme.fold_text): one str.translate pass (NFKD accent folds - the Terminus base has no accented Latin - plus symbol stand-ins and the width-padded emoji map), an embedded-SGR quantizer for canvas truecolor, and a ?-at-own-width catch-all that makes the no-wide-glyph short-circuit true by construction. Applied at the only two places every visible byte passes: render_to_ansi and MapCanvas.to_ansi_lines. - ui/fontset.py freezes the installed font's inventory (dumped live); the gallery now asserts rendered picocalc ANSI carries no truecolor/ 256-colour SGR and no character outside it - the parity gate the first attempt faked by asserting a dataclass field. - Font build: nine new 6x12 marks (ellipsis, warn, backspace, shift, gear, refresh, clock, crosshair, padlock) drawn into donor slots, with donor misses now fatal and a keeper canary (donating pi once erased Cyrillic pe - shared slot). Table re-dumped on-device: identical to fontset.py, 519 = 519. - Type-based name colouring: registry moved to core/nodetypes (services no longer import ui), fed from monitor observations, heard_nodes and merge_contacts. Heat gradient quantizes to heat.* steps on picocalc. - ui/marks.py: the P2-deferred constant relocation - widgets no longer drags map_render/mapcanvas/pathgraph for tuples and aliases. - meshterm specimen: the visual language on one card through the real funnels - the on-device acceptance screen (JP's request). - tools/chat: delivered/no-ack state uses the standard check/query marks, not the banned emoji pair. Verified on the Lyra: font+palette installed, specimen framebuffer captures in .claude/plans/. 1259 tests green, 13 xfailed (P6 list). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |