Jannik/PaperClipAI

0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-26 18:31:34 +01:00

Files

T

History

610bd160a8 feat(ui): render liveness-aware recovery as a recessed in-progress state

Recovery surfaces classified nearly every active action as `needed`, so a
task showed a prominent amber "Recovery needed" warning even while a
recovery owner was already running it.

Make the display derivation liveness-aware. `deriveRecoveryDisplayState`
now takes optional `RecoveryLivenessSignals` (recovery-owner run, source
live run, queued wake, live continuation) and resolves the five display
states against them:

- a live/queued run owned by the recovery owner is `in_progress`, which
  outranks escalation — the escalation already found an owner
- a newer durable source-owner run folds the action to `observe_only`
  rather than leaving a stale call to action
- prominent amber/red is kept only for `needed` (no owner/path) and
  `escalated` (a decision is genuinely required)

Recessed states render as `RecoveryProgressLine` — an expandable
"Recovery in progress · CTO" row that reveals the existing recovery card
on toggle, so evidence and resolve actions stay inspectable without a
second prominent surface competing for attention.

Applied across the recovery card, issue rows, active-agents panel,
blocker indicators, blocked inbox chips, the workspace recovery surface,
and both the classic and chat-style task threads.

Verified: 349 focused UI tests pass across 16 affected suites, tsc clean,
and `pnpm check:token-gates` reports all three gates clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-08-15 19:19:38 +00:00

public

fix(ui): always give respondWith a real Response in the sw fetch fallback (#11292 )

2026-08-12 11:23:18 -07:00

src

feat(ui): render liveness-aware recovery as a recessed in-progress state

2026-08-15 19:19:38 +00:00

storybook

feat(ui): render liveness-aware recovery as a recessed in-progress state

2026-08-15 19:19:38 +00:00

components.json

Overhaul UI with shadcn components and new pages

2026-02-17 09:07:32 -06:00

index.html

fix(ui): fetch the web app manifest with credentials (#11245 )

2026-08-11 19:11:56 -07:00

package.json

build(deps): align Lexical packages at 0.49.0 (#10728 )

2026-08-13 13:17:29 -07:00

README.md

[codex] add comprehensive UI Storybook coverage (#4132 )

2026-04-20 12:13:23 -05:00

tsconfig.json

chore(ui): remove deprecated baseUrl from ui/tsconfig.json (#4067 )

2026-08-04 18:39:13 -05:00

vite.config.ts

revert(ui): back out onboarding port (#10786 ) (#11067 )

2026-08-07 14:55:34 -07:00

vite.qa.config.mjs

feat(mcp) [split 7/8]: activate Apps and gateway UI (#9562 )

2026-07-14 15:40:08 -05:00

vitest.config.ts

build(deps): upgrade lexical family to 0.46.0 and pin via overrides (fixes dual-version getType crash) (#9180 )

2026-07-07 13:00:26 -07:00

vitest.setup.ts

feat(ui): NUX rework behind enableConferenceRoomChat experimental flag — capsule onboarding, conference-room chat, unified composer (#8000 )

2026-06-11 16:32:55 -05:00

README.md

@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.