hub-tailwind-v4

IN BUILD

"I want to make sure we're leveraging MVDS as we build this experiment if there are any ui implications." "MVDS should handle all the breakpoints, not just s and l. if this repo is defaulting to just two I want to fix that in a future effort." — Katy, 2026-07-15 (session, verbatim). Same day, presented with the spike result (MVDS ships Tailwind v4 source only, no compiled CSS), Katy selected: **"Upgrade hub to Tailwind v4"** over MVDS shipping compiled CSS or a page-scoped side-build.

STAGES

  1. proposal07-15
  2. requirements07-15
  3. design07-15 ↻ 07-15predates the Figma as-is + proposed pair
  4. tasks07-15
  5. build—
  6. archived—

CAPABILITY

  • hub-build-pipeline3 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ○1.1Hub looks unchanged on Tailwind v4 — home, experiment detail, and navigation render identically to production (or with founder-approved deltas)not stated
  • ○1.2MVDS components render on the dev route — Button, Badge, Card, Section styled by MVDS tokens in the hub's dark context (hub pins `.dark` on `<html>`; light unreachable)not stated
  • ○1.3CI installs without registry credentials — clean install succeeds with no GitHub Packages token or scoped-registry config anywherenot stated

WHAT HAPPENED

  1. ↺ BACK TO DESIGN

    proposal and specs and design and tasks landed

    2026-07-15 · 2 pull requests
    • #288feat(build): migrate hub to Tailwind v4 + native MVDS consumption
    • #289feat(experiments): etsy-notion-sync hub sync panel (task 3.5)

History read from a manifest built at 2026-09-30 (09e7bcc).

2 pull requests, found by commits touching the change folder