优化结构

internal/integration/README.md

@@ -8,7 +8,7 @@ state, or translate provider-specific protocols into `biz` interfaces.
 
 - `cache`: Redis-backed cache with an in-memory fallback.
 - `email`: SMTP email repository.
-- `mq`: reloadable EMQX/MQTT client exposed through the shared `pkg/mq` interface.
+- `mq`: reloadable EMQX/MQTT and RabbitMQ/AMQP clients exposed through the shared `pkg/mq` interface.
 - `payment`: payment-channel SDKs and callback/signature handling.
 - `storage`: local and object-storage implementations of `biz.FileStorage`.
 - `websocket`: reloadable Melody endpoint exposed through the shared
@@ -28,7 +28,7 @@ Business modules depend on `websocket.Hub` and `mq.Client` from the shared
 `pkg/websocket` and `pkg/mq` packages; they do not construct
 Melody or Paho clients and do not read system configuration directly. The
 system integration packages own runtime refresh and shutdown. Registered
-WebSocket handlers and MQTT subscriptions are retained when database-backed
+WebSocket handlers and broker subscriptions are retained when database-backed
 configuration replaces a live client.
 
 ```go
@@ -45,7 +45,8 @@ Integration configuration is stored in `sys_integration_configs`:
 
 - WebSocket: `kind=websocket`, `provider=melody`
 - EMQX: `kind=mq`, `provider=emqx`
+- RabbitMQ: `kind=mq`, `provider=rabbitmq`
 
-The YAML values are only migration/bootstrap inputs. After the integration
-table exists, the database is authoritative and runtime updates are applied
-without restarting the process. The WebSocket public path defaults to `/ws`.
+These three integrations are stored only in `sys_integration_configs`; they do
+not come from `config.yaml`. Runtime updates are applied without restarting
+the process. The WebSocket public path defaults to `/ws`.