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

docs/messaging/configuration-reference.md

@@ -1,9 +1,18 @@
 # 설정 레퍼런스
 
+> **Prefix.** Every property below binds under `app.messaging`, which is the prefix the deployed
+> runtime and the `APP_MESSAGING_*` environment variables already use. Earlier revisions of this
+> page documented a bare `messaging` prefix and the starter bound `backend.messaging`; neither
+> bound what this page describes, so a deployment configured from it changed nothing. A key under
+> either of the old prefixes now fails startup with a message naming the key — see
+> `MessagingPrefixMigrationValidator`.
+
+
 ## Destination profile
 
 ```yaml
-messaging:
+app:
+  messaging:
   destinations:
     order-events:
       broker: kafka-primary
@@ -77,7 +86,8 @@ messaging:
 ### Kafka
 
 ```yaml
-messaging:
+app:
+  messaging:
   brokers:
     kafka-primary:
       type: kafka
@@ -96,7 +106,8 @@ messaging:
 ### RabbitMQ
 
 ```yaml
-messaging:
+app:
+  messaging:
   brokers:
     rabbit-primary:
       type: rabbitmq
@@ -117,7 +128,8 @@ messaging:
 ## 보안
 
 ```yaml
-messaging:
+app:
+  messaging:
   security:
     kafka-primary:
       producer: { type: SASL_SCRAM, credential-id: kafka-producer }
@@ -135,7 +147,8 @@ messaging:
 기본값은 전부 `false`다.
 
 ```yaml
-messaging:
+app:
+  messaging:
   experimental:
     kafka-share: false
     pulsar: false
@@ -147,7 +160,8 @@ messaging:
 ## Backpressure
 
 ```yaml
-messaging:
+app:
+  messaging:
   backpressure:
     global-limit: 512
     per-destination-limit: 64      # global-limit 이하여야 한다