Live reachability checks + cold-stranger funnel health. Refreshes on page load. If anything below is red, a fresh agent / user can't complete a launch right now.
Loading…
If this is red, the install snippets on the homepage are broken for every new user. Customer-impact: every agent install page tells the runtime to talk to chieflab.io/api/mcp; if it serves HTML or 405s, the agent has nowhere to call.
Bypasses the Cloudflare Pages proxy. If the brand surface above is red but this is green, the proxy bundle regressed — see /trust.
Ten primary tools — one per public operator, plus chieflab_help, chieflab_get_users_after_build, and chieflab_signup_workspace — must all be visible to an unauthenticated tools/list. If any are missing, agents discover an incomplete surface.
The MCP server must respond to initialize with serverInfo.name and the negotiated protocolVersion. (The earlier experimental.progress capability check was removed in May 2026 — the official MCP SDK rejects unknown experimental capabilities, so we stopped advertising it.)
Runs on every deploy via scripts/cold-stranger-smoke.mjs. Creates a fresh workspace key, calls chieflab_launch_product with no connectors, verifies a stranger sees paste-ready copy + signed reviewUrl + funnel events. Red here = something a fresh user would hit in their first 60 seconds.
The grid above runs four live checks against the production surface every time you load this page. The "Last cold-stranger smoke" tile reads the result file written by scripts/cold-stranger-smoke.mjs, which runs after every npm run lab:deploy:prod (see spec/v0.1 §10 conformance).
Cold-stranger gate is blocking — deploys that break the cold path don't promote. Set COLD_STRANGER_SKIP=1 only for docs-only deploys.