v1.4.0

Added

• @dockyard/bridge and @dockyard/ui are published to npm. A
  scaffolded UI project's web/ now resolves them from npm with no
  --dockyard-path and no local Dockyard checkout — dockyard new --template analytics-widgets then cd web && npm install just works. The
  packages set publishConfig.access: "public", track the repo version, and
  publish from a gated, idempotent tag-push job (verified by npm pack + a
  scaffold-install build first). --dockyard-path reverts to a pure
  build-from-source convenience (D-172).
• Bridge View-side task-progress channel. @dockyard/bridge exposes a
  typed bridge.onTaskProgress((p) => …) subscription so an MCP App's card
  can render a live progress value (e.g. "62%") for a long-running task,
  fed by a new ui/notifications/task-progress host→View notification
  (RFC §8.4). The Dockyard runtime emits each TaskHandle.Progress /
  TaskHandle.Status call as an obs/v1 task.progress progress-phase
  event; the inspector forwards those to the App preview, so the channel is
  demoable through dockyard inspect. A host that does not forward progress
  degrades cleanly — the subscriber simply never fires (D-171).

Changed

• obs/v1 task.progress payload gained an optional fraction field
  (the task's completion fraction in [0, 1] at a mid-flight progress point).
  This is an additive change to the obs/v1 contract — existing
  consumers that do not read it are unaffected, the schema version stays
  dockyard.obs/v1, and the golden tests pin the new shape (D-171).

---

Commits

Added

• release: publish @dockyard/bridge + @dockyard/ui to npm (v1.3 wave B item 4)
• bridge: View-side task-progress channel (v1.3 wave B item 5)