Files
pad/web
xarmian 7e85d1ce4e fix(attachments): viewer honors the missing metadata phase; comment refresh (PLAN-2392 3c-i)
Route the surface metadata machine's authoritative `missing` (404) phase through
the viewer's existing tombstone/advance path: an out-of-page delete (another tab,
a job, the API) never crosses the process-local deletion bus, but where the header
probes the shown image its HEAD returns `missing`, which is just as authoritative
(DR-17). A sentinel + untrack keep the effect CONVE-1688-safe and terminating
(a whole gone set cascades advance→advance→close, one 404 at a time). Only
`missing` latches; a `transient` stays retryable.

Fence `runToolbarAction` against the shown identity and reset `toolbarBusy`/
`toolbarError` on subject change, so a confirmed or slow delete of the shown image
that races the advance can't strand "Deleting…" or an error on the survivor now
on screen.

Refresh the final-state comments: the viewer is now the second consumer of the
shared action list; the viewer host carries live `mutationsEnabled` since C1 while
the open channel stays permission-free; the deletion bus is process-local, and
the missing path's probe-scope (strip images seed mime+size and aren't re-probed)
is stated where it matters.

Tests: missing→advance, missing-only→close, whole-set cascade→close, transient→
no-op, and shown-delete-while-confirm-up→clean-toolbar (mutation-verified against
the reset).

Claude-Session: https://claude.ai/code/session_01WFBYxdBuSZs2tjipATxAZu
2026-08-08 19:30:52 +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
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
      activity/              ActivityFeed
    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