// Monitoring workflow for architect: Cloudflare Worker checks, task updates, and Slack escalation.
| name | architect-monitoring |
| description | Monitoring workflow for architect: Cloudflare Worker checks, task updates, and Slack escalation. |
Use this when the task is OS / Cloudflare app health monitoring.
If a source is unavailable, continue with what you have and note the gap.
Use env vars first; if credentials are missing: doppler run --config <env> -- <command>.
For broad or unclear impact, post in #error-pulse with deep links (PostHog issue, Cloudflare Worker logs query, GitHub permalink into apps/os/…).
Do not use Fly machine SSH, pidnap process logs, or sandbox container debugging — that legacy machine stack was removed from the repo.
Create a new Cloudflare app in this repo with the expected package scripts, Doppler shape, and CI workflow wiring.
Query and analyze Cloudflare Workers traces through the general Cloudflare API MCP server. Use when diagnosing Workers traces, distributed tracing spans, observability events, subrequest chains, or when an agent needs Cloudflare trace data programmatically.
Debug MCP servers with the official MCP Inspector UI and CLI. Use when an MCP server will not connect, auth fails, tools/resources/prompts are missing, or a tool call needs to be reproduced outside Codex/Claude.
Drizzle ORM database migration workflow for packages that still use Drizzle (agents, example). Do NOT use for apps/os — that app uses sqlfu/D1.
Debug failures in the Cloudflare OS worker using the Cloudflare MCP server. Use when diagnosing 500s, missing logs, or request-level regressions in production or preview.
PostHog alert responder workflow with required Slack deep-links and escalation rules.