chore: rename Maven artifactId graphcompose -> graph-compose ahead of Central debut (#105)

Reads better on Maven Central. Done now while there is still no
artefact on Central to break — the v1.6.6 cut will be the first
publish, and we choose hyphenated coordinates from day one.

All four artefacts rename:
- root library    graphcompose            -> graph-compose
- reactor parent  graphcompose-build      -> graph-compose-build
- examples module graphcompose-examples   -> graph-compose-examples
- benchmarks      graphcompose-benchmarks -> graph-compose-benchmarks

The internal Maven property <graphcompose.version> stays as-is — it
is build-tool wiring, not a documented coord, and renaming it would
ripple across every ${graphcompose.version} reference for zero
external benefit. Same for system properties like
-Dgraphcompose.visual.approve and the Java package
com.demcha.compose: the rename is a coord-level concern, not a
brand or codebase rename.

Build chain updated atomically (4 poms) so dependency resolution
keeps working end-to-end: examples/pom.xml + benchmarks/pom.xml
parent refs flip to graph-compose-build, their library dep flips
to graph-compose, and the property they read (graphcompose.version)
still resolves from the same source via the reactor.

Forward-facing docs all switch to the new coord:
- README install snippet (Maven + Gradle) + the Maven Central badge
  URL + the "Distribution" note + the javadoc.io URL
- docs/index.html JSON-LD downloadUrl + the Maven + Gradle install
  snippet panels
- CONTRIBUTING.md release-flow javadoc.io URL
- SECURITY.md artifacts line
- ROADMAP.md "Maven Central distribution" entry + the hypothetical
  future split into graph-compose-{core,pdf,docx,templates,testing}
- docs/templates/which-template-system.md "Maven coordinates do not
  change in 2.0" section
- docs/roadmaps/v1.6-roadmap.md Phase E README-snippet wording +
  the benchmark-module artifact reference + the release-identity
  Maven coords line
- docs/contributing/release-process.md top distribution coords
  block + Phase 0.D parent-artifact name + Phase 2.B dependency:get
  command + Phase 6 done-criteria dependency:get command
- CHANGELOG.md v1.6.6 Planned: hero paragraph rewritten to call out
  the hyphenated artifactId, JitPack legacy notice clarified, the
  javadoc.io URL flipped

Historical lessons-learned in docs/contributing/release-process.md
sections 167-169 keep verbatim references to graphcompose-build /
the graphcompose dependency — they describe what happened during
v1.6.0 / v1.6.5 prep when the artifactId was graphcompose, and
rewriting them would falsify history.

scripts/cut-release.ps1 regexes:
- Update-ReadmeVersion: primary Maven Central regex now matches
  <artifactId>graph-compose</artifactId>; legacy graphcompose +
  JitPack regexes kept as ordered fallbacks
- Update-IndexHtmlVersion: Central downloadUrl regex, Maven snippet
  regex, and Gradle snippet regex all switch to graph-compose

VersionConsistencyGuardTest regex list extended to try
graph-compose first, then graphcompose, then the legacy JitPack
format — the snippet check passes on any of the three. Same pattern
on README and docs/index.html. Once the rename is the only form
left, the older patterns can be removed in a cleanup PR; keeping
them now means the test does not flake during the transition
window if any stale snippet sneaks through review.

Build verified: 4-pom dependency resolution OK (./mvnw -DskipTests
install -pl . + ./mvnw -f examples/pom.xml clean compile + ./mvnw
-f benchmarks/pom.xml clean compile all green). Guard suite green:
CanonicalSurfaceGuardTest + DocumentationExamplesTest +
DocumentationCoverageTest + VersionConsistencyGuardTest +
PublicApiNoEngineLeakTest + SemanticLayerNoPdfBoxDependencyTest =
33/0/0. GenerateAllExamples exit 0, 53 PDFs, no layout errors.

Author: DemchaAV

CHANGELOG.md

@@ -6,24 +6,26 @@ follow semantic versioning; release dates are ISO 8601.
 ## v1.6.6 — Planned
 
 **First Maven Central release.** GraphCompose now ships under
-`io.github.demchaav:graphcompose:1.6.6` alongside the existing
-JitPack distribution. The release adds publishable sources/javadoc
-jars, GPG-signed artefacts, a binary-compatibility gate against
-v1.6.5, the metadata Maven Central requires, and a substantial
-documentation polish for the maturity / stability / migration story.
+`io.github.demchaav:graph-compose:1.6.6` — note the **hyphenated**
+artifactId, chosen for readability ahead of the Central debut. The
+release adds publishable sources/javadoc jars, GPG-signed artefacts,
+a binary-compatibility gate against v1.6.5, the metadata Maven
+Central requires, and a substantial documentation polish for the
+maturity / stability / migration story.
 
 **Zero breaking changes from v1.6.5.** Existing JitPack callers continue
-to resolve through the same coordinates; existing API surface compiles
-and runs unchanged (validated by the new `japicmp` gate against the
-v1.6.5 baseline). New: the `@Beta` annotation marker, the `@since 1.0.0`
-class-level Javadoc on entry-point packages, and a curated docs pass
-(decision guide for the two template surfaces, examples maturity index,
-explicit API stability policy).
-
-**Migration from v1.6.5:** no code changes required. Optionally swap
-the JitPack `<dependency>` for the Maven Central equivalent
-(`io.github.demchaav:graphcompose:1.6.6`); both publish paths continue
-to ship the same artefact.
+to resolve through the same coordinates (`com.github.DemchaAV:GraphCompose:v1.6.5`);
+existing API surface compiles and runs unchanged (validated by the new
+`japicmp` gate against the v1.6.5 baseline). New: the `@Beta`
+annotation marker, the `@since 1.0.0` class-level Javadoc on
+entry-point packages, and a curated docs pass (decision guide for
+the two template surfaces, examples maturity index, explicit API
+stability policy).
+
+**Migration from v1.6.5:** no code changes required. Swap the
+JitPack `<dependency>` for the Maven Central form
+(`io.github.demchaav:graph-compose:1.6.6`). The legacy JitPack URL
+keeps resolving for callers pinned to v1.6.5 and earlier.
 
 ### Build
 
@@ -63,7 +65,7 @@ to ship the same artefact.
   alongside the existing JitPack step.
 - **Hosted Javadocs via `javadoc.io`** (Track H3). README's
   distribution-status note now points callers at
-  [javadoc.io/doc/io.github.demchaav/graphcompose](https://javadoc.io/doc/io.github.demchaav/graphcompose),
+  [javadoc.io/doc/io.github.demchaav/graph-compose](https://javadoc.io/doc/io.github.demchaav/graph-compose),
   which auto-mirrors any artefact published to Maven Central within
   minutes — no separate hosting infrastructure required. The note
   also pins Maven Central as the going-forward primary distribution

CONTRIBUTING.md

@@ -78,7 +78,7 @@ GraphCompose follows a fork → feature branch → pull request flow. Exte
 
 1. **Release prep** lands on `develop` — version bumps propagate via `aggregator/pom.xml` to all modules in one pass; fresh CHANGELOG entry; migration guide for minor releases. **README install snippet stays pinned to the previously published version** until Maven Central confirms the new artifact, otherwise consumers copying the snippet during the publish window hit a 404.
 2. **`scripts/cut-release.ps1 -Version <X.Y.Z>`** automates the bump + CHANGELOG date + commit + tag + push from `develop`. The maintainer fast-forwards `main` from `develop` after the tag lands (`git push origin develop:main`).
-3. **Maven Central** picks up the new tag automatically via [`.github/workflows/publish.yml`](./.github/workflows/publish.yml) &mdash; the workflow re-runs `mvnw verify` at the tagged commit, signs the four artefacts (main / sources / javadoc / pom) with the repo's GPG key, and uploads via the `central-publishing-maven-plugin`. Hyphenated tags (`-rc`, `-alpha`, `-beta`) are skipped on Central; they ship only to the GitHub Release pre-release surface. Javadocs auto-publish to [javadoc.io/doc/io.github.demchaav/graphcompose](https://javadoc.io/doc/io.github.demchaav/graphcompose) shortly after each Central release.
+3. **Maven Central** picks up the new tag automatically via [`.github/workflows/publish.yml`](./.github/workflows/publish.yml) &mdash; the workflow re-runs `mvnw verify` at the tagged commit, signs the four artefacts (main / sources / javadoc / pom) with the repo's GPG key, and uploads via the `central-publishing-maven-plugin`. Hyphenated tags (`-rc`, `-alpha`, `-beta`) are skipped on Central; they ship only to the GitHub Release pre-release surface. Javadocs auto-publish to [javadoc.io/doc/io.github.demchaav/graph-compose](https://javadoc.io/doc/io.github.demchaav/graph-compose) shortly after each Central release.
 4. **GitHub Release** is created with notes from the matching `CHANGELOG.md` section.
 
 See [docs/contributing/release-process.md](./docs/contributing/release-process.md) for the full checklist (audit gates, hotfix protocol, lessons learned).

README.md

@@ -12,7 +12,7 @@
 <p align="center">
   <a href="https://github.com/DemchaAV/GraphCompose/actions/workflows/ci.yml?query=branch%3Amain"><img src="https://img.shields.io/github/actions/workflow/status/DemchaAV/GraphCompose/ci.yml?branch=main&style=for-the-badge&label=CI" alt="CI"/></a>
   <a href="https://github.com/DemchaAV/GraphCompose/releases/latest"><img src="https://img.shields.io/github/v/release/DemchaAV/GraphCompose?style=for-the-badge&label=Release" alt="Latest release"/></a>
-  <a href="https://central.sonatype.com/artifact/io.github.demchaav/graphcompose"><img src="https://img.shields.io/maven-central/v/io.github.demchaav/graphcompose?style=for-the-badge&label=Maven%20Central" alt="Maven Central"/></a>
+  <a href="https://central.sonatype.com/artifact/io.github.demchaav/graph-compose"><img src="https://img.shields.io/maven-central/v/io.github.demchaav/graph-compose?style=for-the-badge&label=Maven%20Central" alt="Maven Central"/></a>
   <img src="https://img.shields.io/badge/Java-17%2B-orange?style=for-the-badge&logo=openjdk" alt="Java 17+"/>
   <img src="https://img.shields.io/badge/PDFBox-3.0-red?style=for-the-badge" alt="PDFBox 3.0"/>
   <img src="https://img.shields.io/badge/License-MIT-blue?style=for-the-badge" alt="MIT License"/>
@@ -96,18 +96,18 @@ GraphCompose uses PDFBox under the hood as the rendering backend &mdash; the com
 ```xml
 <dependency>
     <groupId>io.github.demchaav</groupId>
-    <artifactId>graphcompose</artifactId>
+    <artifactId>graph-compose</artifactId>
     <version>1.6.6</version>
 </dependency>
 ```
 
 ```kotlin
-dependencies { implementation("io.github.demchaav:graphcompose:1.6.6") }
+dependencies { implementation("io.github.demchaav:graph-compose:1.6.6") }
 ```
 
 > **Distribution** &mdash; Maven Central is the canonical channel from **v1.6.6** onwards
-> (`io.github.demchaav:graphcompose:<version>`). Hosted Javadocs auto-publish to
-> [javadoc.io/doc/io.github.demchaav/graphcompose](https://javadoc.io/doc/io.github.demchaav/graphcompose)
+> (`io.github.demchaav:graph-compose:<version>`). Hosted Javadocs auto-publish to
+> [javadoc.io/doc/io.github.demchaav/graph-compose](https://javadoc.io/doc/io.github.demchaav/graph-compose)
 > shortly after each Central release. The legacy JitPack URL
 > (`com.github.DemchaAV:GraphCompose:v<version>`) remains resolvable for callers
 > pinned to v1.6.5 and earlier but is no longer the documented install option.

ROADMAP.md

@@ -8,7 +8,7 @@ In flight on `main` / `develop`.
 
 - v1.6 polish — documentation, examples, visual baselines, fixes.
 - Open-source hygiene — security policy, support guidance, dependency automation, security scanning.
-- **Maven Central distribution** — debut shipping in v1.6.6 under `io.github.demchaav:graphcompose`. Replaces JitPack as the primary install channel; the JitPack URL stays alive for existing pinned consumers but is no longer documented as a primary option. Tracked in [#7](https://github.com/DemchaAV/GraphCompose/issues/7).
+- **Maven Central distribution** — debut shipping in v1.6.6 under `io.github.demchaav:graph-compose`. Replaces JitPack as the primary install channel; the JitPack URL stays alive for existing pinned consumers but is no longer documented as a primary option. Tracked in [#7](https://github.com/DemchaAV/GraphCompose/issues/7).
 
 ## Next (v1.7)
 
@@ -23,7 +23,7 @@ Not committed. Reflects current thinking; priorities may shift based on user fee
 
 - **DOCX visibility for unsupported nodes.** Make currently-silent skips (`shape`, `line`, `ellipse`, `barcode`) loud — minimum a warn log, ideally a strict-mode flag that fails instead of dropping content silently.
 - **Backend-neutral layout measurement.** Decouple measurement from PDFBox-specific resources so non-PDF backends do not pull PDFBox into the dependency graph.
-- **Multi-module Maven layout.** Split the artifact into `graphcompose-core` / `graphcompose-pdf` / `graphcompose-docx` / `graphcompose-templates` / `graphcompose-testing` if there is clear demand. Adds release complexity, so requires a real adoption signal first.
+- **Multi-module Maven layout.** Split the artifact into `graph-compose-core` / `graph-compose-pdf` / `graph-compose-docx` / `graph-compose-templates` / `graph-compose-testing` if there is clear demand. Adds release complexity, so requires a real adoption signal first.
 - **DOCX maturity.** Either expand DOCX coverage toward PDF parity, or move DOCX behind an explicitly experimental flag.
 - **Property-based testing.** Random table spans, pagination edge cases, deeply nested layouts.
 - **Real PPTX export.** Current state is a manifest skeleton. Will only be built out if there is concrete user demand.

SECURITY.md

@@ -47,7 +47,7 @@ In scope:
 - DOCX / PPTX semantic backends (`com.demcha.compose.document.backend.semantic`).
 - Templates shipped in `com.demcha.compose.document.templates`.
 - Public authoring API (`GraphCompose`, `DocumentSession`, DSL).
-- Build and release artifacts on Maven Central (`io.github.demchaav:graphcompose`). The legacy JitPack URL remains available for consumers pinned to v1.6.5 and earlier but is no longer the documented install channel.
+- Build and release artifacts on Maven Central (`io.github.demchaav:graph-compose`). The legacy JitPack URL remains available for consumers pinned to v1.6.5 and earlier but is no longer the documented install channel.
 
 Out of scope:
 

aggregator/pom.xml

@@ -5,7 +5,7 @@
     <modelVersion>4.0.0</modelVersion>
 
     <groupId>io.github.demchaav</groupId>
-    <artifactId>graphcompose-build</artifactId>
+    <artifactId>graph-compose-build</artifactId>
     <version>1.6.5</version>
     <packaging>pom</packaging>
 

benchmarks/pom.xml

@@ -6,12 +6,12 @@
 
     <parent>
         <groupId>io.github.demchaav</groupId>
-        <artifactId>graphcompose-build</artifactId>
+        <artifactId>graph-compose-build</artifactId>
         <version>1.6.5</version>
         <relativePath>../aggregator/pom.xml</relativePath>
     </parent>
 
-    <artifactId>graphcompose-benchmarks</artifactId>
+    <artifactId>graph-compose-benchmarks</artifactId>
     <name>GraphCompose Benchmarks</name>
     <description>
         Performance benchmarks, stress tests, and endurance harnesses for
@@ -49,19 +49,19 @@
         <!-- The library under benchmark. -->
         <dependency>
             <groupId>io.github.demchaav</groupId>
-            <artifactId>graphcompose</artifactId>
+            <artifactId>graph-compose</artifactId>
             <version>${graphcompose.version}</version>
         </dependency>
 
         <!--
-            graphcompose's test-only fixtures (com.demcha.mock.*) used by
+            graph-compose's test-only fixtures (com.demcha.mock.*) used by
             CanonicalBenchmarkSupport for CV / invoice / proposal sample
             data. Pulled in via the tests-classifier jar published by
             the main module's maven-jar-plugin test-jar execution.
         -->
         <dependency>
             <groupId>io.github.demchaav</groupId>
-            <artifactId>graphcompose</artifactId>
+            <artifactId>graph-compose</artifactId>
             <version>${graphcompose.version}</version>
             <type>test-jar</type>
             <classifier>tests</classifier>