Files
PaperClipAI/ui
DottaandPaperclip a9dc0df9da fix(ui): clarify dashboard proposal hierarchy (#22180)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - An agent can propose dashboard areas and responsibilities in one
card.
> - The card put the area name above a separate “New area” row.
> - Responsibility rows had no type label and no visible parent
structure.
> - This pull request puts area changes in the heading and nests
responsibility changes below it.
> - People can see what each change creates and where it belongs before
they apply it.

## Linked Issues or Issue Description

**What existing behavior does this improve?**

The dashboard proposal card in task conversations and the dashboard edit
module.

**Subsystem affected**

The board UI and its Storybook examples.

**Current behavior**

“New area” appears in a row below the area title. New responsibilities
appear at the same level. Their type is not stated.

**Proposed behavior**

“New area” appears beside the area title. Each new responsibility has a
label and sits below its parent area. Existing areas have a separate
label. Area headings follow the heading level in the dashboard module.

**Reason and benefit**

The person can see the parent area, the change type and the text to
review in that order. Long proposals are easier to scan.

**Breaking changes**

None. Proposal inputs, indexes, dependencies and apply/decline endpoints
stay the same.

## What Changed

- Put area changes and their controls in the area heading.
- Nest responsibility rows under each area. Label additions, rewords,
moves and removals.
- Keep the drop/keep dependency behavior and the existing apply payload.
- Keep area classification and group partitions in one helper. Expose
whether each group has an existing parent area.
- Add Storybook examples for the new hierarchy, a narrow layout and a
mix of new and existing areas.
- Add focused component and browser checks for the hierarchy, responsive
layout and apply payload.

## Verification

- 24 focused unit tests passed across the proposal card, dashboard
module and dashboard helpers.
- 25 Chromium checks passed against current-source Storybook after the
review refactor, with one worker and no retries. They cover six proposal
states in light and dark themes at widths of 390 and 960 pixels, plus
the existing apply payload.
- The UI typecheck passed in low-memory mode after the review refactor.
The initial implementation also passed the static Storybook build;
current-head CI supplies broad build coverage.
- 30 map/catalog tests passed. Catalog checks, token gates and
whitespace checks passed.
- A hierarchy regression failed before the fix and passed after it. A
later hosted-story check found a skipped heading level. The fix passed
the expanded browser checks.
- Initial concurrent browser, build and typecheck runs hit the workspace
memory limit. The final browser pass used one worker and the typecheck
used low-memory mode.
- The first CI build stopped because its runner received a shutdown
signal after the UI build completed. A new CI run checks the review
fixes.
- The local verification selector returned exit 2 because the new
browser spec is a global CI input. [Current-head
CI](https://github.com/paperclipai/paperclip/actions/runs/44333497172)
passed typecheck, build, all selected test suites, E2E shards and the
final verify gate for `e71916cdde90ede313cc167ab8cfb8a5c3bb501a`. No
visual baseline comparison was run because the baseline manifest has no
published snapshots.
- [Greptile reviewed the current
head](https://github.com/paperclipai/paperclip/pull/22180#issuecomment-6982500386)
at 5/5 with no findings. Both earlier maintainability threads are
resolved; two Paperclip reviews remain pending.

## Risks

Low risk. This changes UI structure and labels. Long text and drop/keep
controls must continue to fit at narrow widths. The focused browser
checks cover those states. Storybook uses synthetic API data and does
not prove server persistence or permissions.

## Model Used

OpenAI GPT-6 through Codex, with reasoning, tool use and code execution.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-11-18 11:29:48 -06: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.

Editor dependency identity

Keep the root and workspace overrides for @codemirror/state, @codemirror/view, and @lezer/common aligned. CodeMirror requires shared extension identity, while Lezer parsers and syntax highlighters require shared NodeProp IDs. Multiple Lezer copies can crash code-block highlighting with tags is not iterable. src/lib/codemirror-single-instance.test.ts checks the installed dependency graph and highlights sample code through the editor's real language dependencies. GitHub Actions owns regeneration of pnpm-lock.yaml.