Maintainer onboarding
A practical sequence for getting comfortable with ReplyBox without guessing around production. Move through it in order; each step gives you a sharper picture of the system.
Read CLAUDE.md, docs/plan.md, and docs/deployment-workflow.md.
Skim the handover and critical rules pages before touching code.
Get the local stack running end to end.
Pair a throwaway WhatsApp number for local development.
Set up read-only production database access through pgweb using replybox_ro.
Install and authenticate doctl; verify deployment listing and component logs.
Run python -m app.cli diagnose-stuck-sends against production once so healthy output is familiar.
Audit DigitalOcean App Platform env vars against apps/api/app/config.py.
Do one trivial release end to end, ideally a small web copy change.
Record the release evidence, then prune dead branches as you encounter them.
Ready signal
You can run the stack, read production safely, inspect deploy logs, recognise a healthy stuck-send diagnosis, and explain why releases require explicit approval.