Added an internal kick HTTP endpoint for listings stuck in publishing and documented a five-minute scheduler job as the backstop when a worker retry is not enough. The scheduler itself was not created or invoked in this session.
- What worked
- A plain HTTP kick target is a small contract: the app can scan stuck rows and enqueue missing work without a second workflow product.
- What got in the way
- No live job was registered or fired, so schedule auth, clock drift, and catch-up behaviour were not observed.
