Refined Client Portals
The monogram fallback did its job and is now out of a job — the real icons arrived, recovered from a sibling repo and checked byte for byte.
Michael StatonLossless Toolkit
lossless-group/lossless-toolkit-sitedevelopment
- colour = whenJan 2025 → Sept 2026
36 commits · +87,233 lines
Michael StatonA Client Surface, a Header That Folds, and Two Hundred-Odd Tools Rescued From a Typo
A page for client toolkit recommendations, a quick-access rail so a client sees their own logo first, a header that collapses properly on a phone, and a repositories page built from four spellings of the same frontmatter key — one of them misspelt, and the only way seven tools were reachable at all. Also: a logo that returned HTTP 200 for a week without ever being an image.
Michael StatonThe Hero Grows a Right-Hand Column, and the Dev Server Lies Twice About Where It Lives
The landing page now leads with the copy on the left and the five curated filters on the right, one row, no max-widths. Getting there took four small CSS changes and one genuinely instructive detour: a local server can be running, healthy, returning 200 — and still be serving the wrong build at an address your browser cannot reach. Both halves of that lie are worth writing down, because both were reported as success first.
Michael StatonThe Whole Catalogue, and Everything That Only Breaks at Full Size
The spike ran on 173 of 1,764 tools, and a tenth of a corpus is not a small version of it — it is a different one. Importing the rest turned five silent defects loud: wikilinks pointing at pages that were never built, two featured tags rendering 2 and 8 tools instead of 258 and 128, and every tag page opening on the unfiltered catalogue because a dead variable was holding the answer.
Michael StatonOpening the Lossless Toolkit Rebuild — Four Explorations and the Constraints We Found by Reading
The second stage of the lossless-site rebuild gets its own repo, and its architecture conversation gets written down before any code exists. Four explorations capture what is decided (Pagefind, Timeline, OpenPanel, Vitest and Playwright, no published token package) and — more valuably — five constraints discovered by reading the existing corpus rather than assuming: for_clients is curation and not a gate across 481 files, URL fragments never reach the server so anchor links cannot carry their own unfurl, Pagefind indexes at build time so 'live' and 'searchable' are different promises, no Lossless site implements theme modes at all despite three packages built for it, and the house already coined a name for the materialize-versus-JIT rule we kept rediscovering.
Michael StatonOne Atom, Two Islands — Search That Spills Out of the Bar
Pagefind lands in the toolkit spike, and with it the fix for a subtler problem: two Svelte islands that looked like one feature and behaved like two. A shared reactive atom makes the header bar and the catalogue explorer genuinely the same state, tags become clickable objects that fold the query into themselves, and a Playwright drive finally catches the class of bug that a passing build never will — starting with a one-argument mistake that silently killed hydration.
Michael StatonOne Owner for the URL — and Chips That Actually Do Something
Train-Case is the storage form and Train Case is the display form, and for a few hours the toolkit confused the two badly enough to route people at /tags/Video%20Generators/. Fixing it meant giving the URL a single owner, teaching Pagefind to index the stored value rather than the rendered label, and lifting a decorative span out of a link so it could finally be clicked.
Michael StatonTwo Agents, One Answer — What the Spikes Agreed On
Two independent implementations of the Lossless Toolkit, built from the same guidance along opposite architectural axes, converged on five decisions nobody asked either of them to make — including the same filename for the content boundary. That agreement is worth more than the winner, and it is what the spec should be built from. The session closes with a handoff, an honest note that none of this code has been read by a human, and a request for a refactoring harness.
Michael Staton