chore(ci): disable upptime workflows post-GitHub-suspension (closes part of #2)

All 5 upptime-driven workflows (graphs / response-time / static-site /
summary / uptime) call api.github.com for releases lookup + issue
management + result commits. Post the 2026-05-06 GitHub org
suspension, no token in our org authenticates there anymore — every
scheduled run fails with HTTP 401 "Bad credentials".

Move the workflow files to .github/workflows-disabled/ so Gitea
Actions stops scheduling them. Adds a README explaining what
happened and pointing at #2 for the replacement plan
(Gitea-native uptime probe).

The history/ directory and .upptimerc.yml stay untouched — the
existing probe-list config is still useful as input to the
replacement; the historical JSON files are read-only data we may or
may not migrate forward.

Tracked: #2.

.github/workflows-disabled-post-suspension/README.md

@@ -1,20 +0,0 @@
-# Disabled upptime workflows
-
-These five workflows were the upptime-driven status page. They have been
-disabled because upptime fundamentally cannot run on Gitea Actions:
-
-- `uptime/uptime-monitor` action calls `api.github.com/repos/upptime/uptime-monitor/releases`
-  on every run to check its own version. This call:
-  - Returns `401 Bad credentials` because the GitHub `Molecule-AI` org
-    PAT was suspended on 2026-05-06.
-  - Cannot be papered over with the operator host's anonymous IP — also
-    rate-limited.
-  - Cannot be re-tokenized with a personal GitHub PAT (the original
-    bot-ring fingerprint that got us banned, per memory
-    feedback_github_botring_fingerprint).
-
-The replacement plan is tracked in `internal#TBD` (RFC).
-
-If you need a status page in the meantime: external services
-(StatusPage.io, BetterStack, healthchecks.io) sit outside the Molecule-AI
-infra and don't depend on GitHub. We picked one of those for the gap.

.github/workflows-disabled/README.md

@@ -0,0 +1,19 @@
+# Disabled upptime workflows
+
+These five workflows (`graphs.yml`, `response-time.yml`, `static-site.yml`,
+`summary.yml`, `uptime.yml`) are upptime-driven and call
+`api.github.com` for releases lookup, issue management, and result
+commits.
+
+Post the 2026-05-06 GitHub org suspension, no token in our org
+authenticates against api.github.com, so every scheduled run fails
+with HTTP 401 "Bad credentials". See molecule-ai-status#2 for full
+diagnosis + the replacement plan.
+
+Workflows here will not be re-enabled — they're moved to
+`workflows-disabled/` so the failed-run noise stops while the
+replacement (Gitea-native uptime probe) is built. Delete this
+directory after the replacement lands and the existing history is
+either migrated or marked archived.
+
+Tracked: molecule-ai-status#2

.github/workflows/ci.yml

@@ -1,36 +0,0 @@
-name: CI
-
-# Tiny no-op workflow so the dashboard doesn't display a stale red
-# badge from the disabled upptime workflows. The workflows that actually
-# probed our endpoints (uptime/response-time/graphs/summary/static-site)
-# were moved to .github/workflows-disabled-post-suspension/ in #5
-# because upptime cannot run on Gitea Actions post-2026-05-06 GitHub
-# org suspension. Replacement is tracked in internal#97.
-#
-# This noop fires on every push to main + once daily so the badge
-# accurately reflects "this repo is intentionally idle" instead of
-# "the last 5x/hour upptime cron failed forever ago."
-
-on:
-  push:
-    branches: [main]
-  schedule:
-    # Daily at 00:00 UTC so the badge stays green even on weeks with no
-    # commits. Cheap; just an echo.
-    - cron: "0 0 * * *"
-  workflow_dispatch: {}
-
-permissions:
-  contents: read
-
-jobs:
-  noop:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Repo intentionally idle
-        run: |
-          echo "molecule-ai-status is intentionally idle until the upptime"
-          echo "replacement lands per internal#97. The five upptime workflows"
-          echo "that used to live in .github/workflows/ have been moved to"
-          echo ".github/workflows-disabled-post-suspension/ — see that"
-          echo "directory's README.md for context."