chore(release): open the 2.1 development line (#436)

* build(release): bump develop to 2.1.0-SNAPSHOT

The 2.1 cycle ships the fixed-layout PPTX render backend and new public
DocumentSession PPTX methods — additive public surface, so the next
release is a minor, not the 2.0.1 patch the GA bump left as a placeholder.
Move all 13 reactor version sites to 2.1.0-SNAPSHOT so the in-development
version signals the minor and japicmp compares the 2.1 line against the
2.0.0 baseline. README/web/module install snippets stay on the latest
published 2.0.0 until 2.1.0 ships — VersionConsistencyGuardTest enforces
both halves.

* docs(api): record the 2.1 surface with correct @SInCE tags

Keep-with-next and the alpha-state helpers landed after the v2.0.0 tag, but
their Javadoc claimed `@since 2.0.0` and their changelog entries sat under the
dated `## v2.0.0 — 2026-07-13` heading. Both are published artifacts — the
javadoc jar on Central is immutable and the changelog section becomes the
GitHub Release notes — so a reader upgrading from 2.0.0 was told the API had
always been there.

Retag the six members that shipped in this cycle (`DocumentNode.keepWithNext`,
`SectionBuilder.keepWithNext` and its boolean overload, `LineBuilder.keepWithNext`
and its boolean overload, `NodeDefinition.firstSliceHeight`) to `@since 2.1.0`,
and add the missing tag to five members that had none: `MarkdownInline`'s
`appendTransformed` / `appendUpperCased` / `appendIfPresent` and
`PdfRenderEnvironment`'s `fillAlphaState` / `strokeAlphaState`.

Move the four keep-with-next entries out of the v2.0.0 section into v2.1.0 and
open that section as `## v2.1.0 — Planned`, the header form the release script
dates. Record the node-model delta the feature entries omitted: the new default
method on `DocumentNode` and the trailing `keepWithNext` component on
`SectionNode` (13 -> 14) and `LineNode` (17 -> 18), which leaves constructor
calls working through the previous-arity overloads but changes what a record
deconstruction pattern must bind.

The compat constructors themselves keep no `@since` — their signatures were the
canonical record constructors at v2.0.0 and have been callable since then.

Verified: full reactor `clean verify` green (1508 tests, 0 failures); japicmp
against the 2.0.0 baseline green with the gate active at 2.1.0-SNAPSHOT;
`javadoc:javadoc` green across the six published modules.

Author: DemchaAV

CHANGELOG.md

@@ -3,10 +3,49 @@
 All notable changes to GraphCompose are documented here. Versions
 follow semantic versioning; release dates are ISO 8601.
 
-## v2.1.0 — in progress
+## v2.1.0 — Planned
 
 ### Public API
 
+- **Keep a heading with its content** — `SectionBuilder.keepWithNext()`. A section
+  marked keep-with-next is never left stranded as the last block on a page apart from
+  the content it introduces: when the section plus the first slice of the following
+  block would overflow the remaining page space (but fit on a fresh page), the section
+  relocates to the next page so the heading stays glued to its body. The first slice is
+  a paragraph's first line, a table's repeated header rows plus first body row, or a
+  list's first item, so the rule holds whether the following block is atomic or a
+  page-spanning table or list. Distinct from `keepTogether()`, which relocates a
+  *whole* block — keep-with-next binds only the start of the following block, the right
+  tool for a boxed section title above a long, page-spanning body. Inert when nothing
+  follows (a trailing heading is never moved) and best-effort when the heading plus the
+  first slice cannot share a page. Default off, so layouts that do not opt in are
+  unchanged.
+- `LineBuilder.keepWithNext()` — the line counterpart of
+  `SectionBuilder.keepWithNext()`, so a full-width header rule joins its banner's
+  keep-with-next run and the whole title block (rule + banner + rule) relocates
+  together instead of the banner stranding apart from its rules or its body.
+- Keep-with-next surfaces on the node model as well: `DocumentNode.keepWithNext()`
+  is a new default method (existing implementations keep the `false` default and
+  need no change), and `SectionNode` and `LineNode` each gain a trailing
+  `keepWithNext` record component. Constructor calls are unaffected — both records
+  keep an overload at the previous argument count that defaults the flag to
+  `false` — but the canonical component count changed (`SectionNode` 13 → 14,
+  `LineNode` 17 → 18), so a **record deconstruction pattern** written against the
+  2.0.0 component list must add the new binding to compile.
+- **Single-column CV presets no longer orphan a section title.** Every preset whose
+  sections flow down the page — BoxedSections, MinimalUnderlined, ModernProfessional,
+  Executive, CenteredHeadline, BlueBanner, EditorialBlue, and ClassicSerif — keeps a
+  section heading with the first line of its body across a page break: a standalone
+  header section binds to the following body section (a multi-node rule + banner + rule
+  group binds as one run), and a combined header+body module keeps the heading in a
+  nested keep-with-next group — including Panel's full-width Profile card, whose header
+  now stays with the summary if a long profile splits the card. Multi-column presets
+  place their sections in fixed columns that do not paginate, so no heading can strand
+  there.
+- **The Modern Proposal template no longer orphans a section heading.** Its flowing
+  section bodies, the Timeline and Investment tables, and the Acceptance terms each keep
+  their title with the first line of the block it introduces across a page break — each
+  title now renders in its own keep-with-next section rather than a bare paragraph.
 - **CV entry titles and subtitles accept inline `[text](url)` links.** In the layered
   CV presets, a `[label](url)` in an experience/education entry title or subtitle now
   renders as a clickable hyperlink — the same inline-Markdown convention already used
@@ -303,37 +342,6 @@ for this cycle.
 
 ### Public API
 
-- **Keep a heading with its content** — `SectionBuilder.keepWithNext()`. A section
-  marked keep-with-next is never left stranded as the last block on a page apart from
-  the content it introduces: when the section plus the first slice of the following
-  block would overflow the remaining page space (but fit on a fresh page), the section
-  relocates to the next page so the heading stays glued to its body. The first slice is
-  a paragraph's first line, a table's repeated header rows plus first body row, or a
-  list's first item, so the rule holds whether the following block is atomic or a
-  page-spanning table or list. Distinct from `keepTogether()`, which relocates a
-  *whole* block — keep-with-next binds only the start of the following block, the right
-  tool for a boxed section title above a long, page-spanning body. Inert when nothing
-  follows (a trailing heading is never moved) and best-effort when the heading plus the
-  first slice cannot share a page. Default off, so layouts that do not opt in are
-  unchanged.
-- `LineBuilder.keepWithNext()` — the line counterpart of
-  `SectionBuilder.keepWithNext()`, so a full-width header rule joins its banner's
-  keep-with-next run and the whole title block (rule + banner + rule) relocates
-  together instead of the banner stranding apart from its rules or its body.
-- **Single-column CV presets no longer orphan a section title.** Every preset whose
-  sections flow down the page — BoxedSections, MinimalUnderlined, ModernProfessional,
-  Executive, CenteredHeadline, BlueBanner, EditorialBlue, and ClassicSerif — keeps a
-  section heading with the first line of its body across a page break: a standalone
-  header section binds to the following body section (a multi-node rule + banner + rule
-  group binds as one run), and a combined header+body module keeps the heading in a
-  nested keep-with-next group — including Panel's full-width Profile card, whose header
-  now stays with the summary if a long profile splits the card. Multi-column presets
-  place their sections in fixed columns that do not paginate, so no heading can strand
-  there.
-- **The Modern Proposal template no longer orphans a section heading.** Its flowing
-  section bodies, the Timeline and Investment tables, and the Acceptance terms each keep
-  their title with the first line of the block it introduces across a page break — each
-  title now renders in its own keep-with-next section rather than a bare paragraph.
 - **Reproducible PDF output** (`@Beta`). `PdfFixedLayoutBackend.builder().deterministic(true)`
   (or `.deterministic(Instant)` for an explicit timestamp) pins the document
   CreationDate / ModDate and derives the PDF `/ID` from the document metadata instead

benchmarks/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.github.demchaav</groupId>
         <artifactId>graph-compose-build</artifactId>
-        <version>2.0.1-SNAPSHOT</version>
+        <version>2.1.0-SNAPSHOT</version>
         <relativePath>../pom.xml</relativePath>
     </parent>
 

bundle/pom.xml

@@ -32,7 +32,7 @@
         graph-compose and graph-compose-templates dependencies below use
         ${project.version}, so they follow automatically.
     -->
-    <version>2.0.1-SNAPSHOT</version>
+    <version>2.1.0-SNAPSHOT</version>
     <packaging>jar</packaging>
 
     <name>GraphCompose Bundle</name>

core/pom.xml

@@ -6,7 +6,7 @@
 
     <groupId>io.github.demchaav</groupId>
     <artifactId>graph-compose-core</artifactId>
-    <version>2.0.1-SNAPSHOT</version>
+    <version>2.1.0-SNAPSHOT</version>
 
     <name>GraphCompose Core</name>
     <description>A declarative layout engine for programmatic document generation, implemented primarily in Java. This is the lean engine coordinate; depend on the `graph-compose` artifact for the drop-in, PDF-capable install.</description>

core/src/main/java/com/demcha/compose/document/dsl/LineBuilder.java

@@ -289,7 +289,7 @@ public LineBuilder fill() {
      * {@link SectionBuilder#keepWithNext()}.
      *
      * @return this builder
-     * @since 2.0.0
+     * @since 2.1.0
      */
     public LineBuilder keepWithNext() {
         this.keepWithNext = true;
@@ -301,7 +301,7 @@ public LineBuilder keepWithNext() {
      *
      * @param value true to keep the line with the next block
      * @return this builder
-     * @since 2.0.0
+     * @since 2.1.0
      */
     public LineBuilder keepWithNext(boolean value) {
         this.keepWithNext = value;

core/src/main/java/com/demcha/compose/document/dsl/SectionBuilder.java

@@ -60,7 +60,7 @@ public SectionBuilder keepTogether(boolean value) {
      * nothing follows the section on the page.
      *
      * @return this builder
-     * @since 2.0.0
+     * @since 2.1.0
      */
     public SectionBuilder keepWithNext() {
         this.keepWithNext = true;
@@ -72,7 +72,7 @@ public SectionBuilder keepWithNext() {
      *
      * @param value true to keep the section with the first line of the next block
      * @return this builder
-     * @since 2.0.0
+     * @since 2.1.0
      */
     public SectionBuilder keepWithNext(boolean value) {
         this.keepWithNext = value;

core/src/main/java/com/demcha/compose/document/layout/NodeDefinition.java

@@ -132,7 +132,7 @@ default List<LayoutFragment> emitOverlayFragments(PreparedNode<E> prepared,
      *
      * @param prepared prepared node whose first slice is being measured
      * @return the first slice's height in points
-     * @since 2.0.0
+     * @since 2.1.0
      */
     default double firstSliceHeight(PreparedNode<E> prepared) {
         return prepared.measureResult().height();

core/src/main/java/com/demcha/compose/document/node/DocumentNode.java

@@ -99,7 +99,7 @@ default boolean keepTogether() {
      * siblings relocate together, with the break hoisted before the run.</p>
      *
      * @return true to keep this node with the first line of the following block
-     * @since 2.0.0
+     * @since 2.1.0
      */
     default boolean keepWithNext() {
         return false;

coverage/pom.xml

@@ -29,7 +29,7 @@
     <parent>
         <groupId>io.github.demchaav</groupId>
         <artifactId>graph-compose-build</artifactId>
-        <version>2.0.1-SNAPSHOT</version>
+        <version>2.1.0-SNAPSHOT</version>
         <relativePath>../pom.xml</relativePath>
     </parent>
 

examples/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.github.demchaav</groupId>
         <artifactId>graph-compose-build</artifactId>
-        <version>2.0.1-SNAPSHOT</version>
+        <version>2.1.0-SNAPSHOT</version>
         <relativePath>../pom.xml</relativePath>
     </parent>