E7 — Production Readiness (ALO-126)#108
Conversation
…LO-126) Add the operability docs and prod-deploy gate that close out E7 production readiness. Most of the underlying work (observability, rate limiting, CSRF, CSP, signed R2 URLs, DMCA, moderation, e2e, k6, D1 backup) already shipped in earlier PRs — this consolidates the operator-facing artifacts: * docs/runbooks/on-call.md — sev ladder, first-five-minutes, rollback, common playbooks, comms. * docs/runbooks/cost-monitoring.md — alert thresholds per CF line item, abuse triage, cost discipline rules. * docs/runbooks/production-readiness.md — single checklist mapping every E7 requirement to its artifact. * deploy-prod.yml — staging-smoke job probes /api/health on staging and blocks the prod job until it returns status=ok. STAGING_HEALTH_URL is overridable via repo variable. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
…-126) Two accuracy fixes on the E7 runbooks so they match the actual code: * on-call.md: the rate-limit DO binding is `RATE_LIMITER`, not `RATE_LIMIT_DO` — `wrangler.toml` defines it under `[[durable_objects.bindings]]` with `name = "RATE_LIMITER"`. * production-readiness.md: clarify that worker Sentry is wired via `Sentry.withSentry(...)` in `src/workers/index.ts`, so an operator can trace the integration end-to-end without grepping. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
Closes ALO-126.
Most of the E7 scope (observability, DO rate limiter, CSRF/CSP, signed R2 URLs, DMCA, moderation queue, lifecycle state machine, Playwright e2e, k6 load, D1 backup runbook, AI Gateway guard) already shipped across earlier PRs. This PR consolidates the remaining operator-facing artifacts and the prod release gate.
Summary
docs/runbooks/on-call.md) — sev ladder, first-five-minutes, rollback steps, playbooks for deploy regressions, DB failures, stuck uploads, rate-limiter overreach, DMCA, cost spikes.docs/runbooks/cost-monitoring.md) — per-line-item thresholds (Workers, Logs, R2, D1, Stream, AI Gateway), abuse triage queries, cost-discipline rules (no model defaults in code, bounded loops, log retention).docs/runbooks/production-readiness.md) — single index mapping every E7 requirement to the artifact that satisfies it..github/workflows/deploy-prod.yml) — newstaging-smokejob probes/api/healthon staging (URL overridable viavars.STAGING_HEALTH_URL) and blocks the prod job unlessstatus=ok. Realises the "staging mirrors prod" Done-when criterion at the workflow level.Test plan
npm run lint— 0 warnings, AI Gateway guard 0 findingsnpm test -- --run— 491/491 passing across 44 filesstaging-smokejob runs and gates correctly (deferred — needs a working staging deployment, which is owned outside this PR)🤖 Generated with Claude Code