0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-06 21:05:21 +02:00

Files

T

TonioandClaude Opus 5 b38d6ddb81 fix(onboarding): choose the launcher's step from the company's mission too (#11429 )

The last of the three ways into onboarding for a company that already exists.
The route resolver and the dashboard both pick the step from whether the
company already has its mission; the "Add Agent" card on `/{prefix}/onboarding`
hardcoded the mission step. So the one entry point whose own copy reads "Add
another agent to X" was the one that stopped to ask X for the mission it
already had.

It now calls `onboardingStepForCompany`, like the other two. `matchedCompany`
moves above the early return because a hook cannot be called after it.

An unsettled or failed lookup still reads as "no mission" and costs the step,
which the customer can answer - the same fail-open rule the other callers
follow, and safe now that confirming the mission updates the company's existing
goal rather than adding a second one.

`OnboardingRoutePage` is exported so this can be driven directly. The
alternative was the whole `<App>` route table, which is a much heavier harness
for a question about one button's argument.

Four cases, and the first fails against the hardcoded step. The button lookup
asserts it matched something before clicking, because a lookup that silently
matches nothing turns the click into a no-op and the test into decoration.

This is the last piece of #11259 that had not landed.

ui typecheck clean; full ui suite 4010 pass. The one failure, in
IssueProperties, is timezone-dependent and reproduces on master.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-15 01:54:47 -07: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

fix(onboarding): choose the launcher's step from the company's mission too (#11429 )

2026-08-15 01:54:47 -07:00

storybook

fix(ui): move agent secret access to searchable secrets tab (#11283 )

2026-08-14 08:03:20 -04:00

components.json

…

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

…

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

…

vitest.setup.ts

…

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.