heymegabyte/agent-skills / 08-deploy-and-runtime-verification
deploy-and-runtime-verification
UnverifiedMANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.6 KB |
| backup-and-disaster-recovery.md | markdown | 2.7 KB |
| changelog-and-releases.md | markdown | 5.3 KB |
| ci-cd-pipeline.md | markdown | 7.1 KB |
| critical-css.md | markdown | 4.7 KB |
| font-subsetting.md | markdown | 4.5 KB |
| gh-fix-ci.md | markdown | 3.5 KB |
| launch-day-sequence.md | markdown | 5.2 KB |
| pipeline-health-check.md | markdown | 4.5 KB |
| r2-lifecycle.md | markdown | 5.6 KB |
| service-worker.md | markdown | 9.7 KB |
| uptime-and-health.md | markdown | 6.5 KB |
uptime-and-health.md
View on GitHub---
name: "Uptime and Health"
version: "1.2.0"
updated: "2026-04-23"
description: "Health endpoints on every Worker (/health + /health/deep), external monitoring (UptimeRobot, Better Stack), /status page, cron self-check with Resend alert escalation."
---
# Uptime and Health
## Health Endpoint (EVERY Worker)
```typescript
app.get('/health', (c) => {
return c.json({
status: 'ok',
version: c.env.VERSION || 'unknown',
timestamp: new Date().toISOString(),
region: c.req.header('cf-ray')?.split('-')[1] || 'unknown',
});
});
// Deep health check (optional — checks dependencies)
app.get('/health/deep', async (c) => {
const checks: Record<string, string> = {};
// D1
try {
await c.env.DB.prepare('SELECT 1').first();
checks.d1 = 'ok';
} catch { checks.d1 = 'error'; }
// KV
try {
await c.env.KV.get('__health');
checks.kv = 'ok';
} catch { checks.kv = 'error'; }
// R2
try {
await c.env.R2.head('__health');
checks.r2 = 'ok';
} catch { checks.r2 = 'ok'; } // head returns null for missing, not error
const allOk = Object.values(checks).every(v => v === 'ok');
return c.json({ status: allOk ? 'ok' : 'degraded', checks }, allOk ? 200 : 503);
});
```
## External Monitoring (Let Others Handle It)
### UptimeRobot (Free — 50 monitors)
- Monitor — `https://domain.com/health`
- Interval — 5 minutes
- Alert — email to brian@megabyte.space
### Better Stack (Free tier)
Better UI, incident management, status pages.
- Monitor — `https://domain.com/health`
- Status page — auto-generated
### Cloudflare Health Checks (Built-in)
If using Cloudflare Load Balancing, health checks are built in.
## Status Page (Optional)
```typescript
app.get('/status', async (c) => {
const health = await fetch(`https://${c.env.DOMAIN}/health/deep`).then(r => r.json());
return c.html(renderStatusPage(health));
});
```
Simple status page showing:
- Overall status (operational / degraded / down)
- Individual service checks (D1, KV, R2)
- Last checked timestamp
- Uptime percentage (from KV counter)
## Cron Self-Check (Optional)
```typescript
// wrangler.toml: [triggers] crons = ["*/5 * * * *"]
export default {
async scheduled(event, env, ctx) {
const res = await fetch(`https://${env.DOMAIN}/health`);
if (!res.ok) {
// Alert via Resend
await new Resend(env.RESEND_API_KEY).emails.send({
from: 'Monitor <alerts@megabyte.space>',
to: ['brian@megabyte.space'],
subject: `⚠️ ${env.DOMAIN} is down`,
html: `Health check failed with status ${res.status}`,
});
}
},
};
```
## MCP Tools Available
### Coolify MCP (`mcp__coolify__*`) — for self-hosted service health
- **`diagnose_app`** — diagnose a Coolify-hosted app (Postiz, Listmonk, PostHog, etc.)
- **`diagnose_server`** — check overall server health (CPU, memory, disk)
- **`get_infrastructure_overview`** — full infrastructure summary — all apps, DBs, services
- **`application_logs`** — pull recent logs for a specific application
- **`find_issues`** — auto-detect issues across all services
- **`validate_server`** — validate server configuration and connectivity
- **`list_applications`** — list all running applications with status
- **`control`** — start / stop / restart any Coolify service
### Cloudflare MCP (`mcp__claude_ai_Cloudflare_Developer_Platform__*`)
- **`workers_list`** — list all Workers to verify they're deployed
- **`workers_get_worker`** — check a specific Worker's status
### Playwright MCP (`mcp__playwright__*`) — for visual health verification
- **`browser_navigate`** — navigate to `/health` or `/status` endpoint
- **`browser_take_screenshot`** — screenshot the status page for visual verification
## Health Endpoint Schema (Strict)
Every Worker MUST return this exact JSON shape from `/health`:
```typescript
interface HealthResponse {
status: 'ok' | 'degraded' | 'error';
version: string; // semver from wrangler.toml or env
timestamp: string; // ISO 8601
region: string; // Cloudflare colo code from cf-ray header
uptime?: number; // seconds since last restart (optional)
}
interface DeepHealthResponse extends HealthResponse {
checks: Record<string, 'ok' | 'error' | 'timeout'>;
// Each key is a dependency: 'd1', 'kv', 'r2', 'stripe', 'postiz', etc.
}
```
### Rules
- `/health` returns 200 for `ok`, 503 for `degraded` or `error`
- Response time must be <500ms (no heavy queries in shallow health)
- `/health/deep` may take up to 5s (checks external dependencies)
- Never expose secrets, internal IPs, or stack traces in health responses
## Monitoring Integration Patterns
### Pattern 1: Coolify + Cloudflare Workers (hybrid)
```
Coolify services (Postiz, Listmonk, PostHog)
→ mcp__coolify__diagnose_app per service
→ mcp__coolify__find_issues for cross-service problems
Cloudflare Workers (site, API)
→ fetch /health endpoint directly
→ mcp__claude_ai_Cloudflare_Developer_Platform__workers_get_worker for deploy status
```
### Pattern 2: Cron self-check with escalation
```
Every 5 min: Worker cron hits /health
→ OK: log to KV (increment uptime counter)
→ FAIL: send Resend alert + log to KV
→ 3 consecutive FAILs: escalate (post to Slack via mcp__claude_ai_Slack__slack_send_message)
```
## Computer Use Integration
Use `mcp__computer-use__*` for visual verification of monitoring dashboards:
1. **Better Stack dashboard** — screenshot the status page to verify all monitors show green
2. **UptimeRobot dashboard** — visual check that no monitors are in alert state
3. **Coolify dashboard** — screenshot `https://coolify.megabyte.space` to see all service health at a glance
Best used during: incident investigation, post-deploy verification, weekly health audits.
## Acceptance Criteria
1. `/health` returns 200 with valid JSON — `curl /health` returns `{ status: 'ok', version, timestamp, region }`
2. `/health` responds in <500ms — `curl -w '%{time_total}' /health` <0.5
3. `/health/deep` checks all dependencies — response `checks` object has keys for every bound resource (D1, KV, R2)
4. 503 returned when any dependency is down — kill a dependency, confirm status flips to `degraded` and HTTP 503
5. Cron self-check fires every 5 minutes — check KV uptime counter increments every 5 min
6. Alert email sent on failure — simulate failure, confirm Resend email arrives within 5 minutes
7. External monitor configured — UptimeRobot or Better Stack has an active monitor for `/health`
8. Status page renders correctly — Playwright screenshot of `/status` shows current health, no errors
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |