Roadmap review and teaching progress page

What happened

• Reviewed all 16 phase files, plan.md, docs/roadmap.md and docs/tech-stack.md. Report: plans/reports/review-261013-1855-roadmap-learning-flow-and-gaps.md. It lists five defects (RV1–RV5), ten stale text spots (RV6), two learning-order proposals (RV7, RV8) and one harness gap, the missing eval loop (RV9).
• Built plans/260922-0123-hango-agent-harness-roadmap/plan.html. It covers what a harness is, the agent loop, durable runs, middleware, observability, tenancy, the architecture by phase, the roadmap ladder and the review findings.
• build_plan_html.go (//go:build ignore, stdlib only) generates the page from plan-template.html, the phase files, the newest review report and the four compiled diagrams in diagrams/.
• Progress comes from the 186 success-criteria checkboxes, using the same rule as ak plan parse.
• The delivery checklist in docs/roadmap.md §5 now includes ticking the criteria and regenerating plan.html.
• Published a private copy: hango harness plan.

Problems hit

• The phase 1 learning doc was missed because a parenthetical between backticked paths stopped the path parser. Fixed leadPathRe to skip (...) notes and diffed the extracted paths before and after the change.
• The diagram compiler silently produced nothing when called through the symlinked skill path. Calling it through realpath works.
• Headless Chrome on macOS clamps the window width to 500px and follows the OS theme.
  • Phone checks now run inside a 375px iframe that posts its layout report to the parent page.
  • The theme is forced with --blink-settings=preferredColorScheme.
• Screenshots taken after scrollTo came out blank, so sections are offset with a negative margin-top instead.
• At 375px and 768px, wide tables scrolled and hid columns (the anatomy status column, the hook descriptions).
  • At 700px and below, tables with three or more columns now stack into labelled cards.
  • table.wide min-width is cut to 640px.
• Artifact viewers set data-theme on the root element.
  • The dark tokens are now guarded by :root:not([data-theme="light"]), with a copy under :root[data-theme="dark"].
  • Diagram theme sync follows the root attribute.

Decisions

• The phase checkboxes are the only source of progress. There is no separate status file.
• The page needs no network access. External URLs are outbound links only.
• The architecture view shows v1 until a phase is done. After that it starts at the last phase of the unbroken run of done phases.

Next steps

• User decides which of RV1–RV9 to apply (RV1: O1 or O2; RV9: O1, O2 or O3) and whether to build in the order 1 → 3 → 2 → 4 → 5.
• Then /ak:cook phase 1.
• After each phase:
  • Tick the criteria and run go run build_plan_html.go.
  • If boxes were ticked by hand, run ak plan reindex --apply.
  • Republish the shared copy.

Historical work record — not durable authority. Prefer docs/specs/ADRs for current decisions.