[krflol]

Component consumers need to know whether a reusable kit works on its own or requires document theme values. This guide and downloadable report demonstrate both contracts: a concrete palette factory and a kit with explicit prefixed tokens. Authors can rebrand either card or override one named part without inspecting generated selectors.

The guide explains defaults versus instance choices, missing bindings, document-wide token collisions, print/screen styling, and styled/unstyled HTML export. It links from the existing component guides and examples. Both modules are maintainer-authored; independent author feedback and the alpha stability decision remain open.

Validation:

• Executed the actual source ZIP with published Fullbleed 2.6.0a14. Four one-page PDFs have embedded fonts, expected content, no reported text overlaps and identical bytes on repeated rendering.
• PDFium comparisons confine each brand change to its card and the local override to its value. Negative checks cover missing tokens and unknown parts; collision and immutability checks retain their documented behavior.
• All three literal Python examples execute. Chromium checks all four styled and unstyled exports at desktop and mobile widths, including colors, layout and content.
• Strict MkDocs build, 154-page path/anchor checks, desktop/mobile guide review and actual ZIP download verification pass.
• Adds Windows and Linux CI checks that rebuild the ZIP, reproduce the published PDF bytes and decoded PNG pixels and verify the browser exports before deployment.

The PNG gate requires identical format, mode, dimensions, metadata and every decoded pixel. PNG compression can differ between platforms; the retained first Linux artifact had identical pixels and all four identical PDFs. Seven tests cover equivalent compression, altered pixels, dimensions, mode, gamma metadata, invalid data and a different image format. No visual tolerance or PDF-byte check was relaxed.