Check bot readiness before deploying the dashboard #4

Merged

chrono merged 1 commit from fix/deployment-readiness into main 2026-10-15 17:28:28 -04:00

Conversation 0 Commits 1 Files changed 10 +154 -9

chrono commented 2026-10-15 17:26:57 -04:00

Owner

• Copy link
• Copy Markdown

Summary

The deployment probe mistakes the private dashboard's 401 response for an unhealthy bot. Add /api/health, returning only readiness with HTTP 200 or 503, based on Discord connectivity and every joined server's initialized context. Disabled activity tracking remains healthy. Keep dashboard authorization unchanged and check anonymous policy denial at the current policy.get route.

checks pass → bot deployment passes readiness → dashboard deployment

Evidence

• Before: Osiris run 117 failed with Bot/API health check failed; production /api/status returned 401. New readiness tests failed before implementation.
• After: 133 Bun tests, 16 Python tests, and typecheck/lint/format/boundary checks pass locally.
• The administrator installed the updated receiver on Osiris; its checksum and root ownership/mode were verified.

Merge Danger

Door: two-way

Older releases lack /api/health and cannot pass the updated receiver's readiness probe, including rollback verification. The updated receiver is already installed on Osiris.

Blast Radius: deployment

Bot readiness requires Discord connectivity and an initialized, available context for every joined server. Failed bot deployments now skip Cloudflare deployment.

## Summary The deployment probe mistakes the private dashboard's 401 response for an unhealthy bot. Add `/api/health`, returning only readiness with HTTP 200 or 503, based on Discord connectivity and every joined server's initialized context. Disabled activity tracking remains healthy. Keep dashboard authorization unchanged and check anonymous policy denial at the current `policy.get` route. ```text checks pass → bot deployment passes readiness → dashboard deployment ``` ## Evidence - **Before:** Osiris run 117 failed with `Bot/API health check failed`; production `/api/status` returned 401. New readiness tests failed before implementation. - **After:** 133 Bun tests, 16 Python tests, and typecheck/lint/format/boundary checks pass locally. - The administrator installed the updated receiver on Osiris; its checksum and root ownership/mode were verified. ## Merge Danger **Door:** two-way Older releases lack `/api/health` and cannot pass the updated receiver's readiness probe, including rollback verification. The updated receiver is already installed on Osiris. **Blast Radius:** deployment Bot readiness requires Discord connectivity and an initialized, available context for every joined server. Failed bot deployments now skip Cloudflare deployment.

chrono added 1 commit 2026-10-15 17:26:57 -04:00

Check bot readiness before deploying the dashboard f693be154d

chrono merged commit f693be154d into main 2026-10-15 17:28:28 -04:00

chrono deleted branch fix/deployment-readiness 2026-10-15 17:28:28 -04:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

chrono/guildmaster!4

No description provided.