MessageWeave/docs
anonsaber ed93358e29 feat(notify): unify /ready not-ready 503 into the error envelope
- GET /ready: ready -> 200 + diagnostic report (unchanged success body);
  not ready -> 503 + {"error":"service_unavailable","request_id":id}
  + Retry-After: 30, consistent with the other public entry points
- drop the legacy {"status":"not_ready"} diagnostic block from the 503 body
  (backward compatibility not required)
- HTTP 200/503 semantics preserved, so Uptime Kuma HTTP(s) monitors
  (status-code based) keep working
- sync docs: README.md, README.zh-CN.md, docs/design.md, docs/deployment.md,
  AGENTS.md, docs/todo.md
2026-09-27 13:11:29 +08:00
..
deployment.md feat(notify): unify /ready not-ready 503 into the error envelope 2026-09-27 13:11:29 +08:00
design.md feat(notify): unify /ready not-ready 503 into the error envelope 2026-09-27 13:11:29 +08:00
todo.md feat(notify): unify /ready not-ready 503 into the error envelope 2026-09-27 13:11:29 +08:00