etsy-notion-sync-build

IN BUILD

"I want a ui for this work - not to have to edit python files every time I want to do it." "…the ui is a prototype inside the hub… which shows what synced, when, and allows me to initiate another sync when I need to." — Katy, 2026-07-15 (session, verbatim)

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—

CAPABILITIES — 2 IN ONE CHANGE

  • etsy-sync-hub-page2 requirements
  • etsy-sync-runtime3 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ○1.1Scheduled run lands in Supabase — the daily sync completes with no human involved, and Katy can see the run (trigger source `scheduled`) and its snapshots in Supabasenot stated
  • ○1.2Tokens rotate across consecutive runs — two back-to-back runs succeed with zero manual token worknot stated
  • ○1.3Etsy remains read-only server-side — runs only ever GET from Etsy, and existing history rows are never mutatednot stated
  • ○1.4Run history renders on the hub page — Katy opens the experiment page and sees what synced, when, what changed, and quota remainingnot stated
  • ○1.5Sync now triggers a run — Katy clicks the button, sees it queued/running, and the completed run appears in the historynot stated

WHAT HAPPENED

  1. ↺ BACK TO DESIGN

    proposal and specs and design and tasks landed

    2026-07-15 · 3 pull requests
    • #286feat(experiments): etsy-notion-sync server-side runtime + hub API
    • #287feat(experiments): etsy-notion-sync hub sync page (tasks 2.1 + 3.5)
    • #289feat(experiments): etsy-notion-sync hub sync panel (task 3.5)

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

3 pull requests, found by commits touching the change folder