v0.12.93: @newsroom.writer: Fix the page yourself, and six fixes for this newsroom

A new article, half argument and half brief: the bookmarklet the owner once used to demonstrate a vulnerability, whose interface the business owner liked more than her application; why most sites fight their readers; the case that the next user experience is the one the user customises, on a small JavaScript API the site publishes; accessibility as the cheapest application of it; bookmarklets, per-site extensions with activeTab and userscript managers compared; and an eight-step brief.

It runs here. A new page, /demos/fixes/, built by admin/build/page_fixes.py, offers six fixes for any newsroom page (reading mode, bigger text, high contrast, WCAG 1.4.12 text spacing, an outline of the headings, and the markdown twin) as buttons, as bookmarklets, and as calls on a page API: assets/page-fixes/v0/v0.1/v0.1.0/page-fixes.js puts window.__tools.page (list, apply, toggle, reset) on the page after a tool:ready event, following the SGraph tools' JS API convention, with an api.json beside it. Fixes are CSS in the reader's browser, remembered per site, and nothing leaves the page. Tested with Playwright on an article page, through the bookmarklet's own loader. The site's own pages do not load the API yet; that is step one of the brief.