[DO NOT MERGE] Runbook: revert celery-beat migrations in prod

[ajeety4]

Summary

• Runbook for cleaning up the partial migration state left by the failed 2026-05-18 DatabaseScheduler deploy, before feat: configure celery beat with file-based schedule #229 ships.
• Do not merge. Draft PR opened purely so reviewers can comment on the steps before execution.

Test plan

• N/A — docs-only.

🤖 Generated with Claude Code

[sravfeyn]

Isn't this simply a matter of getting into the right docker instance and running below?

(Confirm an RDS snapshot exists on AWS)

# make sure we are in the right instance
./manage.py showmigrations messaging django_celery_beat 
# reset migrations
./manage.py migrate messaging 0007
./manage.py migrate django_celery_beat zero

May be claude runbook is not the right tool here given that this is a one off, one environment task?

[ajeety4]

Isn't this simply a matter of getting into the right docker instance and running below?

(Confirm an RDS snapshot exists on AWS)

# make sure we are in the right instance
./manage.py showmigrations messaging django_celery_beat 
# reset migrations
./manage.py migrate messaging 0007
./manage.py migrate django_celery_beat zero

May be claude runbook is not the right tool here given that this is a one off, one environment task?

Yes. Just a correction, we need to create the right docker container.
The runbook I created just list down the steps with details, I plan to run all the steps manually.

I have updated the steps in the PR description to be run.