obot.roadmap becomes the project's memory: hub-migration requirement, HTML design doc, and full site implementation.
Work completed
Scaffolded obot.roadmap with the gsm.roadmap-style requirement lifecycle and migrated the open P004 requirements as #1 (safety.viz), #2 (Safety Histogram pilot), and #3 (obot GitHub App).
Documented requirement-template enforcement in AGENTS.md (#5, merged in PR #6).
Drafted Requirement #7 — migrate the obot-claw hub into obot.roadmap as the project's memory — with the repo's first HTML design document (requirements/design/7_design.html, per the convention from obot-claw#59).
Jeremy resolved design decisions D1–D4 (all recommendations accepted): P006 keynote becomes a backlog requirement, diary continues per working session, all hub reports migrate (superseded ones flagged), dashboard refreshes daily.
Implemented the migration in PR #8: 32 hub diary entries migrated into diary/, ten-chapter framework report plus nine standalone reports into reports/ with provenance READMEs, static homepage, dashboard/roadmap/diary generators, and the deploy-site.yml Pages workflow.
The dashboard's sign-off gates and the roadmap's Status grouping need a ROADMAP_TOKEN repo secret (PAT with project read) — the default Actions token cannot read the user-level project. Both scripts degrade gracefully without it.
GitHub Pages must be enabled (build type: GitHub Actions) before the first deploy.
🙋 ToDo
@jwildfire: review PR #8 and 👍 #7 for design sign-off.
@jwildfire: add a ROADMAP_TOKEN secret and enable GitHub Pages (Actions build) if the automated attempt fails.