Files
pad/web
xarmian d67a02e785 fix(web): the tag saver no longer overwrites a concurrent tag change (BUG-3143) (#1432)
The item pane's tag saver PATCHed the whole tag set with no version token.
Another writer's tag change disappeared, with no conflict anywhere to retry on.

Every tag batch now:
- carries the version token of the row whose tags it last confirmed (seq via
  occTokenFor, as updateField sends), so a write that landed since is refused
  with a 409 instead of overwritten;
- sends the burst's GESTURE applied to that row,
  rederiveListWrite(base, desired, confirmed), the same helper BUG-3038 added.
  It does this on EVERY batch, not only after a 409. The saver coalesces edits
  into absolute sets taken from a display that can lack the other writer's
  tag, and a batch that follows a 409 goes out with a current token, so a
  replay there would erase the tag with no conflict.

The conflict path is a new top-level sendTagBatch: identityHeld before the
refetch, the refetch, identityHeld again, advance, re-send. flushTagSaver
keeps its original single-await shape and its BUG-3084 check. When a batch
drains with nothing queued, the saver is rebased onto the returned row. The
tag overlay would otherwise keep hiding the other writer's tag after the
burst.

Playwright: real server conflicts, one batch and two. Removing the token,
re-deriving only on a 409, or dropping the rebase each turns a leg red.

Claude-Session: https://claude.ai/code/session_01X4uYKs5ZPF28eCWfm8VPvE
2026-09-22 12:19:23 -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