Files
PaperClipAI/ui
DottaandPaperclip 58d5adc1c7 Wire external object surfaces across markdown, properties, related work, sidebar, list, filters
- MarkdownBody/InlineEditor accept an externalReferences map and render
  resolved URLs with a host-rendered status icon prefix (no inline plugin
  React, per Phase 1B security review)
- IssueProperties shows a read-only "External objects" row above Parent,
  with skeleton/error fallbacks
- IssueRelatedWorkPanel adds a third "External objects" section between
  References and Referenced by, severity-sorted with mention-source chips
- SidebarProjects renders a per-project ExternalObjectStatusSummary marker
  to the right of the project name
- IssueRow accepts an externalObjectSummary in the desktop trailing slot
- IssueFiltersPopover gains an "External object status" section with
  failed/waiting/running/auth_required/unreachable/stale/none options
- Add useIssueExternalObjects, useIssueExternalObjectSummary,
  useProjectExternalObjectSummary hooks plus queryKeys.externalObjects
- IssueDetail loads external objects once and forwards to description,
  properties, mobile properties drawer, and the related-work tab

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-23 00:35:04 +00:00
..

@paperclipai/ui

Published static assets for the Paperclip board UI.

What gets published

The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.

Storybook

Storybook config, stories, and fixtures live under ui/storybook/.

pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook

Typical use

Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.