Fullbleed Node 0.4.1: engine 2.5.22

Fullbleed 0.4.1 brings the published 2.5.22 engine to Node and browser applications. It includes fixes for nested counters, filtered overflow inside clipped containers, border-image tiling, and floated initials. The adapter enables the engine's native SVG raster fallback; this adds no external renderer dependency.

npm install --save-exact fullbleed@0.4.1

Browser applications should recopy their runtime assets after upgrading:

npx fullbleed-browser-assets public/fullbleed

The JavaScript API and memory limit are unchanged. Review existing PDF baselines when upgrading because corrected layout can change appearance.

The exact attached tarball passed all 13 package CI jobs: Node 22/24/26 on Windows, Linux, and macOS, and Chrome, Firefox, and Playwright WebKit. Verification includes:

• 45 native/WASM PDF and finalized-preview comparisons, also matching local Windows output to CI Linux output.
• 13 focused engine fixtures with retained text, color, and Chrome print expectations: 26 worker/process cases on Windows and Linux, and 13 downloaded PDFs in each browser.
• 144 browser checks per browser engine, including actual downloads, failure recovery, and cancellation.
• 14 queue lifecycle checks in each of the nine installed Node/platform combinations.
• Exact preservation of the reviewed invoice and three-page report: PDF bytes, native previews, independently rendered pixels, extracted text, inputs, and fonts.

The evidence ZIP retains the public 0.4.0 control, which fails 24 of the 26 focused worker/process cases across all four fix families. It also retains an unpublished pin-only candidate's four blank SVG cases; enabling the native SVG fallback corrects those outputs. The test-only Noto Sans font is excluded from the npm package.

See the engine checks, browser guide, and queue guide.

These checks cover the retained fixtures and API behavior. They do not establish complete CSS parity or PDF/UA, PDF/A, PDF/X, or PDF/VT conformance. The native-runtime investigation in issue #7 remains open. The separately downloadable browser, React, Vue, and Next.js starters retain their existing verified package pins.

The fresh npm installation record verifies the registry tarball against CI, audits registry signatures and provenance, repeats the 14 queue lifecycle checks and 26 independent worker/process cases, and passes 144 Chrome checks plus 13 independently inspected downloads. Its PDFs and previews match the release evidence. The separate npm verification ZIP retains those outputs and test logs.