Workers, ports across them, frames that measure themselves, scripts that run once
The window's frame is the shell's own on Wayland
Pointing in the painter's order, the viewport's reach, the document base URL, pushState reaching the shell, the traversal interfaces; the scripted score
A window that changes size: one tab laid out once a frame; what a turn of the loop cost
When a page runs out of memory: the script heap's ceiling, the window's memory watch, and their two flags
Themes: Firefox's and Chrome's, converted from an .xpi, a .crx or a folder dropped into the profile; three more tokens; --import-theme and the import-theme verb
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 cache: freshness, heuristics, revalidation and the profile's cache folder
The command palette and the theme presets: what the palette lists, how a theme is chosen and kept
Profiles and containers: the profile's files, what a container keeps apart, and what is left
Session restore: what comes back, where the file lives, and the --profile option
The Linux window: the display's scale, touch, the input method, the shell's own frame
Content blocking: the lists, the folder, the option, what is not applied
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ebXZs43Ks9pd5MerR62rG
The Linux window: Running Sashfold, Building, Architecture, Networking, Not written yet
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EkzH8EAowXWrPXkiKyR9f6
Measurements: 7650 of 13477; --add-font in the runner's flags
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