Back to dashboard
public checkssix-hour monitorprogress gatesblocked

Automation status

This page shows what runs automatically before the site trusts a result. A packet can be public immediately, but it cannot change progress or verified leaderboard credit until the reproduction gate passes.

Overall automation
blocked
Stages
6
Quality gates
6
Schedule
every 6h
Workflow
GitHub

Generated 6/4/2026, 10:43:10 AM

m23:verify
Local verifier

Builds and runs the full contribution flow before deployment.

6 hours
Recurring monitor

Checks the live site, APIs, notebook path, and leaderboard.

reproduced
Progress gate

Pending and schema-only records cannot move the progress bar.

Actions
Workflow file

.github/workflows/m23-automation.yml

Automated checks

What runs without asking users to install complex software.

Before deployment and before accepting major changesok

Local full verification

Runs lint, production build, smoke tests, and desktop/mobile browser checks against an isolated local site.

npm run m23:verify

Verifies

  • The dashboard, work pages, notebook guide, upload forms, verification forms, and leaderboard render.
  • Bad uploads and secret-like text are rejected before they enter the public record.
  • Pending packets do not change progress until a reproduction record is attached.

Visible evidence

  • /m23
  • /m23/work/m23-replay-0006
  • /m23/leaderboard
Inside local verification and CIok

Contribution-flow smoke test

Creates review, artifact, result, and verification records through public APIs and checks their progress effects.

npm run m23:smoke

Verifies

  • ChatGPT Pro reviews earn review credit only.
  • Schema-only verification stays pending.
  • Reproduced same-script or stronger verification advances completed units and leaderboard credit.

Visible evidence

  • /api/m23/progress
  • /api/m23/verifications
Inside local verification, CI, and optional production checksok

Browser UI regression

Opens the site in a real browser engine at desktop and mobile widths and checks text, links, forms, and overflow.

npm run m23:browser

Verifies

  • Visitors can start from the dashboard and reach ChatGPT Pro, notebook, cloud, and local-worker paths.
  • The verification form can be submitted from the packet detail page.
  • Mobile pages do not horizontally overflow.

Visible evidence

  • /m23/automation
  • /m23/notebook/m23-replay-0006
On demand and every six hours in GitHub Actionswarning

Production monitor

Checks the live public site, APIs, notebook endpoint, leaderboard, storage status, and canonical domain.

npm run m23:prod

Verifies

  • The public www site returns HTTP 200.
  • The progress API exposes route, queue, leaderboard, storage, and readiness data.
  • Known account-owner blockers are warnings until strict mode is enabled.

Visible evidence

  • /api/m23/readiness
  • /api/m23/automation

Finish durable storage and apex DNS so production monitor can become fully green.

Enable after account-owner DNS and storage setupblocked

Strict production gate

Turns durable storage and apex HTTPS redirect from warnings into hard failures.

npm run m23:prod:strict

Verifies

  • Production contributions persist after redeploys.
  • https://m23isgalois.com redirects safely to https://www.m23isgalois.com.

Visible evidence

  • https://www.m23isgalois.com
  • https://m23isgalois.com

Add or refresh the Vercel TXT verification records in Porkbun, then refresh Vercel Domains until apex HTTPS redirects to www.

Push, pull request, manual dispatch, and every six hoursok

GitHub Actions schedule

Runs the local verifier, production monitor, and production browser check continuously from the repository.

.github/workflows/m23-automation.yml

Verifies

  • A broken page, API, upload flow, or mobile layout fails before it silently ships.
  • Production drift is noticed even when nobody is actively editing the site.

Visible evidence

  • .github/workflows/m23-automation.yml

Verification gates

What must pass before progress changes.

Task visible before compute

ok

Every worker and notebook path shows the public task card, safety rules, hashes, and scope caveat before work starts.

No secret uploads

ok

Artifacts, result packets, ChatGPT reviews, and verification notes reject secret-like strings.

Pending does not count

ok

A submitted packet is public but does not change progress or leaderboard verified units until reproduced.

Schema-only does not count

ok

Schema-valid checks are useful triage, but completed units require reproduced_same_script or stronger verification.

Durable production record

blocked

Production must use Vercel Blob or Postgres before real community contributions should be treated as durable.

Apex domain ready

blocked

The apex domain should verify and redirect to www so visitors have one safe canonical URL.