From 40750a5ad8a40e06930a9151b59fcb7597240e21 Mon Sep 17 00:00:00 2001
From: Minsu Lee <minsu.lee@pleaseai.dev>
Date: Wed, 8 Jul 2026 21:22:58 +0900
Subject: [PATCH] chore(demo): monitor GitHub/Cloudflare/npm via the statuspage
 adapter
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The hosted demo pinged api.github.com / cloudflare.com / npm as plain http
checks. GitHub, Cloudflare and npm all publish an Atlassian Statuspage, so mirror
their own published verdict via check: statuspage instead — a better showcase of
the adapter with real component-level data. Keep one plain http check (1.1.1.1)
for contrast.
---
 status.config.yml | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/status.config.yml b/status.config.yml
index a117743..80df13f 100644
--- a/status.config.yml
+++ b/status.config.yml
@@ -6,21 +6,21 @@
 name: statusbeam Demo
 
 sites:
-  - name: GitHub API
-    url: https://api.github.com
-    check: http
-    expectedStatusCodes: [200]
-    maxResponseTime: 2000
+  # Statuspage adapter — mirror each vendor's own published verdict (their
+  # /api/v2/summary.json) instead of a naive reachability ping. GitHub, Cloudflare
+  # and npm all publish an Atlassian Statuspage. See docs/adapters/statuspage.md.
+  - name: GitHub
+    url: https://www.githubstatus.com
+    check: statuspage
   - name: Cloudflare
-    url: https://www.cloudflare.com
-    check: http
-    expectedStatusCodes: [200]
-    maxResponseTime: 2000
-  - name: npm Registry
-    url: https://registry.npmjs.org
-    check: http
-    expectedStatusCodes: [200]
-    maxResponseTime: 3000
+    url: https://www.cloudflarestatus.com
+    check: statuspage
+  - name: npm
+    url: https://status.npmjs.org
+    check: statuspage
+    component: Package installation
+
+  # One plain http check for contrast — a direct reachability probe.
   - name: Cloudflare DNS
     url: https://1.1.1.1
     check: http