#3993 Docs: run-workflows-on-a-schedule tells readers to curl /health for queue state, which no longer lists schedules

swamp-club#3842 turns the unauthenticated GET / and GET /health routes on swamp serve into a liveness check in every auth mode: they now answer only status ok and version 1, with no schedule or webhook inventory.

content/manual/how-to/run-workflows-on-a-schedule.md (around line 93) says each schedule reports its queue state on the server's /health endpoint and shows a curl of /health. After #3842 ships that returns no schedules.

Suggested update: point readers at the serve dashboard for schedule and webhook queue state (queued, oldestQueuedAt, lastQueueDelayMs; active per webhook route), or at GET /api/v1/health, which needs a bearer token unless serve runs with auth mode none and shows each token only the workflows it may read. Keep /health described as a liveness probe, as the Kubernetes guide already does.