Files
pad/web
xarmian 6862c6fc5c fix(BUG-3192): a parent's progress is the server's, and a tab loaded hidden defers its non-essential panels until shown (#1505)
Two parts, per the lead's ruling on Unit B.

1. Progress has one writer. ItemDetail recomputed computedOverrides.progress
   from ChildItems' children list, racing the load's GET /progress, and the
   two disagree. Measured on a private instance: children in a collection
   whose done field is `stage` (board_group_by), one shipped and one not,
   gave server 2/1/50% and client 2/0/0%, because the client read `status`.
   Two of three plain tasks done gave 66% vs 67%. Whichever landed last won.
   The client no longer computes it. A change in the children (ids or
   statuses) within a load re-reads /progress, and the load's first report
   does not, since the load already asked; if the load's own read failed,
   that first report re-asks once. /progress reads are ordered by a ticket
   and high-water mark, so an older answer landing last never wins.
   ChildItems' header takes the same numbers through a new `progress` prop,
   with NO local fallback: without them it shows the child count alone and
   no bar.

2. A tab loaded hidden (session restore, middle-click, several at once)
   mounts decisions, attachments, the comments timeline, children,
   backlinks and relation backlinks only when it is first shown.
   visibility.seenVisible flips once and never back, so nothing is ever
   unmounted, and PLAN-2290's never-unmount rule stands. A visible load is
   unchanged.

Claude-Session: https://claude.ai/code/session_01Vf8uZmYdsrQqJtbAmjUFSX
2026-09-24 07:51:43 -04:00
..
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00

Pad Web UI

SvelteKit 2 + Svelte 5 frontend for Pad, compiled to static files and embedded into the Go binary.

Development

npm install
npm run dev          # Dev server at localhost:5173 (proxies API to localhost:7777)
npm run build        # Production build to build/
npm run check        # Type checking with svelte-check

When developing, run the Go backend separately with make dev from the project root.

Building for Production

Do not build in isolation. Always use make build from the project root — this builds the web frontend, then compiles the Go binary with the build output embedded via //go:embed.

Stack

  • Svelte 5 with runes ($state, $derived, $effect)
  • SvelteKit 2 with adapter-static (SPA mode)
  • Tiptap block editor with markdown round-trip
  • svelte-dnd-action for drag-and-drop in board/list views
  • SSE for real-time updates
  • TypeScript throughout

Structure

src/
  routes/                    SvelteKit pages
    +layout.svelte           App shell (sidebar + main)
    +page.svelte             Landing/redirect
    [workspace]/
      +page.svelte           Dashboard (collections, phases, activity)
      +layout.svelte         SSE connection per workspace
      [collection]/
        +page.svelte         Collection view (board/list)
      [collection]/[item]/
        +page.svelte         Item detail + editor
      conventions/            Purpose-built conventions page
      playbooks/              Purpose-built playbooks page
      settings/               Workspace settings
  lib/
    api/client.ts            HTTP API client
    components/
      layout/                Sidebar, navigation
      editor/                Tiptap editor, raw markdown editor
      fields/                FieldEditor, relation picker
      items/                 ItemCard, ItemDetail
      collections/           BoardView, ListView
      common/                StatusBadge, badges, modals
      search/                CommandPalette
    stores/                  Svelte 5 reactive stores
      workspace.svelte.ts    Workspace state
      collections.svelte.ts  Collection + item state
      ui.svelte.ts           Sidebar, mobile state
    types/index.ts           TypeScript types and constants
  app.css                    Global styles and design tokens