feat: jpa, messaging, notification, mongo, graphql 어댑터터 구현체 추가

docs/jpa/repository-adaptation.md

@@ -35,8 +35,19 @@ This is the same adaptation already applied to the HTTP client platform
 | `jpa-spring-boot-starter` | `:app-bootstrap` (`dev.caskeleton.bootstrap.autoconfigure.jpa`) | This repository's composition root owns wiring, startup validation, and actuator surface; an adapter leaf must not auto-configure itself. `AGENTS.md` assigns composition to `app-bootstrap`. |
 | `jpa-testkit`, `jpa-testkit-postgresql`, `jpa-testkit-migration`, `jpa-testkit-queryplan` | `:adapter:outbound:persistence-jpa` `src/testkit/java/**/testkit` | The plan forbids production modules depending on the testkit. A source set whose dependencies are declared only on test configurations gives the same guarantee without a new Gradle project, and more than one lane consumes it. |
 
-The package boundary is enforced by `JpaModuleBoundaryTest`, which reproduces the plan's
-§3 module dependency map as package rules.
+The package boundary is enforced by `JpaModuleBoundaryTest`. It holds a closed catalog of the
+production root's direct child packages, compares that catalog against the tree for exact equality,
+checks every observed top-level edge against the declared ones, and rejects cycles.
+
+This used to be a stronger claim than the test. The catalog listed thirteen packages while the tree
+held twenty-two, so nine — `audit`, `config`, `failure`, `fileserver`, `h2`, `idempotency`, `lock`,
+`notification`, `outbox` — were governed by nothing, and a `transaction → postgresql` /
+`postgresql → transaction` cycle passed. Both are closed now, and the catalog's exact-equality check
+is what keeps a new package from being green by omission.
+
+**Known gap.** The catalog governs top-level packages. Sub-package edges inside one top-level
+package are not checked, and the target tree in the review's JPA-023 (a `capability/*` layout) is
+not implemented — the notification configuration facade is the first step toward it.
 
 ## 2. Package mapping
 

docs/jpa/support-matrix.md

@@ -1,23 +1,52 @@
 # JPA Persistence Platform — Support Matrix
 
-The machine-readable source for `JpaReleaseManifest`. A release gate parses this file, so a version
-or gate that stops being named here stops being claimed — and the build fails rather than the
-document quietly drifting from the code.
+**This document is a rendering. The machine-readable source is
+[`src/config/jpa/release-registry.json`](../../src/config/jpa/release-registry.json).**
+
+`JpaReleaseManifest` used to parse this file with regular expressions: every `PostgreSQL NN` it
+mentioned became a supported version, whatever table or sentence produced the match. An Experimental
+major joined the Stable list, a version named once in prose counted as supported, and demoting a
+major changed nothing so long as the string survived somewhere in the document. Now the registry
+declares a support level per major as a field, each gate names the Gradle task that produces its
+evidence, and this document describes what the registry says.
 
 ## Database
 
 | Database | Support | Evidence |
 |---|---|---|
-| PostgreSQL 16 | Stable | full contract suite, release lane |
-| PostgreSQL 17 | Stable | full contract suite, release lane |
-| PostgreSQL 18 | Stable | full contract suite, release lane |
+| PostgreSQL 16 | Stable | full contract suite, release lane (own matrix job) |
+| PostgreSQL 17 | Stable | full contract suite, release lane (own matrix job) |
+| PostgreSQL 18 | Stable | full contract suite, release lane (own matrix job) |
 | PostgreSQL 19 | Experimental | compatibility lane only; promotion requires an ADR |
 | H2 | Local convenience | **never** evidence of PostgreSQL behaviour |
 
-H2 is not a second production target. It reports different SQLSTATEs for the same violation, has no
-`SKIP LOCKED` guarantee the platform relies on, no JSONB operators, no range types, and no
-concurrent index builds. A green H2 run is evidence that the code compiles and runs, and nothing
-more.
+Each major gets its **own release job**, because for a while it did not. The release lane passed
+`-Pjpa.matrix.versions=16,17,18` to a `JpaPlatformContractSupport.start()` that used
+`selectedVersions().get(0)`, so the whole integration suite ran against PostgreSQL 16 and this table
+recorded 17 and 18 as fully covered on the strength of a three-assertion smoke test. `start()` now
+refuses a multi-version selection outright, `jpa-release.yml` fans out to one job per major, and a
+promotion job requires all three majors' evidence to carry the same commit SHA — so a removed major
+removes the release, not the evidence for it.
+
+**Provider baseline.** The gates run against the Hibernate version the Spring Boot BOM resolves —
+**7.1.8.Final** — which the registry records as `stable-tested-baseline`. This document previously
+called 7.4 the Stable baseline and the pagination gate was named `hibernate-7.4-fetch-pagination`,
+so every run of that gate produced evidence labelled with a provider it had never executed against.
+7.4 is recorded as `compatibility-target`; it becomes the baseline when a full lane has actually run
+on it.
+
+H2 is not a second production target. It reports different SQLSTATEs for the same violation, no JSONB
+operators, no range types, and no concurrent index builds. A green H2 run is evidence that the code
+compiles and runs, and nothing more.
+
+`SKIP LOCKED` needs its own sentence, because two documents said different things about it. The
+module's `CLAUDE.md` records a measurement: H2 2.4.240 accepts `FOR UPDATE SKIP LOCKED` and does
+genuinely skip locked rows, which is why the outbox claim SQL is identical on both vendors. This
+document previously said H2 has no such guarantee. Both are right about different questions, and
+the distinction is the point: **observed behaviour in the version we measured is not a production
+guarantee, and it is never PostgreSQL contract evidence.** The measurement is why the claim SQL
+needs no vendor branch; the absence of a guarantee is why every concurrency contract still runs
+against a real PostgreSQL.
 
 ## Specification and provider
 
@@ -67,7 +96,7 @@ Each row is a way the platform could pass its tests and still be wrong in produc
 | `osiv-disabled` | gate | lazy loading from the view layer, one query per rendered row |
 | `flyway-validate` | gate | Hibernate mutating a deployed schema, or running against one it was not built for |
 | `runtime-role-no-ddl` | gate | the application's own credential being able to alter or drop schema objects |
-| `hibernate-7.4-fetch-pagination` | gate | a paged collection fetch silently reading the whole table and paginating in memory |
+| `collection-fetch-pagination` | gate | a paged collection fetch silently reading the whole table and paginating in memory |
 
 ## Explicitly unsupported