release: staging to main (2026-10-07), with the Toddle Enhancement Extension 0.9.0

[bryanfawcett]

Release of staging to main, together with the extension's 0.9.0 (owner, 2026-10-06: hold the learning site until 0.9.0 is released; 2026-10-07: 0.9.0 tested, pushed to the store and tagged). The branch is main plus staging's exact tree in one commit (git diff origin/staging is empty).

• ci: tag staging merges as patches and run the build on staging #64 ci: tag staging merges as patches and run the build on staging
• chore: the default branch is main #65 chore: the default branch is main
• docs(legal): every claim about the extension matches its code, for 0.8.2 and 0.8.4 #66 docs(legal): privacy on Zimbabwe's Act and the GDPR; every extension claim matches its code
• docs: the extension page and legal pages describe 0.9.0, with flags concealed, not hidden #67 docs: the extension page and legal pages describe 0.9.0, with flags concealed, not hidden
• feat: a public Releases page for the extension; the terms say who owns it #68 feat: a public Releases page for the extension; the terms say who owns it
• docs: the licence server's address is licenses.nyuchi.com #71 docs: the licence server's address is licenses.nyuchi.com
• docs: one account of 0.9.0 across the site #70 docs: one account of 0.9.0 across the site
• docs: 0.9.0's last changes: readable sizes, flag Markdown, a licence that follows your Chrome account, and the upgrade #72 docs: 0.9.0's last changes: readable sizes, flag Markdown, a licence that follows your Chrome account, and the upgrade
• ci: a release to main is tagged as the next minor #73 ci: a release to main is tagged as the next minor (this merge should be tagged v0.1.0)
• docs: release review fixes: the licence host per version, one legal date, the changelog cut to 0.1.0 #75 docs: release review fixes: the licence host per version, one legal date, the changelog cut to 0.1.0
• docs: second release review fixes: what 0.9.0 reads, versioned flag claims, fixed review history #76 docs: second release review fixes: what 0.9.0 reads, versioned flag claims, fixed review history

0.9.0 is in Chrome Web Store review (uploaded, STAGED_PUBLISH, PENDING_REVIEW), so its release entry still has no date and the pages call it the next version. Replaces the stale draft #69.

Review and verification are recorded in a comment below.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
learning	Ready	Preview	Oct 7, 2026 4:22am UTC

[bryanfawcett]

Merge-gate record (2026-10-07, release supervisor):

• Tree equals origin/staging exactly (git diff origin/staging empty) at 1b02dfa.
• /code-review pass 1: 1 medium, 3 low (llms.txt date; licence host per version; changelog contradictions; version numbering). Fixed in docs: release review fixes: the licence host per version, one legal date, the changelog cut to 0.1.0 #75 (itself reviewed to clean).
• Pass 2: 2 medium, 4 low (0.9.0's reads; review history tied to current; unversioned 'never hides'; student-privacy flags; 'once a day'; staging workflow guard). Fixed in docs: second release review fixes: what 0.9.0 reads, versioned flag claims, fixed review history #76 (reviewed to clean).
• Pass 3: clean.
• Local on the release tree: astro check 0 errors; npm test 97/97; CSP 5 inline scripts across 14 pages. Runtime check of the built site in headless Chromium (on docs: 0.9.0's last changes: readable sizes, flag Markdown, a licence that follows your Chrome account, and the upgrade #72): changed pages 200, #v0.9.0 visible, no page errors.
• CI green (17 checks).
• Chrome Web Store still shows 0.8.2 (0.9.0 uploaded, PENDING_REVIEW, staged), so the 0.9.0 entry keeps no date.

Merging without deleting the branch. main-version.yml should tag this merge v0.1.0.

🤖 Generated with Claude Code