docs(plans): capture modern Web UI follow-ups

Author: Oba-One

.plans/active/public-website-design-implementation/eval.md

@@ -19,6 +19,10 @@
 - Browser proof verifies allowlisted live submissions render as public stewards and non-allowlisted live submissions render as public members.
 - Seeded-data proof verifies chapter, steward, member, and anonymous density nodes plus mycelial edges render together.
 - Visual proof compares the map against the HiFi reference at 375, 1024, and 1440 widths, including node treatments, filter legibility, thread density, and mobile readability.
+- Any modern CSS/Web UI primitive proposed after this plan update has a feature-readiness classification, reduced-motion path, and static fallback or `@supports`/feature-detection proof.
+- Any changed site shell, map, chip, card, focus, or form-control primitive includes a contrast or forced-colors spot check when color, translucency, shadow, or image-backed text carries meaning.
+- Text-scale meta is not enabled until large-text behavior is proven at 375, 1024, and 1440 widths.
+- Astro MPA View Transitions, CSS scroll spy, scroll-state header behavior, and `closedby="any"` dialog polish remain progressive enhancements and do not gate content access.
 - Email magic-link node updates are email-only, use hashed one-use tokens, expire after 30 minutes, and never expose owner email or token state in public responses.
 - The edit-token/update-request migration uses the next available migration number after the current highest migration and does not collide with operational content migrations.
 - New public `POST /map-nodes` submissions require email.
@@ -58,3 +62,4 @@
 - Website checks for selected-node update request, `/map/edit?token=...`, token removal from visible URL before analytics/outbound navigation, success/error states, mobile overflow, add-node dialog interaction, theme selection, placement fallback, live refresh, and public steward/member rendering.
 - Targeted stale-path scan for the former root V2 and research locations across README, root config, package scripts, and `.plans`.
 - Visual checks at 1440, 1024, and 375 for HiFi comparison, chapter/steward/member node treatments, anonymous density, mycelial edges, filter color comfort, non-color cues, accessible legend, edge-density behavior, connection clarity, live-mode copy, and mobile add-node flow.
+- Modern CSS/Web UI follow-up checks, when implemented later: text-scale screenshots, reduced-motion verification, unsupported-feature fallback proof, and focused route/browser checks for any scroll spy, View Transition, scroll-state, or dialog-light-dismiss changes.

.plans/active/public-website-design-implementation/plan.todo.md

@@ -135,3 +135,15 @@ The modern-CSS-standard initiative is otherwise complete and on `main`: the `DES
 
 - [ ] **Phase 5 — Remove Tailwind.** `@astrojs/tailwind` is unused (0 utilities, 0 `@apply`) but its integration auto-injects a preflight reset. Removing it blindly gives nav `<ul>`/`<ol>` (header, footer, breadcrumb) their default margins/indent and visibly shifts chrome. **Prerequisite:** add an explicit element reset (lists, headings, fieldset, figure) to the `gp-base` layer in `gp-tokens.css` to replace preflight, then remove `tailwind()` from `packages/website/astro.config.mjs`, delete `tailwind.config.js`, and drop `@astrojs/tailwind` + `tailwindcss` (+ `postcss`/`autoprefixer` if unused) from `packages/website/package.json`. Verify with `bun run ui:verify` **and** a visual pass at 375/1024/1440. Touches the shared `package.json`/lockfile.
 - [ ] **Phase 6 — Author-time stylelint guard.** Add `stylelint` + `stylelint-config-standard` + `postcss-html` (dev deps; shared `package.json`) with a house config: token-only colors, `var(--gp-font-*)` fonts, no pure white/black, no stray viewport `@media` (allowlist the documented chrome + type-scale exceptions), logical properties. Wire `bun run ui:check` scoped to changed files; keep advisory (no hook by default — use the `update-config` skill to opt into one later).
+
+## Modern Web UI Follow-Ups (progressive; keep behind current P0 map/design work)
+
+- [ ] Start from `reports/modern-web-ui-follow-up-2026-05-24.md`.
+- [ ] Audit root font-size and large-text behavior before adding `<meta name="text-scale" content="scale">`.
+- [ ] Audit `color-scheme`, `prefers-contrast`, and `forced-colors` behavior for the site shell, map controls/dialog, chips, cards, focus rings, and form controls before relying on translucent or color-only states.
+- [ ] Evaluate Astro MPA View Transitions with `@view-transition { navigation: auto; }` as progressive enhancement only, with reduced-motion fallback.
+- [ ] Identify long story, library, garden, or chapter surfaces where CSS scroll spy can improve section orientation.
+- [ ] Evaluate scroll-state header behavior only if it reduces visual noise without hiding navigation context.
+- [ ] Add `closedby="any"` to simple dialogs only when existing escape/click fallback behavior and focus behavior remain proven.
+- [ ] Review `packages/website/src/scripts/parallax.ts` against the current CSS-only `GpLayout.astro` background approach; remove or realign it only in a future implementation lane with browser proof.
+- [ ] Keep overscroll gestures, HTML-in-Canvas, CSS `@function`, CSS `if()`, shape APIs, and `fit-text` out of production scope.

.plans/active/public-website-design-implementation/spec.md

@@ -22,6 +22,7 @@ Build the next public Greenpill Network website experience in `packages/website`
 - Add controlled Live Onboarding Mode for workshops and demos so admin-enabled submissions can appear publicly in near real time.
 - Add email magic-link ownership for submitted map nodes so users can request edits without wallet auth or workspace login.
 - Keep visual acceptance proof tied to the high-fidelity artifacts at desktop, tablet, and mobile widths.
+- Track modern CSS/Web UI follow-ups inside this hub rather than creating a competing plan source.
 
 ## Constraints
 
@@ -53,6 +54,10 @@ Build the next public Greenpill Network website experience in `packages/website`
 - Raw magic-link tokens must never be logged or persisted; only hashes may be stored. The public edit page must clear the token from the visible URL before analytics, outbound links, or external navigation can run.
 - Directus/admin access must keep token rows, owner emails, IP/user-agent, and raw request metadata restricted to trusted/admin roles. Standard stewards should only see review-safe update request fields needed to approve or reject edits.
 - Directus/admin review should provide current-vs-proposed comparisons, explicit approve/reject transitions, reviewer metadata, and private notes.
+- Modern CSS/Web UI follow-ups must preserve the existing `DESIGN.md` standard: token-only styling, container-query-first layout, dynamic viewport units, reduced-motion behavior, and multi-width browser proof.
+- Preference-mode follow-ups must explicitly cover `color-scheme`, `prefers-contrast`, `forced-colors`, focus visibility, touch targets, and large-text behavior on map, shell, card, chip, and form-control surfaces.
+- Chromium-first features such as text-scale meta, CSS scroll spy, scroll-state queries, and `closedby="any"` must remain progressive until fallback behavior is proven.
+- Research-only APIs such as overscroll gestures, HTML-in-Canvas, CSS `@function`, CSS `if()`, shape APIs, and `fit-text` must not become production dependencies in this hub.
 
 ## Public Map Recovery Decisions