release: promote stabilized quick scan flow

.env.example

@@ -52,19 +52,6 @@ TURNSTILE_SECRET_KEY=
 TURSO_DATABASE_URL=
 TURSO_AUTH_TOKEN=
 
-# ── Durable public-history scans (required for high-volume accounts) ───────
-# Turso persists every cursor and final snapshot. The existing Vercel deployment
-# drains this internal queue through /api/internal/public-scan every five minutes;
-# it does not require a third-party queue service or separate queue credentials.
-# Vercel Hobby permits only daily Cron jobs, so this configured cadence requires
-# a plan that supports sub-daily Cron execution.
-# Vercel Cron sends `Authorization: Bearer $CRON_SECRET`. Never expose it to
-# browsers or the CLI.
-CRON_SECRET=
-# Local-only manual worker test header. Not accepted in production; use this to
-# call the internal route without a Vercel Cron delivery.
-PUBLIC_SCAN_WORKER_SECRET=
-
 # ── Admin endpoints (optional) ────────────────────────────────────────────
 # Secret for the profile backfill endpoint (POST /api/admin/backfill-profiles
 # with header `x-admin-secret`). No default → the endpoint is inert until set.

.github/workflows/ci.yml

@@ -27,7 +27,6 @@ jobs:
       TURSO_AUTH_TOKEN: ""
       UPSTASH_REDIS_REST_URL: ""
       UPSTASH_REDIS_REST_TOKEN: ""
-      CRON_SECRET: ""
     steps:
       - name: Check out full history
         uses: actions/checkout@v4

README.md

@@ -204,11 +204,10 @@ TURSO_DATABASE_URL=file:./local.db
 1. Push to GitHub, import in Vercel.
 2. Configure environment variables (as above). `UPSTASH_*` can be provisioned in one click via Vercel's Upstash integration.
 3. Grab a Cloudflare Turnstile site/secret key pair; set `NEXT_PUBLIC_TURNSTILE_SITE_KEY` + `TURNSTILE_SECRET_KEY`.
-4. (Optional) Turso: `TURSO_DATABASE_URL` + `TURSO_AUTH_TOKEN` to enable the leaderboard, archived reports, profile comments/reactions, and resumable public-history scans.
-5. For resumable public-history scans in Vercel, set `CRON_SECRET`. The included `vercel.json` invokes the authenticated internal worker every five minutes; Turso is the durable queue and no additional queue SaaS is required. This cadence requires a Vercel plan that permits sub-daily Cron jobs; Vercel Hobby deployments reject the five-minute schedule at deployment time.
-6. (Optional) GitHub OAuth: `AUTH_GITHUB_ID` + `AUTH_GITHUB_SECRET` + `AUTH_SECRET` to enable signed-in comments/reactions.
-7. Set both `NEXT_PUBLIC_SITE_URL` and `PUBLIC_SITE_URL` to the same HTTPS origin. Vercel Production rejects a missing, local, HTTP, malformed, or mismatched value during the build so metadata, sitemap, API profile URLs, cards, and LLM attribution cannot drift.
-8. Deploy.
+4. (Optional) Turso: `TURSO_DATABASE_URL` + `TURSO_AUTH_TOKEN` to enable the leaderboard, archived reports, profile comments/reactions, and persisted quick-scan profiles.
+5. (Optional) GitHub OAuth: `AUTH_GITHUB_ID` + `AUTH_GITHUB_SECRET` + `AUTH_SECRET` to enable signed-in comments/reactions.
+6. Set both `NEXT_PUBLIC_SITE_URL` and `PUBLIC_SITE_URL` to the same HTTPS origin. Vercel Production rejects a missing, local, HTTP, malformed, or mismatched value during the build so metadata, sitemap, API profile URLs, cards, and LLM attribution cannot drift.
+7. Deploy the web application.
 
 ## Bring your own model / API key
 

config/release-versions.json

@@ -15,7 +15,7 @@
     "trackingIssue": null
   },
   "compatibility": {
-    "publicScoreReadOrder": ["v9", "v8"],
+    "publicScoreReadOrder": ["v9"],
     "roastReplay": [
       {
         "score": "v9",