[krflol]

The browser playground, its downloadable Python and Node projects, and the Rust quickstart still used Fullbleed 2.5.29. They now use the published 2.5.35 engine and npm 0.8.1, including the fixes for long tables, forced page breaks, and footnotes that move with their text. The Rust starter ZIP, guide, API links and homepage Cargo command use the same release. The existing playground source-size, page-count, memory and time limits remain enforced.

Nine shared pagination fixtures now run through native/WASI rendering, both real project exports, and the browser editor. Independent PDF readers check all 80 table rows, repeated headers, marker placement, footnote placement and page bounds. The browser check compares every displayed pagination page with the native preview.

Validation retained in docs/assets/playground/upgrade-verification-081.json:

• 29 native/WASI fixtures with identical PDF/PNG output and deterministic rerenders.
• 35 actual Python exports and 35 actual npm-installed Node exports with matching PDF/PNG output.
• 27 independent pagination checks across WASI, Python and Node; the previous playground build fails eight of the nine inputs while the fixed-height clipping control still passes.
• 159 Chrome UI checks, strict MkDocs build, internal links and Rust formatting.
• 29 compiled Rust quickstart fixtures match the playground's PDF/PNG output; 77 checks exercise the actual standalone Rust ZIP, including edited inputs, error handling and recovery.
• Both Rust binaries pass cargo check --release --locked --bins with the documented minimum Rust 1.85 compiler.

Nineteen prior fixtures retain identical PDF and preview bytes. The Common Ground report matches the already reviewed 2.5.35 starter output: its repeated heading moves down 0.75 pt on pages 2 and 3, with all other text geometry preserved. The historical upgrade records remain available.

The React starter manifest also links to its completed three-browser CI run. Its downloadable source and ZIP are unchanged; the successful follow-up commit only extended the WebKit dependency-installation timeout.