Running Sashfold, scripting the shell, the Sashfold 100: the instruments — a run timed whole, the window measured without a display, the counters a script can assert, and where the seconds go
The Sashfold 100 is rendered by the Linux build as well
The Sashfold 100 page and the Measurements table say the hundred are
rendered twice, on a Windows runner and on a Linux runner, published side
by side and linking each other; the corpus script's three new options are
listed; and the note that a page arrives blank without scripts is
replaced by what happens now, its scripts running for three seconds of
virtual time before the picture is taken.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ebXZs43Ks9pd5MerR62rG
Inline boxes take their room and draw their edges; the dashboard keeps Arizona time
Organize the wiki: a Home index by category, the pages that carry the details, and the C++ rationale under Design decisions
Home is an index in five categories — getting started, what works
today, measured, design decisions, testing and tools — with a sidebar
on every page. The details that lived in the README's paragraphs move
into pages of their own (Building, Running Sashfold, Themes, Parsing,
Styling, Layout, Painting and text, Networking, The shell, Not written
yet, Measurements, The Sashfold 100, The Pledge, Security defaults,
Testing, Scripting the shell), each with headings, lists and tables.
The C++ rationale becomes the Why C++ page under Design decisions,
its five points kept and its prose tightened.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Aat76GqxAyBf9VRJ4QaUbK