Project Window: a plain-language view of the project

Goal

Pablo asked for a visual "window to the project" that both founders (and later anyone given access) can open without reading GitHub: status and progress, history and who did what, decisions waiting and made, which sectors have data and which don't, and the status of each data source, with a plain explanation next to the technical one, updating itself after every change (issue #3).

What changed

src/keel/window/: keel window build reads STATUS.md, the roadmap, the ADRs, the worklog, docs/context/ (team and glossary), the registry, git history and (with a token) GitHub pull requests, issues and CI runs, and writes site/index.html (one self-contained page) plus site/window.json. No new dependency; a small, escaped Markdown renderer is included.
The page: Overview (current phase, needs attention, key figures, coming up, latest activity, who's on what), Progress (timeline and every goal), Decisions, Data (six-step source journey, sectors, sector-by-emirate coverage, every source, portal reachability), Activity (filterable), Team and Glossary. Plain/Technical switch; light and dark; works at phone width.
.github/workflows/window.yml: rebuilds on every push to main, after CI, on pull request and issue events and every morning; publishes to Cloudflare Pages when WINDOW_PUBLISH is set. make window builds and opens it locally.
Plain words at the source: an "In plain words" line in ADR-0001 to ADR-0010 and the ADR template; summary: in the worklog template; progress conventions at the top of the roadmap, with two M0 goals marked in progress (facts from STATUS.md and the 2026-09-28 worklog) and a new M0 goal for putting the window online; twelve plain definitions (GitHub words, roadmap, Project Window) added to the glossary; docs/context/team.yaml maps GitHub usernames to people.
Process: /end-session and /new-adr ask for the plain summaries; new /log-update skill for things that happen outside the code; AGENTS.md and CLAUDE.md updated to match.
Docs: ADR-0011 (Proposed), docs/runbooks/project-window.md, docs/setup/project-window-hosting.md (plain-language Cloudflare Pages + Access setup).
tests/test_window.py (13 tests). make check: 40 tests pass, registry valid (the known personal-data warning on dha_health_professionals only).

Decisions

ADR-0011 (Proposed): generate the window from the repository; host it privately on Cloudflare Pages behind Cloudflare Access. GitHub Pages was rejected because a site from a private repository on our Team plan is public.

Open questions and blockers

Hosting needs a Cloudflare account, two repository secrets and an Access policy (docs/setup/project-window-hosting.md). Until then, make window or a Claude artifact.
Fede's GitHub username is not in docs/context/team.yaml yet (same gap as CODEOWNERS).
Portal reachability on the page is read from the free-text notes in registry/portals.yaml; structured fields would be sturdier (a core change, for both founders to decide).
Snapshot history per source appears once shared storage exists (M0-4); the workflow already passes the storage settings when KEEL_STORAGE_URL is set.

State for the next person

Branch pushed: yes
make check: passing
Data touched: none
Next step: review and merge the pull request, then follow docs/setup/project-window-hosting.md to put the window online.