0.1.0-rc2

roc-pdf 0.1.0-rc2

This candidate closes Gate 4's production-visual compiler evidence and makes
the common authoring lifecycle more explicit.

Highlights:

• opaque Pdf.Prepared values with prepare-once buffered or chunked emission;
• complete 16-bit sRGB theme colors through the packaged profile and output
  intent;
• ergonomic 8-bit sRGB constructors and complete style, spacing, and margin
  theme setters;
• executable single-image figures using typed packed raster or validated JPEG
  sources, required alternative text, and optional visible captions;
• forward-compatible opaque vector/grouped drawings and content-first fixed
  pages;
• bounded InvalidDocument diagnostics with stable dotted feature codes for
  represented capabilities whose lowering is not executable yet;
• realistic runnable examples using the released basic-cli platform;
• generated public API documentation, checked for private-kernel leakage and
  published through GitHub Pages;
• refreshed capability and migration guidance.

Standard means the implemented deterministic PDF 2.0 subset. PDF/A-4 and
PDF/UA-2 are not claimed. Single-image figures are executable; broader drawing
composition and fixed pages reject atomically until their later contracts
close. Representability alone is not a capability claim.

0.1.0-rc1

roc-pdf 0.1.0-rc1

This early-development release candidate exposes the usable public Pdf
facade for deterministic PDF 2.0 generation under Pdf.Profile.Standard.
Pdf.to_bytes supports the built-in single-face authoring path for titles,
headings, paragraphs, and bulleted lists.

This is not a PDF/A-4 or PDF/UA-2 release. Archive and
AccessibleArchive remain unavailable and return structured capability errors;
they are never silently downgraded. The current public multi-face, full bidi,
and case-mapping boundaries are also incomplete. Do not claim archival or
accessibility conformance from this release candidate.

Pdf.to_chunks is not yet a usable authored-document delivery path. Use
Pdf.to_bytes for nonblank documents in this release candidate.

The bundle is validated with the repository's pinned official Roc nightly and
dev-backend test suite, then by compiling the public facade example against the
served bundle. The workflow never provisions a locally patched compiler.