[Neup123]

Summary

• keep the existing sendText endpoint and queue only transient Automation Safety blocks
• persist queue payloads and schedules in PostgreSQL/MySQL so work survives restart and reconnect
• re-run the current safety policy immediately before delivery
• calculate earliest eligible time from the real rolling-window boundary
• reject permanent suppression, allowlist, quiet-hour, duplicate, and invalid-recipient decisions
• reject enqueue only when recent sent messages plus queued work reach instance or recipient daily capacity
• add GET and DELETE outboundQueue endpoints with detailed Swagger responses
• add migrations, unit/PostgreSQL tests, CI coverage, and English documentation

The database is authoritative and the worker functions without RabbitMQ. RabbitMQ is therefore optional rather than a durability dependency.

Validation

• npm run test:outbound-safety
• npm run test:outbound-queue
• npm run lint:check
• npm run build
• npm run audit:runtime-openapi
• npm run audit:chat-docs
• PostgreSQL migration/integration test runs in CI

Fixes #33