@jini-ai/ui 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Open Design contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,277 @@
+# `@jini/ui` — generic, product-neutral UI primitives
+
+Renamed from `@jini/components` in this session (2026-07-16) once it became clear
+one "components" bucket undersold the scope: this package is meant to hold more
+than flat presentational components — pure business logic, hooks, and injectable
+providers for whatever generic (non-chat, non-OD-branded) UI domains fall out of
+extracting OD's ~217-file `apps/web/src/components/` zone.
+
+## Scope boundary (hard rule, decided 2026-07-16)
+
+Only genuinely **cross-product-reusable** UI lands here — buttons, dialogs, form
+controls, layout primitives, icons, and any small feature-shaped domain (e.g. a
+generic toast/notification system) that isn't tied to Open Design's product
+vocabulary.
+
+**Not here:** anything OD-product-specific — `FileViewer`, `ProjectView`,
+`DesignSystemFlow`, memory-extraction config UI, automations, handoff,
+brand/plugin/figma-specific components. Those stay in
+`foundry/integrations/open-design/` as OD's own UI if/when that adapter needs them.
+`SettingsDialog` itself is one of these (its `execution`/`orbit`/`media`/
+`composio`/`critiqueTheater`/`pet`/`designSystems`/`projectLocations`/
+`routines`/`about` tabs and its AMR/autosave shell state stay OD-specific) —
+but its reusable tabbed-dialog *shell* and 6 of its small, clean, generic
+tabs (`appearance`, `notifications`, `language`, `instructions`,
+`integrations`, `privacy`) shipped as `src/features/settings-dialog/`; see
+`packages/ui/source-map.md`.
+Also not here: chat/artifact UI — that's `@jini/chat-core` (already built),
+`@jini/chat-react`, and `@jini/renderers-react` (separate packages, kept
+separate deliberately — see the chat-core/chat-react split discussion in
+`foundry/docs/jini-port/` session notes).
+
+## Internal structure
+
+- `src/react/components/` — flat, presentational-only atoms. Props in, JSX
+  out, no state/logic/fetch (same discipline as OD's own ADR 0002 slice
+  rule). Renamed from `src/components/` (2026-07-18) to keep the React layer
+  visibly separate at the package top level too, consistent with the
+  per-feature `react/` convention below.
+- `src/features/<domain>/` — anything that needs its own hooks + ports +
+  dumb-components + barrel because it's a cohesive concern, not a single atom
+  (mirrors the ports+dependencies+barrel discipline already proven by OD's
+  `features/memory`, `features/chat-pane`, `features/chat-composer` slices —
+  see `foundry/docs/jini-port/od-reference-branches.md`). **Within each feature
+  (decided 2026-07-17):** files with zero React import (`types.ts`,
+  `constants.ts`, `rules.ts`, `ports.ts`, `dependencies.ts`, the barrel
+  `index.ts`) stay at the feature's top level; anything that imports React
+  (`hooks/`, `components/`) moves under a `react/` subfolder —
+  `features/<domain>/react/{hooks,components}/`. This is a deliberately
+  *lighter* motivation than the `@jini/chat-core`/`@jini/chat-react` package
+  split: not "prepare for a Vue consumer" (no such consumer exists or is
+  planned), just keeping the pure layer visibly and mechanically separate
+  from the React layer within one package, at effectively zero cost. See
+  `packages/ui/source-map.md`'s `features/connectors/` section for the
+  worked example. **Retrofitted onto the flat `src/components/` bucket
+  (2026-07-18, now `src/react/components/`)**; `src/hooks/` below is not —
+  it still sits at the top level; revisit if this pattern proves worth
+  extending there too.
+- `src/providers/` — the *only* place allowed to import a concrete
+  transport/DOM adapter and bind it to a `features/<domain>/ports.ts`
+  interface. Everything else in this package depends on the port, never a
+  concrete implementation.
+- `src/hooks/` — generic hooks that don't belong to one feature domain
+  specifically (feature-local hooks live inside their own `features/<domain>/`
+  instead).
+- `src/utils/` — non-component pure helpers and small stateful browser-API
+  wrappers that don't need the full ports+dependencies ceremony. Added in the
+  i18n/observability/utils porting task (2026-07-16); see
+  `packages/ui/source-map.md`.
+
+## Status
+
+Real content has landed in several parallel passes — see
+`packages/ui/source-map.md` for full per-section provenance:
+
+- `src/utils/` — a framework-free DOM/pure-function layer (2026-07-16), plus
+  a second batch (i18n/observability-adjacent utils: notifications, uuid,
+  platform, etc., also 2026-07-16).
+- `src/features/i18n/` and `src/features/observability/` (2026-07-16).
+- `src/components/` (now `src/react/components/`, see rename above) and
+  `src/hooks/` — `foundry/docs/jini-port/ui-extraction-plan.md` section A's flat-group
+  components and the `useInView` hook (2026-07-17) — the first content in
+  these two directories, and the first task to pull in `react`/`react-dom`
+  as real dependencies of this package.
+- `src/features/connectors/` — the `ConnectorsBrowser.tsx` god-component
+  canary (2026-07-17), per `foundry/docs/jini-port/god-components-extraction-plan.md`
+  §0: an OAuth integration marketplace UI (ports+dependencies+hooks+
+  components+barrel).
+- `src/features/browser-chrome/` — a **partial** slice of
+  `DesignBrowserPanel.tsx` (2026-07-17), per
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Section B: the
+  generic "embeddable webview/iframe browser tab" primitive (navigation
+  stack, address-bar normalization, history/favicon utilities, a
+  viewport-preset switcher, and ports for `onNavigate`/history storage/
+  brand-bridge registration) — not the full file. The first feature to use
+  the new `react/{hooks,components}/` layout described above. See
+  `packages/ui/source-map.md` for the full breakdown, including a confirmed
+  duplicate with `FileViewer.tsx`'s (not-yet-ported) viewport controls.
+- `src/features/sketch-editor/` — `SketchEditor.tsx`'s Excalidraw-integration
+  shim (2026-07-17), per the god-components-extraction-plan.md Consolidation
+  map §B: theme sync, dirty/save/export orchestration, and a DOM-enhancement
+  toolkit for embedding `@excalidraw/excalidraw`. The first feature to use
+  the **new** `react/{hooks,components}/` layout described above, and the
+  first to take a real third-party UI-library dependency (not just
+  browser/DOM primitives).
+- `src/features/asset-grid/` — a generic `AssetGrid<TAsset>` ported from
+  `LibrarySection.tsx` (2026-07-17), per
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Consolidation map:
+  rubber-band multi-select, day-bucketed timeline grouping, kind/source
+  facets, debounced search, SSE live-merge, grid/timeline view toggle,
+  bulk-delete-with-confirm, keyboard shortcuts, kind-aware thumbnail
+  dispatch. The first feature built under the **new**
+  `react/{hooks,components}/` layout described above.
+- `src/features/viewer-shell/` — the file-viewer's media-viewer shell family
+  (2026-07-17), per `foundry/docs/jini-port/god-components-extraction-plan.md`'s
+  consolidation map: a generic viewer-toolbar/body chrome, a resolved
+  viewport-switcher-overlap pair (`ViewportSwitcher`/`ViewportToggleGroup`),
+  the comment side-panel, and a markdown split-pane with scroll-sync. The
+  first feature built under the new `react/{hooks,components}` layout
+  described above (not yet retrofitted onto `connectors`/`progress-card`).
+- `src/features/settings-dialog/` (shell) + `src/features/settings-dialog/
+  tabs/{appearance,notifications,language,instructions,integrations,privacy}/`
+  — extracted from `SettingsDialog.tsx` (2026-07-17), per
+  `foundry/docs/jini-port/god-components-extraction-plan.md` item 5. Uses the NEW
+  `react/{hooks,components}` layout (this is the first feature built with it
+  from scratch). See `packages/ui/source-map.md`.
+- `src/features/tab-strip/` — a consolidated draggable/reorderable tab-strip
+  primitive (2026-07-18), per `foundry/docs/jini-port/god-components-extraction-plan.md`'s
+  Consolidation map §A `features/tab-strip/` row: `WorkspaceTabsBar.tsx`'s
+  workspace-tab strip and `FileWorkspace.tsx`'s independently-reimplemented
+  inline `Tab` component (r6 confirms these are two divergent
+  implementations of the same interaction, not shared even within OD's own
+  codebase) both design into ONE generic primitive (`TabStrip`/
+  `TabStripItem`/`useTabStripDragReorder`) rather than porting either
+  verbatim — drag-to-reorder (with a `'live'`-vs-`'onDrop'` reorder-timing
+  option and pinned-tab drop-edge coercion), active/close-button
+  affordances, host-injected tab content. A dual-shape test proves both
+  source interaction shapes work correctly through the same code paths, not
+  just that they compile. See `packages/ui/source-map.md`.
+- `src/features/list-detail-panel/` — a generic `ListDetailPanel<TItem>`
+  master-detail (list+preview) navigator shell, ported from
+  `DesignSystemsTab.tsx` (2026-07-18), per
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Consolidation map.
+  `PluginsView.tsx`'s detail modal and `ProjectView.tsx`'s composition were
+  read and confirmed NOT to share this shape (a portal overlay and a
+  resizable 2-pane split, respectively) — scoped to `DesignSystemsTab.tsx`
+  alone rather than forcing a broader generalization. See
+  `packages/ui/source-map.md`.
+- 10 more `src/components/` flat atoms (2026-07-18) — the Section C
+  bucket-A batch from `NewProjectPanel.tsx` (`OptionCards`, `CompactToggle`,
+  `ToggleRow`), `PluginsView.tsx` (`StatCard`, `Notice`, `ImportChoice`,
+  `FileImportPanel`), and `EntryShell.tsx` (`OnboardingPanelHeader`,
+  `OnboardingChipField`, `OnboardingDropdown`). See `packages/ui/source-map.md`.
+- `src/features/memory/` — ported from OD's never-merged PR #5228 (a
+  vertical-slice decomposition of `MemorySection.tsx`, 2026-07-18): the
+  saved-memory list/editor, the extraction-history stream, and the
+  connector-sourced-suggestions flow. Carries forward every async/
+  state-correctness fix that PR's own long review cycle found (the bugs were
+  independently confirmed pre-existing in OD's original monolith, not
+  introduced by the decomposition), plus one additional fix
+  (`fetchMemoryList()`'s under-validated response) made during this port. See
+  `packages/ui/source-map.md` for the full provenance note, including why its
+  connector-reconciliation reducers reuse `features/connectors/rules.ts`
+  instead of re-deriving a third copy.
+
+- `src/features/schedule-picker/` — `RecurringSchedulePicker`, a generic
+  "cron-lite" recurring-schedule editor (2026-07-18), ported from
+  `NewAutomationModal.tsx`'s `SchedulePopover` per
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Consolidation map.
+  Also added flat `src/components/{PillButton,PopoverMenu,PopoverItem}.tsx`
+  and `src/utils/timezone.ts`, both from the same source file. See
+  `packages/ui/source-map.md`.
+- `src/features/mention-autocomplete/` — `MentionAutocomplete`, a generic
+  "type a trigger character, get a filtered picker" mention/capability
+  autocomplete (2026-07-18), also ported from `NewAutomationModal.tsx`, per
+  the same Consolidation map row. Checked against `QuickSwitcher.tsx` and
+  the `composer/*` Lexical `@mention` system for a possible 3-way overlap —
+  concluded they're three distinct shapes, not one primitive done three
+  times; see `packages/ui/source-map.md` for the full comparison (read that
+  section before extracting either of those two).
+
+- `src/react/components/EditorIcon.tsx` (2026-07-18) — a flat icon-by-key
+  atom ported from `EditorIcon.tsx`, same lookup-table shape as `Icon.tsx`/
+  `AgentIcon.tsx`/`RemixIcon.tsx`. First file under the new
+  `src/react/components/` path (the `refactor/ui-flat-components-under-react`
+  rename hadn't landed on this branch's base yet, so this is a new folder
+  alongside the still-present flat `src/components/`). See
+  `packages/ui/source-map.md`.
+- `src/features/iframe-pool/` — a generic, host-configurable "cap N mounted
+  iframes, LRU-evict inactive ones, park the rest off-DOM" pool (2026-07-18),
+  ported from `IframeKeepAlivePool.tsx` per
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Consolidation map (the
+  pattern recurs 3 times in OD's own codebase; this is the canonical
+  implementation). Genericizes the origin's `projectId`/`fileName` key pair
+  into one opaque string key and drops the OD-specific
+  `OD_PREVIEW_KEEP_ALIVE` env-var toggle. Fixed two real bugs found while
+  porting (a missing `px`-unit append on numeric style values, and a reused
+  parked iframe never having its hidden/inert markers undone) — see
+  `packages/ui/source-map.md`.
+- `src/features/command-palette/` — `CommandPalette`, a generic Cmd/Ctrl+P
+  fuzzy file-and-item palette (2026-07-18), ported from `QuickSwitcher.tsx`.
+  Collapses the origin's file/tab discriminated union into one
+  `CommandPaletteItem` shape; recents persist via a real
+  `localStorage`-backed `CommandPaletteRecentsPort`. Confirmed distinct from
+  `features/mention-autocomplete/` (already checked in that feature's
+  source-map section) rather than re-litigated. See
+  `packages/ui/source-map.md`.
+- `src/features/tab-launcher-menu/` — `TabLauncherMenu`, an anchored,
+  portal-rendered "+"-button command-palette dropdown (2026-07-18), ported
+  from `TabLauncherMenu.tsx`. Generic `TabLauncherResultItem` shared by both
+  the file list and the tab list; `TabLauncherAction<TActionCtx>` generic
+  over whatever context a host's actions run against, replacing the origin's
+  OD-specific `LauncherContext`. `features/tab-strip/` does not exist on
+  this branch despite the extraction plan describing it as already shipped
+  — documented as a discrepancy, matching the same pattern already recorded
+  for `features/progress-card/`. See `packages/ui/source-map.md`.
+- `src/features/revision-review/` — `RevisionDiffCard`/`RevisionHistoryList`,
+  a generic "proposed change review" widget (2026-07-18), ported from
+  `DesignSystemFlow.tsx`'s remaining pieces. Genericizes `DesignSystemRevision`
+  to `RevisionReviewItem<TMeta>`; unifies the origin's two duplicate diff
+  functions into one `diffAddedLines`. Confirmed distinct from
+  `features/progress-card/` rather than folded in. See
+  `packages/ui/source-map.md`.
+- `src/react/components/{TokenChip,ValueChip,ComponentKitPreview}.tsx`
+  (2026-07-18) — the rest of `DesignSystemFlow.tsx`'s remaining pieces: a
+  color-swatch chip, a plain-value chip, and the theme-toggle-driven
+  style-guide preview panel that renders both, with the token source
+  genericized to host-injected data (the origin's markdown-parsing pipeline
+  is not ported). Reuses the already-shipped `utils/color-math.ts` rather
+  than re-deriving its math a second time. See `packages/ui/source-map.md`.
+- `src/features/file-dropzone/` — `FileDropzone`, a consolidated file-staging
+  primitive (2026-07-18) ported from **two** independent OD file-staging
+  zones — `DesignSystemAssetDropzone.tsx` (a kind-aware thumbnail grid +
+  lightbox) and `DesignSystemFlow.tsx`'s `DropZone` (a labeled zone with a
+  file-dialog cancel-vs-still-loading detection heuristic) — read in full,
+  confirmed the same underlying interaction, and shipped as one primitive
+  instead of two. Also promoted the drag/drop directory-walk and clipboard
+  utilities the two features already duplicated a third time (from
+  `features/asset-tree-browser/rules.ts`) up to `utils/file-transfer.ts` and
+  `browser/useFileDropTarget.ts`, so this package now has exactly one copy.
+  See `packages/ui/source-map.md` for the consolidation evidence, a real
+  infinite-render-loop bug found and fixed during this port, and full
+  test/coverage numbers.
+- `src/utils/scroll-tabs-with-wheel.ts` and `src/utils/color-math.ts`
+  (2026-07-18) — two flat bucket-A atoms from
+  `foundry/docs/jini-port/god-components-extraction-plan.md`'s Consolidation map §C:
+  a generic wheel-to-horizontal-scroll handler for an overflowing tab strip
+  (from `FileWorkspace.tsx`'s `scrollWorkspaceTabsWithWheel`) and hex/RGB/
+  luminance/mix color-math primitives (from `DesignSystemFlow.tsx`). See
+  `packages/ui/source-map.md` for the full writeup, including what was
+  deliberately left behind (the OD-specific color-selection heuristic that
+  consumes the math, not the math itself).
+- `src/features/lexical-rich-text-editor/` (renamed from `rich-text-input/`,
+  2026-07-26 — the feature is Lexical specifically, not a general rich-text
+  input, so the old name promised an engine-neutrality its Lexical-shaped API
+  never had; see `packages/ui/source-map.md`'s dated rename entry) — a real Lexical (Meta's
+  rich-text framework) editor integration ported from OD's chat composer
+  (2026-07-18): editor setup/config, an atomic `@mention`/`/command`
+  token node type (generic, host-injected `resolveMentionColor` instead of
+  importing OD's connector-brand-color logic), a caret-floating-layer
+  positioning hook/component, and serialize/deserialize between the
+  editor's document model and a plain `@token` string. Named by three
+  prior tasks (`mention-autocomplete`'s own "3-way overlap" note among
+  them) as this exact destination. See `packages/ui/source-map.md`,
+  including four dead branches found and refactored away during the
+  coverage-driven-refactor loop (a `mention-parser.ts` merge pass, a
+  `rules.ts` selection catch-all, a `useSeededValue` StrictMode guard, and
+  two `$isRangeSelection`/`$isMentionNode` re-checks) — all four provably
+  unreachable given Lexical's own selection/point invariants, not padded
+  with contrived tests.
+
+Section B (vertical-slice `features/<domain>/` work: `byok-config`,
+`mcp-config`) and section C (cross-package routing) of the extraction plan
+are not started. `workspace-tabs` (renamed `tab-strip`, see the
+Consolidation map's naming-reconciliation note) and `rich-text-input`
+(renamed `lexical-rich-text-editor`, 2026-07-26) are now landed, per above —
+no longer in this "not started" list. The god-components-extraction-plan.md
+list beyond the features enumerated above is also not started.

package/dist/browser/index.d.ts

@@ -0,0 +1,4 @@
+export * from './useDismissOnOutsideOrEscape.js';
+export * from './useGlobalKeydown.js';
+export * from './useFileDropTarget.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/browser/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/browser/index.ts"],"names":[],"mappings":"AAOA,cAAc,kCAAkC,CAAC;AACjD,cAAc,uBAAuB,CAAC;AACtC,cAAc,wBAAwB,CAAC"}

package/dist/browser/index.js

@@ -0,0 +1,10 @@
+// @jini-ai/ui/browser — small, generic browser-interaction hooks shared across
+// feature extractions (popovers/dialogs dismissing on outside-click/Escape,
+// global keydown shortcuts scoped to a component's active lifetime). See
+// packages/ui/source-map.md for the extractions that motivated this and
+// AGENTS.md's `packages/ui` entry for how this directory relates to
+// `utils/`, `hooks/`, and `components/`.
+export * from './useDismissOnOutsideOrEscape.js';
+export * from './useGlobalKeydown.js';
+export * from './useFileDropTarget.js';
+//# sourceMappingURL=index.js.map

package/dist/browser/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/browser/index.ts"],"names":[],"mappings":"AAAA,+EAA+E;AAC/E,4EAA4E;AAC5E,yEAAyE;AACzE,wEAAwE;AACxE,oEAAoE;AACpE,yCAAyC;AAEzC,cAAc,kCAAkC,CAAC;AACjD,cAAc,uBAAuB,CAAC;AACtC,cAAc,wBAAwB,CAAC"}

package/dist/browser/useDismissOnOutsideOrEscape.d.ts

@@ -0,0 +1,18 @@
+import type { RefObject } from 'react';
+export interface UseDismissOnOutsideOrEscapeOptions {
+    /** Skip attaching any listeners while `false` (e.g. only while a menu is open). Defaults to `true`. */
+    enabled?: boolean;
+    /**
+     * Element whose subtree counts as "inside" — a `pointerdown` outside it
+     * calls `onDismiss`. Omit to skip the outside-click listener entirely and
+     * only react to Escape (e.g. a modal whose backdrop click is already
+     * handled by the caller).
+     */
+    containerRef?: RefObject<HTMLElement | null>;
+}
+/**
+ * Calls `onDismiss` on a `pointerdown` outside `options.containerRef` (when
+ * supplied) or on the Escape key anywhere. A no-op outside the browser (SSR).
+ */
+export declare function useDismissOnOutsideOrEscape(onDismiss: () => void, options?: UseDismissOnOutsideOrEscapeOptions): void;
+//# sourceMappingURL=useDismissOnOutsideOrEscape.d.ts.map

package/dist/browser/useDismissOnOutsideOrEscape.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"useDismissOnOutsideOrEscape.d.ts","sourceRoot":"","sources":["../../src/browser/useDismissOnOutsideOrEscape.ts"],"names":[],"mappings":"AAuBA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGvC,MAAM,WAAW,kCAAkC;IACjD,uGAAuG;IACvG,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB;;;;;OAKG;IACH,YAAY,CAAC,EAAE,SAAS,CAAC,WAAW,GAAG,IAAI,CAAC,CAAC;CAC9C;AAED;;;GAGG;AACH,wBAAgB,2BAA2B,CACzC,SAAS,EAAE,MAAM,IAAI,EACrB,OAAO,GAAE,kCAAuC,GAC/C,IAAI,CAcN"}

package/dist/browser/useDismissOnOutsideOrEscape.js

@@ -0,0 +1,42 @@
+// Shared "close this popover/dialog" plumbing. Six independent feature
+// extractions each hand-rolled a version of this: a `pointerdown` outside a
+// menu's own DOM subtree, or the Escape key anywhere, should close it.
+// ViewportSwitcher (viewer-shell) and BrowserViewportControls (browser-chrome)
+// wrote byte-for-byte identical `document.addEventListener('pointerdown', ...)`
+// + `document.addEventListener('keydown', ...)` pairs; useSettingsDialogShell
+// (settings-dialog) and DeleteConfirmDialog (asset-grid) each wrote the
+// Escape-only half of the same pattern (their backdrop already owns the
+// outside-click half via its own `onMouseDown`/`onClick`). This hook covers
+// both shapes — pass `containerRef` for the full dropdown/menu behavior, omit
+// it for Escape-only modal behavior.
+//
+// The listener logic itself is NOT reimplemented here: it's a thin
+// `useEffect` wrapper around `subscribeOutsideClickOrEscape` in
+// `../utils/dom-subscriptions.js`, which is the one place that logic lives
+// (framework-free, SSR-safe, already unit-tested there). `subscribeOutsideClickOrEscape`
+// was updated alongside this hook to use `pointerdown` (matching every real
+// call site above) and to accept an omitted container for the Escape-only
+// case — see that file's doc comment. This hook only adds the
+// React-lifecycle plumbing: `enabled` gating and a latest-callback
+// indirection so callers don't have to memoize `onDismiss`.
+import { useEffect, useRef } from 'react';
+import { subscribeOutsideClickOrEscape } from '../utils/dom-subscriptions.js';
+/**
+ * Calls `onDismiss` on a `pointerdown` outside `options.containerRef` (when
+ * supplied) or on the Escape key anywhere. A no-op outside the browser (SSR).
+ */
+export function useDismissOnOutsideOrEscape(onDismiss, options = {}) {
+    const { enabled = true, containerRef } = options;
+    // Latest-ref indirection so callers don't need to memoize `onDismiss` for
+    // the subscription effect below to stay attached with fresh behavior.
+    const onDismissRef = useRef(onDismiss);
+    useEffect(() => {
+        onDismissRef.current = onDismiss;
+    }, [onDismiss]);
+    useEffect(() => {
+        if (!enabled)
+            return;
+        return subscribeOutsideClickOrEscape(containerRef, () => onDismissRef.current());
+    }, [enabled, containerRef]);
+}
+//# sourceMappingURL=useDismissOnOutsideOrEscape.js.map

package/dist/browser/useDismissOnOutsideOrEscape.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"useDismissOnOutsideOrEscape.js","sourceRoot":"","sources":["../../src/browser/useDismissOnOutsideOrEscape.ts"],"names":[],"mappings":"AAAA,uEAAuE;AACvE,4EAA4E;AAC5E,uEAAuE;AACvE,+EAA+E;AAC/E,gFAAgF;AAChF,8EAA8E;AAC9E,wEAAwE;AACxE,wEAAwE;AACxE,4EAA4E;AAC5E,8EAA8E;AAC9E,qCAAqC;AACrC,EAAE;AACF,mEAAmE;AACnE,gEAAgE;AAChE,2EAA2E;AAC3E,yFAAyF;AACzF,4EAA4E;AAC5E,0EAA0E;AAC1E,8DAA8D;AAC9D,mEAAmE;AACnE,4DAA4D;AAE5D,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,OAAO,CAAC;AAE1C,OAAO,EAAE,6BAA6B,EAAE,MAAM,+BAA+B,CAAC;AAc9E;;;GAGG;AACH,MAAM,UAAU,2BAA2B,CACzC,SAAqB,EACrB,UAA8C,EAAE;IAEhD,MAAM,EAAE,OAAO,GAAG,IAAI,EAAE,YAAY,EAAE,GAAG,OAAO,CAAC;IAEjD,0EAA0E;IAC1E,sEAAsE;IACtE,MAAM,YAAY,GAAG,MAAM,CAAC,SAAS,CAAC,CAAC;IACvC,SAAS,CAAC,GAAG,EAAE;QACb,YAAY,CAAC,OAAO,GAAG,SAAS,CAAC;IACnC,CAAC,EAAE,CAAC,SAAS,CAAC,CAAC,CAAC;IAEhB,SAAS,CAAC,GAAG,EAAE;QACb,IAAI,CAAC,OAAO;YAAE,OAAO;QACrB,OAAO,6BAA6B,CAAC,YAAY,EAAE,GAAG,EAAE,CAAC,YAAY,CAAC,OAAO,EAAE,CAAC,CAAC;IACnF,CAAC,EAAE,CAAC,OAAO,EAAE,YAAY,CAAC,CAAC,CAAC;AAC9B,CAAC"}

package/dist/browser/useFileDropTarget.d.ts

@@ -0,0 +1,25 @@
+import { type DragEvent } from 'react';
+export interface UseFileDropTargetResult {
+    draggingFiles: boolean;
+    dropReadError: string | null;
+    clearDropReadError: () => void;
+    onDragEnter: (event: DragEvent<Element>) => void;
+    onDragOver: (event: DragEvent<Element>) => void;
+    onDragLeave: (event: DragEvent<Element>) => void;
+    onDrop: (event: DragEvent<Element>) => void;
+}
+/**
+ * A generic drop target: nesting-depth-tracked drag-over state (`dragenter`/
+ * `dragleave` fire for every descendant element, so a naive boolean would
+ * flicker off while dragging over a child element — `dragDepthRef` is what
+ * avoids that), and a drop handler that recursively expands dropped folders
+ * via `utils/file-transfer.ts`'s `filesFromDataTransfer`.
+ *
+ * Promoted (2026-07-18) from `features/asset-tree-browser`'s
+ * `useAssetTreeDragUpload` (itself already fully generic — no asset-tree
+ * types) once `features/file-dropzone/` needed the identical shape, so a
+ * second feature reuses one hook instead of a near-duplicate copy.
+ * `useAssetTreeDragUpload` re-exports this under its original name.
+ */
+export declare function useFileDropTarget(onUploadFiles: (files: File[]) => void): UseFileDropTargetResult;
+//# sourceMappingURL=useFileDropTarget.d.ts.map

package/dist/browser/useFileDropTarget.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"useFileDropTarget.d.ts","sourceRoot":"","sources":["../../src/browser/useFileDropTarget.ts"],"names":[],"mappings":"AAAA,OAAO,EAAiC,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAItE,MAAM,WAAW,uBAAuB;IACtC,aAAa,EAAE,OAAO,CAAC;IACvB,aAAa,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,kBAAkB,EAAE,MAAM,IAAI,CAAC;IAC/B,WAAW,EAAE,CAAC,KAAK,EAAE,SAAS,CAAC,OAAO,CAAC,KAAK,IAAI,CAAC;IACjD,UAAU,EAAE,CAAC,KAAK,EAAE,SAAS,CAAC,OAAO,CAAC,KAAK,IAAI,CAAC;IAChD,WAAW,EAAE,CAAC,KAAK,EAAE,SAAS,CAAC,OAAO,CAAC,KAAK,IAAI,CAAC;IACjD,MAAM,EAAE,CAAC,KAAK,EAAE,SAAS,CAAC,OAAO,CAAC,KAAK,IAAI,CAAC;CAC7C;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,iBAAiB,CAAC,aAAa,EAAE,CAAC,KAAK,EAAE,IAAI,EAAE,KAAK,IAAI,GAAG,uBAAuB,CAgDjG"}