# jobs-recovery: lab5: worker down -> 202 -> restart api+broker -> ready; broker down -> outbox waits
# date: 2026-11-07 19:32:20, commit: 20afc2c + uncommitted changes
# command: python.exe student-tests/test_jobs.py worker-down broker-down
# exit code: 0, 60.4 s

--- worker-down: Защита п.2-3: worker остановлен -> 202 -> сообщение с вложением -> рестарт API+broker -> worker -> ready.
worker stopped
upload while worker is down -> 202 queued, attachment 5d7b65bc-2cb9-4b4a-801e-6c30173dd513
message with attachment 201, content 409, other messages 201; job 6133fe0a-b568-4024-8bb7-4d7d32ed0433 published, queue messages/unacked = (1, 0)
rabbitmq and api restarted with volumes; queue still holds 1 message(s); status queued
worker started -> same job 6133fe0a-b568-4024-8bb7-4d7d32ed0433 ready, thumbnail downloadable; staging object deleted
--- broker-down: Брокер недоступен: API принимает (outbox), dispatcher копит и публикует после восстановления.
rabbitmq stopped
upload -> 202 and /health/ready 200 without broker; outbox row pending for job 3e57742c-4cc4-48b0-9645-0e742fa323d0
rabbitmq started -> dispatcher published the pending row -> ready
2 passed, 0 failed
