Fullbleed 2.5.10: keep inline labels at their intended width

Fullbleed 2.5.10 fixes a regression in 2.5.9 that could wrap tracked flex and inline-block labels even when they had enough room. Invoice and report footers now keep their intended single-line layout.

python -m pip install --upgrade "fullbleed==2.5.10"

Try the Markdown to PDF starter for editable print CSS, bundled fonts, a two-page example, and a runnable ZIP. Its 69 checks pass on both Windows and Linux.

Rust users can update the fullbleed crate to 2.5.10. Node.js and .NET packages have separate release gates.

Intrinsic widths now include the fragment-edge letter spacing and layout-unit rounding used during layout. Min-content sizing recognizes collapsible-space word boundaries, while no-wrap runs retain their combined width. The styled-inline overlap correction remains intact. No public API or runtime dependency is added.

Upgrade note: Affected line breaks and PDF hashes can change. Review saved baselines, especially for tracked labels and footers.

All six sizing cases and 48 wrapping cases pass on Linux and Windows with independent text/glyph-position checks and retained native/PDFium previews. All 54 PDFs are byte-identical across those platforms. The six embedded-font sizing cases also have identical preview pixels; the unembedded Helvetica/Times wrapping cases retain documented host-dependent preview differences. Public 2.5.9 fails all four tracked sizing cases while its two zero-tracking controls pass.

Validation includes 500 Python tests, 1,325 default Rust tests and 1,326 Python/SVG Rust tests, 86 CSS fixtures, the Rust 1.85 packaged consumer, font checks, golden documents, designed examples, notebook execution, and real PDF responses from FastAPI, Flask, and Django. The two changed golden images and web invoice preview were reviewed against independent text positions. Public package hashes and fresh Python/Rust consumers were checked after publication.

This evidence is scoped to the retained fixtures. It does not establish general CSS parity or PDF standards conformance. The dedicated PDF/VT validator remains unconfigured.

See PR #45 and the release runbook. Attached distributions and verification evidence include checksums and source provenance.