# System book browser verification ## Scope Verified the generated System book application through the existing extension browser task in Chromium and Firefox on CachyOS. Book, document views, and board share one authenticated localhost application; raw authored HTML and unsandboxed previews remain trusted active same-origin content. This is browser-contract verification, not universal platform, accessibility, or security certification. ## Verified features - Public book/view/board commands share a server; ID, slug, path, core-document, cross-document, heading, backlink, and browser-history navigation work. - Desktop sidebar and mobile disclosure navigation support keyboard activation; search supports selection, Enter, clearing, repeated highlighting, empty/no-match input, and retained results after refresh. - Graph controls cover zoom, reset, wheel, drag, bounds, and Chromium CDP touch gestures. - Book and board render across light/dark desktop/mobile layouts, including completed Mermaid diagrams, MathML, code, tables, and authored HTML. - Local previews cover real iframe content, encoded HTML filenames, decoded SVG images, valid VP8 WebM playback, and full-size navigation. - Board and metadata controls cover state transitions, spec/plan constraints, plan status, proposal application/rejection, drop/restore, disabled terminal execution, persistence, and action failure feedback. - Live updates cover multiple tabs, changed documents/states/proposals, preserved search/scroll/location/disclosures, malformed config/board recovery, and last-good previews. - Authentication checks cover handshake, cookies, server isolation, cross-origin Origin rejection, reuse, shutdown, and reopening. - Browser diagnostics distinguish active Mermaid failures after canceled or hash-only navigation from a held import canceled by confirmed document departure. - Generated footnotes and ID references remain document-local; active raw HTML counters, custom fragments, and SVG references retain authored IDs. - Core documents beginning with raw HTML still receive generated heading anchors. - Footnote links and backlinks navigate to destinations clearing the fixed desktop header, not merely intersecting the viewport. ## Reproduced issues fixed - Search results clipped by the fixed header; Enter selection, clearing, repeated highlights, and accessible naming needed correction. - Encoded local filenames were not recognized as previews. - Refresh lost navigation disclosure state; proposal application triggered avoidable reloads. - Initialization could leave mutation controls disabled after an equal state snapshot. - Heading and footnote destinations could be covered by the fixed header. - Footnote IDs, backlinks, and array-valued accessibility references needed consistent generated-ID scoping. - Broad ID rewriting broke authored script/SVG ownership; document roots beginning with HTML could incorrectly classify subsequent generated content as authored HTML. - Mermaid teardown handling used an unsafe timer window; active failures now remain visible and wrapper errors expose their underlying cause. - Browser health collection previously ignored every aborted request and used aggregate failure allowances; accepted failures are now counted explicitly, with active-abort negative controls. - Parent typechecking exposed additional book TypeScript errors; those were fixed without editing concurrent extension work. ## Results A fresh build followed by the strengthened fragment test initially failed in both browsers at the fixed-header clearance check. After extending fragment offsets to ID targets, fresh build plus the same Chromium/Firefox test passed both cases. After final source formatting, another fresh build and complete book browser run passed all 30 cases across both browsers. The latest focused native run passed 132 tests across 19 files; 18 modernization tests also passed. Extension lint passed. Final root `//:check` and `//:lint` reruns passed, including typechecking, static validation, compatibility, and all 46 README checks. These results supersede the earlier fixture failures without establishing their causes; concurrent work was preserved. No broader CI or repository-wide browser suite was run. Selected fresh screenshots remain under `/tmp/the-system-browser-review/verified-final`; the reproduced pre-fix fragment failure remains under `/tmp/the-system-browser-review/parent-fragments`. Superseded owned browser artifacts were removed after inspection. ## Acceptance limits Clipboard operations, native editor dispatch, and Pi execution use isolated fixtures; they do not establish actual desktop clipboard, IDE, or governed-agent execution acceptance. Touch gestures use Chromium CDP, not a physical device; Firefox multitouch and WebKit were not exercised. Cross-origin rejection includes explicit Origin-negative HTTP checks, not a separate hosted attacker-browser application. Headless Playwright uses Ubuntu fallback browser builds on this unsupported Linux distribution. Screenshots were visually inspected across light/dark desktop/mobile states; no screen-reader audit or native Windows/macOS/Android acceptance was performed. Valid SVG and VP8 WebM examples do not establish every supported media codec. Dependency findings remain open; Mermaid diagram sanitization does not sanitize surrounding authored HTML or isolate preview scripts. Provider-token before/after impact was not measured.