Launch React on GitHub Pages and document maintainer handoff

[advaitmb]

The React site is live at https://behavioral-data.github.io/ from master. Remaining work is the human handoff; PR #35 updates the runbook. Updated September 10, 2026.

• Complete the approved production switch to GitHub Actions and deploy React.
• Validate clean builds and verify representative production pages, PDFs, assets, metadata, and the custom 404.
• Record launch details, rollback revision, and deployment/recovery procedures.
• Name primary maintainer: advaitmb.
• Retain the working manual deployment process; automatic deployment has not been enabled.
• Record the maintainer’s deferral of IdioFid signup verification in Complete browser, accessibility, route, and signup checks #26; no successful submission is claimed.
• Rehearse a content edit and revert in an isolated clean checkout: update rendered, original bytes restored, rebuilt export passed, and production unchanged.
• Name a backup maintainer and have them complete a content update, preview/check, and revert/redeploy exercise.

Known-good pre-migration revision: d6a7b92. Use reviewed revert commits for normal content rollback; do not rewrite production history. An agent rehearsal cannot stand in for another maintainer completing the handoff.

Evidence: runbook, issue status.

[advaitmb]

Launch update — September 9, 2026\n\nThe React site is live at https://behavioral-data.github.io/ from master commit 655d927. GitHub Pages now uses the Actions workflow; the first deployment succeeded in run https://github.com/behavioral-data/behavioral-data.github.io/actions/runs/34403337235.\n\nProduction checks passed for the home, team, publications, a labeled preprint detail, IdioFid, legacy allnews.html and /vacancies/ routes, plus a representative PDF, logo, robots.txt, sitemap.xml, and custom 404. The known-good pre-migration revision is d6a7b92 and the prior Pages mode was the legacy publisher on master at /.\n\nPR #32 records the launch/rollback procedure and fixes metadata/accessibility findings. Remaining before this issue is complete: name a primary and backup maintainer, perform the separately authorized IdioFid test signup, and decide whether deployments should remain manual or run after approved merges.