docs: note the SEO regeneration step for new pages

Record in PRE-LAUNCH-TODO.md that new pages still need ARTICLE_DATES + a
seo_inject.py --all --sitemap run (the commit hook covers News/homepage/bot
sync but not SEO), so it isn't forgotten.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/PRE-LAUNCH-TODO.md

@@ -35,6 +35,18 @@ placeholder inventory lives in `PRE-LAUNCH-CHECKLIST.md`; GA4 setup in
 - [ ] Periodically bump Font Awesome (currently 6.5.1, pinned + SRI) and regenerate its integrity hash.
 - [ ] Confirm the host takes docroot backups (source is already version-controlled in Gitea; form data in Google Sheets / MailerLite).
 
+## 🛠 Maintenance / build steps to remember
+
+- [ ] **After adding a brand-new page, run SEO.** The pre-commit hook
+      (`tools/git-hooks/pre-commit`, activate once with
+      `git config core.hooksPath tools/git-hooks`) auto-syncs the News hub,
+      homepage "Latest news", `/llms.txt` and `/links-for-bots/` on every commit —
+      but it does **not** run SEO. For a new page also:
+      1. add its date to `ARTICLE_DATES` in `tools/seo_inject.py`, then
+      2. run `python tools/seo_inject.py --all --sitemap` (SEO meta + canonical/hreflang + sitemap entry).
+      - Open decision: fold `seo_inject` into the hook or a deploy step so even this is hands-off
+        (kept out by default because it rewrites all ~225 pages).
+
 ## ✅ Done (for reference — already live/hardened)
 
 - Security headers (HSTS, enforcing CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy)