@xh/hoist 81.0.0 → 81.0.2

package/CHANGELOG.md

@@ -1,6 +1,21 @@
 # Changelog
 
-## 81.0.0 - 2026-02-12
+## 81.0.2 - 2026-02-12
+
+### 💥 Breaking Changes (upgrade difficulty: 🟢 LOW)
+
+See [`docs/upgrade-notes/v81-upgrade-notes.md`](docs/upgrade-notes/v81-upgrade-notes.md) for
+detailed, step-by-step upgrade instructions with before/after code examples.
+
+* Requires hoist-core `v36.1` or greater.
+* Renamed the CSS class on Panel's outer structural wrapper from `xh-panel__content` to
+  `xh-panel__inner`. The `xh-panel__content` class is now used on the new inner frame wrapping
+  content items (the target of `contentBoxProps`). Update any app CSS selectors targeting the old
+  `xh-panel__content` class accordingly.
+* Changed the signatures of some `HoistAuthModel` methods to return `IdentityInfo` rather than
+  a `boolean`. For most apps this will require a trivial change to the signature of the
+  implementation of `HoistAuthModel.completeAuthAsync`.
+* Renamed Blueprint `Card` exports to `BpCard` and `bpCard`.
 
 ### 🎁 New Features
 
@@ -14,20 +29,9 @@
   `Card`.
 * Added `scrollable` prop to desktop `Panel`, matching the existing mobile `Panel` API. Sets
   `overflowY: 'auto'` on the content area.
-* Layout props `padding`, `margin` (and their directional variants), and `gap` now accept a boolean
-  shorthand: `true` resolves to the standard app padding CSS variable (`--xh-pad-px`, default 10px),
-  `false` is treated as unset.
-
-### 💥 Breaking Changes
-* Requires hoist-core `v36.1` or greater.
-* The CSS class on Panel's outer structural wrapper has been renamed from `xh-panel__content` to
-  `xh-panel__inner`. The `xh-panel__content` class is now used on the new inner frame wrapping
-  content items (the target of `contentBoxProps`). Update any app CSS selectors targeting the old
-  `xh-panel__content` class accordingly.
-* Change to the signatures of some `HoistAuthModel` methods to return `IdentityInfo` rather than
-  a `boolean`.  For most apps this will require a trivial change to the signature of the
-  implementation of `HoistAuthModel.completeAuthAsync`.
-* Renamed Blueprint `Card` exports to `BpCard` and `bpCard`.
+* Enhanced layout props `padding`, `margin` (and their directional variants), and `gap` to accept a
+  boolean shorthand: `true` - resolves to the standard app padding CSS variable (`--xh-pad-px`,
+  default 10px), with `false` treated as unset.
 
 ### 🐞 Bug Fixes
 
@@ -42,19 +46,22 @@
 
 ### ⚙️ Technical
 
-* Improve the efficiency of initialization by reducing the number of server requests required
-  to get user identity.
+* Improved the efficiency of initialization by reducing the number of fetch requests required to
+  load user identity.
 
 ## 80.0.1 - 2026-01-28
 
 ### ⚙️ Technical
 
-* New properties `Cube.lastUpdated` and `View.cubeUpdated` support more efficient updating of
+* Added `Cube.lastUpdated` and `View.cubeUpdated` properties to support more efficient updating of
   connected cube views.
 
 ## 80.0.0 - 2026-01-27
 
-### 💥 Breaking Changes
+### 💥 Breaking Changes (upgrade difficulty: 🟢 LOW)
+
+See [`docs/upgrade-notes/v80-upgrade-notes.md`](docs/upgrade-notes/v80-upgrade-notes.md) for
+detailed, step-by-step upgrade instructions with before/after code examples.
 
 * Modified several CSS classes related to `FormField` to better follow BEM conventions.
     * ⚠️The commonly targeted `xh-form-field-label` class is now `xh-form-field__label`, although
@@ -88,7 +95,7 @@
 * Added `AggregationContext` as an additional argument to `CubeField.canAggregateFn`.
 * Added `filterMatchMode` option to `ColChooserModel`, allowing customizing match to `start`,
   `startWord`, or `any`.
-* Added support for reconnecting a `View` to its associated `Cube`
+* Added support for reconnecting a `View` to its associated `Cube`.
 
 ### ⚙️ Typescript API Adjustments
 
@@ -122,11 +129,14 @@
 * Added a direct dependency and forced resolution to pin to `jquery@3.x`. This is a transitive
   dependency of the `golden-layout` library and is specified by that library very loosely as `*`,
   causing a break if upgraded to jQuery's new 4.x release.
-  * ⚠️Apps will need to add their own resolution to ensure they stay on the last 3.x version.
+    * ⚠️Apps will need to add their own resolution to ensure they stay on the last 3.x version.
 
 ## 79.0.0 - 2026-01-05
 
-### 💥 Breaking Changes
+### 💥 Breaking Changes (upgrade difficulty: 🟠 MEDIUM)
+
+See [`docs/upgrade-notes/v79-upgrade-notes.md`](docs/upgrade-notes/v79-upgrade-notes.md) for
+detailed, step-by-step upgrade instructions with before/after code examples.
 
 Note that a server-side upgrade to `hoist-core >= 35` is recommended to support several changes in
 this release, but is not strictly required.
@@ -206,7 +216,7 @@ this release, but is not strictly required.
 ### 🐞 Bug Fixes
 
 * Fixed Highcharts timezone handling regression from version 77.
-    * Note that Highcharts has deprecated the `time.useUTC` option and its functioning seem
+    * Note that Highcharts has deprecated the `time.useUTC` option and its functioning seems
       suspect - set `time.timezone` instead. See https://api.highcharts.com/highcharts/time.useUTC.
 
 ### ⚙️ Technical
@@ -231,7 +241,10 @@ this release, but is not strictly required.
 
 ## 78.0.0 - 2025-11-21
 
-### 💥 Breaking Changes
+### 💥 Breaking Changes (upgrade difficulty: 🎉 TRIVIAL)
+
+See [`docs/upgrade-notes/v78-upgrade-notes.md`](docs/upgrade-notes/v78-upgrade-notes.md) for
+detailed, step-by-step upgrade instructions with before/after code examples.
 
 * `GridModel.setColumnState` no longer patches existing column state, but instead replaces it
   wholesale. Applications that were relying on the prior patching behavior will need to
@@ -248,7 +261,7 @@ this release, but is not strictly required.
 ### 🐞 Bug Fixes
 
 * Fixed `GridModel` not appending children to the parents correctly when recs have numeric IDs.
-* Fixed issue where newly added columns appearing in the Displayed Columns section of the column
+* Fixed issue where newly added columns would appear in the Displayed Columns section of the column
   chooser after loading grid state that was persisted before the columns were added to the grid.
 * Removed a minor Cube `Query` annoyance - `dimensions` are now automatically added to the `fields`
   list and do not need to be manually repeated there.
@@ -273,10 +286,10 @@ this release, but is not strictly required.
 
 ### 🐞 Bug Fixes
 
-* Improved `StoreRecord.isModified` to no return `true` after a field has been edited but then
+* Improved `StoreRecord.isModified` to not return `true` after a field has been edited but then
   returned to its original value in a subsequent edit.
 * Restored support for `TabModel.content` set to `null`, to support dynamic tab content.
-* Fixed and issue where stray context menus could appear when clicking on column group headers and
+* Fixed an issue where stray context menus could appear when clicking on column group headers and
   other grid empty space.
 
 ## 77.0.1 - 2025-10-29
@@ -305,7 +318,7 @@ this release, but is not strictly required.
 
 ### ⚙️ Technical
 
-* Support Grails 7 service name conventions in admin client (backward compatible)
+* Added support for Grails 7 service name conventions in admin client (backward compatible).
 
 ## 76.2.0 - 2025-10-22
 

package/build/types/kit/blueprint/Wrappers.d.ts

@@ -1,5 +1,8 @@
-import { Alert, Button, ButtonGroup, Callout, Card as BpCard, Checkbox, ControlGroup, Dialog, Drawer, EditableText, FileInput, FormGroup, Hotkey, Hotkeys, InputGroup, Label, Menu, MenuDivider, MenuItem, Navbar, NavbarDivider, NavbarGroup, NavbarHeading, NumericInput, OverflowList, Overlay2 as Overlay, Popover, Radio, RadioGroup, RangeSlider, Slider, Switch, Tab, Tabs, Tag, TagInput, Text, TextArea, Tooltip, Tree } from '@blueprintjs/core';
+import { Alert, Button, ButtonGroup, Callout, Card as BpCard, Checkbox, ControlGroup, type DialogProps, Drawer, EditableText, FileInput, FormGroup, Hotkey, Hotkeys, InputGroup, Label, Menu, MenuDivider, MenuItem, Navbar, NavbarDivider, NavbarGroup, NavbarHeading, NumericInput, OverflowList, Overlay2 as Overlay, type PopoverProps, Radio, RadioGroup, RangeSlider, Slider, Switch, Tab, Tabs, Tag, TagInput, Text, TextArea, Tooltip, Tree } from '@blueprintjs/core';
 import { DatePicker } from '@blueprintjs/datetime';
+import React from 'react';
+declare const Dialog: React.FC<DialogProps>;
+declare const Popover: React.FC<PopoverProps>;
 export { Alert, Button, ButtonGroup, Callout, BpCard, Checkbox, ControlGroup, DatePicker, Dialog, Drawer, EditableText, FileInput, FormGroup, Hotkeys, Hotkey, InputGroup, Label, Menu, MenuItem, MenuDivider, Navbar, NavbarDivider, NavbarGroup, NavbarHeading, NumericInput, OverflowList, Overlay, Popover, Radio, RadioGroup, RangeSlider, Slider, Switch, Tab, Tabs, Tag, TagInput, TextArea, Text, Tooltip, Tree };
-export declare const alert: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").AlertProps>, button: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ButtonProps>, controlGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ControlGroupProps>, checkbox: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CheckboxProps>, dialog: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").DialogProps>, datePicker: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/datetime").DatePickerProps>, menuDivider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuDividerProps>, menuItem: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuItemProps>, navbarDivider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarDividerProps>, numericInput: import("@xh/hoist/core").ElementFactory<Omit<import("@blueprintjs/core").HTMLInputProps, "size"> & import("@blueprintjs/core").NumericInputProps>, overflowList: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").OverflowListProps<any>>, popover: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").PopoverProps<import("@blueprintjs/core").DefaultPopoverTargetHTMLProps>>, radio: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ControlProps>, rangeSlider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").RangeSliderProps>, slider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").SliderProps>, switchControl: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").SwitchProps>, textArea: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TextAreaProps>, tree: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TreeProps<unknown>>, tagInput: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TagInputProps>, fileInput: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").FileInputProps>, overlay: import("@xh/hoist/core").ElementFactory<Omit<import("@blueprintjs/core").Overlay2Props, "ref"> & import("react").RefAttributes<import("@blueprintjs/core").OverlayInstance>>, tooltip: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TooltipProps<import("@blueprintjs/core").DefaultPopoverTargetHTMLProps>>;
-export declare const buttonGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ButtonGroupProps>, callout: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CalloutProps>, bpCard: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CardProps>, drawer: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").DrawerProps>, editableText: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").EditableTextProps>, formGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").FormGroupProps>, hotkey: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").HotkeyProps>, hotkeys: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").HotkeysProps>, inputGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").InputGroupProps>, label: import("@xh/hoist/core").ElementFactory<import("react").AllHTMLAttributes<HTMLLabelElement> & import("react").RefAttributes<HTMLLabelElement>>, menu: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuProps>, navbar: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarProps>, navbarHeading: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarHeadingProps>, navbarGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarGroupProps>, radioGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").RadioGroupProps>, tabs: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TabsProps>, tab: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TabProps>, tag: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TagProps>, text: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TextProps>;
+export declare const alert: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").AlertProps>, button: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ButtonProps>, controlGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ControlGroupProps>, checkbox: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CheckboxProps>, dialog: import("@xh/hoist/core").ElementFactory<DialogProps>, datePicker: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/datetime").DatePickerProps>, menuDivider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuDividerProps>, menuItem: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuItemProps>, navbarDivider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarDividerProps>, numericInput: import("@xh/hoist/core").ElementFactory<Omit<import("@blueprintjs/core").HTMLInputProps, "size"> & import("@blueprintjs/core").NumericInputProps>, overflowList: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").OverflowListProps<any>>, popover: import("@xh/hoist/core").ElementFactory<PopoverProps<import("@blueprintjs/core").DefaultPopoverTargetHTMLProps>>, radio: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ControlProps>, rangeSlider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").RangeSliderProps>, slider: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").SliderProps>, switchControl: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").SwitchProps>, textArea: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TextAreaProps>, tree: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TreeProps<unknown>>, tagInput: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TagInputProps>, fileInput: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").FileInputProps>, overlay: import("@xh/hoist/core").ElementFactory<Omit<import("@blueprintjs/core").Overlay2Props, "ref"> & React.RefAttributes<import("@blueprintjs/core").OverlayInstance>>, tooltip: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TooltipProps<import("@blueprintjs/core").DefaultPopoverTargetHTMLProps>>;
+export declare const buttonGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").ButtonGroupProps>, callout: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CalloutProps>, bpCard: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").CardProps>, drawer: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").DrawerProps>, editableText: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").EditableTextProps>, formGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").FormGroupProps>, hotkey: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").HotkeyProps>, hotkeys: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").HotkeysProps>, inputGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").InputGroupProps>, label: import("@xh/hoist/core").ElementFactory<React.AllHTMLAttributes<HTMLLabelElement> & React.RefAttributes<HTMLLabelElement>>, menu: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").MenuProps>, navbar: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarProps>, navbarHeading: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarHeadingProps>, navbarGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").NavbarGroupProps>, radioGroup: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").RadioGroupProps>, tabs: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TabsProps>, tab: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TabProps>, tag: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TagProps>, text: import("@xh/hoist/core").ElementFactory<import("@blueprintjs/core").TextProps>;

package/docs/changelog-format.md

@@ -10,9 +10,11 @@ apply.
 ```markdown
 ## {VERSION} - {YYYY-MM-DD}
 
-### 💥 Breaking Changes
+### 💥 Breaking Changes (upgrade difficulty: {RATING})
+
+See [`docs/upgrade-notes/v{NN}-upgrade-notes.md`](docs/upgrade-notes/v{NN}-upgrade-notes.md) for
+detailed, step-by-step upgrade instructions with before/after code examples.
 
-* {Introductory bullet with overview and link to upgrade notes}
 * {Required change 1}
 * {Required change 2}
     * {Sub-detail if needed}
@@ -87,12 +89,20 @@ Bad:
 
 ## Breaking Changes Section
 
-For major versions, this section should:
-
-1. **List** every required app-level change as a separate bullet
-2. **Be specific** — name exact classes, methods, and config keys
-3. **Include** difficulty-rated sub-headers when useful (see Difficulty Ratings below)
-4. **Link** to upgrade notes when available: `docs/upgrade-notes/v{NN}-upgrade-notes.md`
+**Every major version with breaking changes MUST include all of the following.** Do not skip or
+reorder these requirements:
+
+1. **Difficulty rating in the header** — append `(upgrade difficulty: {RATING})` to the section
+   header. See Difficulty Ratings below for the rating scale.
+2. **Upgrade notes link as a standalone sentence** — immediately after the header (before any
+   bullets), include a sentence linking to the upgrade notes file. This is **not** a bullet point —
+   it is a standalone paragraph. Use this exact format:
+   ```markdown
+   See [`docs/upgrade-notes/v{NN}-upgrade-notes.md`](docs/upgrade-notes/v{NN}-upgrade-notes.md) for
+   detailed, step-by-step upgrade instructions with before/after code examples.
+   ```
+3. **List** every required app-level change as a separate bullet
+4. **Be specific** — name exact classes, methods, and config keys
 5. **Link** to relevant framework upgrade guides (e.g. Blueprint, AG Grid) when applicable
 
 Each bullet should be concise (1-2 lines). The upgrade notes file handles expanded detail with

package/docs/upgrade-notes/v81-upgrade-notes.md

@@ -1,9 +1,6 @@
 # Hoist React v81 Upgrade Notes
 
-> **From:** v80.x → v81.0.0 | **Released:** _unreleased_ | **Difficulty:** 🟢 LOW
-
-**Note:** This guide is a draft for the upcoming v81 release and may be updated before the final
-release.
+> **From:** v80.x → v81.0.2 | **Released:** 2026-02-12 | **Difficulty:** 🟢 LOW
 
 ## Overview
 
@@ -39,7 +36,7 @@ Before:
 
 After:
 ```json
-"@xh/hoist": "~81.0.0"
+"@xh/hoist": "~81.0.2"
 ```
 
 ### 2. Update Panel CSS Class References

package/kit/blueprint/Wrappers.ts

@@ -15,7 +15,8 @@ import {
     Card as BpCard,
     Checkbox,
     ControlGroup,
-    Dialog,
+    Dialog as BpDialog,
+    type DialogProps,
     Drawer,
     EditableText,
     FileInput,
@@ -34,7 +35,8 @@ import {
     NumericInput,
     OverflowList,
     Overlay2 as Overlay,
-    Popover,
+    Popover as BpPopover,
+    type PopoverProps,
     Radio,
     RadioGroup,
     RangeSlider,
@@ -51,6 +53,15 @@ import {
 } from '@blueprintjs/core';
 import {DatePicker} from '@blueprintjs/datetime';
 import {elementFactory} from '@xh/hoist/core';
+import React, {createElement as reactCreateElement} from 'react';
+
+// Wrap Dialog and Popover to disable fade/scale-in transitions by default.
+// See also popover & overlay related CSS overrides in ./styles.scss.
+const Dialog: React.FC<DialogProps> = props =>
+    reactCreateElement(BpDialog, {transitionDuration: 0, transitionName: 'none', ...props});
+
+const Popover: React.FC<PopoverProps> = props =>
+    reactCreateElement(BpPopover, {transitionDuration: 0, ...props});
 
 //---------------------
 // Re-exports

package/kit/blueprint/index.ts

@@ -7,11 +7,9 @@
 import {
     BlueprintProvider,
     Classes,
-    Dialog,
     FocusStyleManager,
     type HotkeyConfig,
     OverlayToaster,
-    Popover,
     PopoverInteractionKind,
     Position,
     type ToasterPosition,
@@ -26,12 +24,6 @@ import './styles.scss';
 // on focusable components when focused via mouse click.
 FocusStyleManager.onlyShowFocusOnTabs();
 
-// Disable fade/scale-in transitions.
-// See also popover & overlay related overrides in ./styles.scss.
-Dialog.defaultProps.transitionDuration = 0;
-Dialog.defaultProps.transitionName = 'none';
-Popover.defaultProps.transitionDuration = 0;
-
 //---------------------
 // Re-exports
 //---------------------

package/package.json

@@ -1,8 +1,11 @@
 {
   "name": "@xh/hoist",
-  "version": "81.0.0",
+  "version": "81.0.2",
   "description": "Hoist add-on for building and deploying React Applications.",
-  "repository": "github:xh/hoist-react",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/xh/hoist-react.git"
+  },
   "homepage": "https://xh.io",
   "bugs": "https://github.com/xh/hoist-react/issues",
   "author": "Extremely Heavy Industries, Inc.",

package/.claude/settings.json

@@ -1,6 +0,0 @@
-{
-  "enabledPlugins": {
-    "typescript-lsp@claude-plugins-official": true,
-    "jdtls-lsp@claude-plugins-official": true
-  }
-}

package/.claude/skills/xh-update-doc-links/SKILL.md

@@ -1,108 +0,0 @@
----
-name: xh-update-doc-links
-description: Pre-commit documentation consistency check. Ensures docs/README.md index and docs/README-ROADMAP.md stay in sync with documentation files on disk, validates inter-doc links, and enhances cross-references when new docs are added. Invoke after editing READMEs or concept docs, before committing.
-tools: Read, Glob, Grep, Bash, Edit, Write
----
-
-# xh-update-doc-links — Documentation Consistency Check
-
-Pre-commit skill to ensure documentation index files, inter-doc links, and cross-references
-stay consistent after editing READMEs or concept docs.
-
-## Step 1: Discover Documentation Files
-
-Build a complete inventory of documentation files on disk.
-
-1. Use `Glob` to find all `**/README.md` files, excluding `node_modules/`, `public/`, and
-   `static/` directories.
-2. Use `Glob` to find all files under `docs/`.
-3. Run `git diff --name-only` and `git status --porcelain` to identify which docs were
-   recently changed or added.
-4. Build a master list of all documentation files, noting which are new or recently modified.
-
-## Step 2: Read Index Files
-
-Read the two index files and parse their current entries.
-
-1. Read `docs/README.md` — focus on the **Package Documentation** section (the tables under
-   "Core Framework", "Components", "Utilities", "Concepts", and "Other Packages").
-   - Parse each table row to extract the package path and linked README path.
-   - Parse the "Other Packages" paragraph to extract unlisted package names.
-
-2. Read `docs/README-ROADMAP.md` — parse all priority tables and the Concepts table.
-   - Extract each package path, description, and status value.
-   - Note which entries are `Planned`, `Drafted`, or `[Done](link)`.
-
-## Step 3: Reconcile Indexes
-
-Compare documentation on disk against both index files.
-
-### docs/README.md Reconciliation
-
-For each README on disk:
-- Check if it has an entry in the appropriate `docs/README.md` table (Core Framework, Components,
-  Utilities, Concepts, or Other Packages).
-- **Missing entries:** Add a new table row in the correct section using this format:
-  ```markdown
-  | [`/package/`](../package/README.md) | One-sentence description | Key, Topics, Here |
-  ```
-  (Note: paths are relative from `docs/`, so package READMEs use `../` prefix.)
-- **Stale entries:** If an entry links to a README that no longer exists, remove it.
-- **Promotion:** If a package is listed in the "Other Packages" paragraph and now has a
-  README, move it to the appropriate table and remove it from the paragraph.
-- **AGENTS.md directive:** Verify that `AGENTS.md` still contains the directive pointing
-  to `docs/README.md` (the "Hoist Documentation" section). Do not re-add package tables
-  to AGENTS.md.
-
-### README-ROADMAP.md Reconciliation
-
-For each README on disk:
-- Check if it has an entry in the roadmap with the correct status.
-- **Status updates:** Change `Planned` → `[Done](../path/README.md)` for newly completed docs.
-  Change `Drafted` → `[Done](../path/README.md)` if appropriate.
-- **Missing entries:** Add entries for docs not yet on the roadmap.
-- **Progress notes:** Add a progress note entry for the current date if doc changes are
-  detected. Follow the existing format in the "Progress Notes" section.
-
-## Step 4: Validate Inter-Doc Links
-
-Scan every documentation file (READMEs + concept docs) for relative markdown links.
-
-1. For each file, extract all markdown links matching `[text](path)` where `path` is a
-   relative path (not a URL).
-2. Resolve each relative path from the source file's directory.
-3. Verify the target exists on disk.
-4. **Broken links:** Report and fix. Common fixes include:
-   - Correcting `../` depth for moved files
-   - Updating paths for renamed files
-   - Removing links to deleted files
-
-## Step 5: Enhance Cross-Links
-
-When new or recently changed docs are detected, look for cross-linking opportunities.
-
-1. **Topic-based linking:** Scan existing READMEs for sections that discuss the same topic
-   as a new doc. Where an existing README has a brief treatment of a topic that now has
-   dedicated documentation, add a contextual "See [`/package/`](path) for details" link.
-
-2. **Related Packages sections:** Check if a new README was created for a package that is
-   referenced without a link in another doc's "Related Packages" section. Add the link using
-   the format:
-   ```markdown
-   - [`/package/`](path) - Brief description
-   ```
-
-3. **Be conservative:** Only add links where the existing text already discusses the topic.
-   Do not restructure existing content or add new sections just to create links.
-
-## Step 6: Report
-
-Output a summary organized into these sections:
-
-1. **Index Updates** — `docs/README.md` entries added, updated, or removed.
-2. **Roadmap Updates** — Status changes, new entries, progress notes added.
-3. **Broken Links Fixed** — Source file, broken target, and fix applied.
-4. **New Cross-Links Added** — Source file, target doc, and surrounding context.
-5. **Items Needing Review** — Ambiguities or items requiring human judgment.
-
-If no changes were needed in a category, note "None" for that section.

package/.claude/skills/xh-update-docs/SKILL.md

@@ -1,112 +0,0 @@
----
-name: xh-update-docs
-description: Update hoist-react documentation after adding new components or features. Use when a developer has made changes to hoist-react and wants to update README files, AGENTS.md, and the documentation roadmap to reflect those changes. Invoke with a commit hash or PR number. Also use when you detect that recent commits or PRs have added new components, models, or services that are not yet reflected in the documentation.
-tools: Read, Glob, Grep, Bash, Edit, Write
----
-
-# xh-update-docs — Documentation Update Skill
-
-Update hoist-react documentation to reflect recent code changes. This skill analyzes
-commits or PRs, identifies documentation-worthy changes, and proposes targeted updates
-to package READMEs, AGENTS.md, and the documentation roadmap.
-
-## Step 1: Resolve Input
-
-Accept `$ARGUMENTS` as a commit hash or PR number.
-
-**If arguments are provided:**
-- If it looks like a PR number (digits only, typically 1-5 digits), use `gh pr diff <number>`
-  and `gh pr view <number>` to analyze
-- Otherwise treat it as a commit hash and use `git diff <hash>~1..<hash>`
-
-**If no arguments are provided:**
-- Run `git log --oneline -6` to fetch the last 6 commits
-- Present them to the user via `AskUserQuestion` as selectable options, where each option
-  label is the short hash + commit message
-- The user picks the commit(s) that contain the changes to document
-
-## Step 2: Analyze Changes
-
-Analyze the diff to identify documentation-worthy changes:
-
-1. **Identify new and modified files:**
-   - New files added (new components, models, services)
-   - Modified files (changed behavior, new props/config, new methods)
-
-2. **Determine affected packages:**
-   - Map changed files to packages: `/cmp/`, `/core/`, `/data/`, `/svc/`, `/desktop/`,
-     `/mobile/`, `/admin/`, `/format/`, `/utils/`, etc.
-
-3. **Read source files:**
-   - Don't just rely on the diff — read the actual source files to understand what was
-     added or changed, including class hierarchies and exported APIs
-
-4. **Cross-reference CHANGELOG.md:**
-   - Check `CHANGELOG.md` for entries related to the commit/PR
-   - The changelog uses categorized sections under version headers:
-     `💥 Breaking Changes`, `🎁 New Features`, `⚙️ Technical`, `🐞 Bug Fixes`
-   - Look for entries in the current SNAPSHOT version that describe the change
-   - These provide curated descriptions and are a strong signal of documentation-worthy changes
-
-## Step 3: Inventory Existing Documentation
-
-Check current documentation state for each affected package:
-
-1. **Package READMEs** — Read the relevant README(s) to see what's already documented.
-   Use `Glob` to check for `<package>/README.md` files.
-
-2. **Documentation Index** — Check for existing entries in the `docs/README.md` Package
-   Documentation tables. Read `docs/README.md` and look for the affected package paths.
-
-3. **Documentation Roadmap** — Check `docs/README-ROADMAP.md` for status of affected packages.
-
-## Step 4: Propose Updates
-
-Generate a categorized list of proposed documentation changes. For each change, explain
-**what** would be updated and **why**.
-
-Categories:
-
-### README Updates
-Edits to existing package READMEs. Examples:
-- New section for a newly added component or model
-- Updated configuration table with new properties
-- New usage pattern or code example
-- Updated architecture diagram
-- New entry in Common Pitfalls
-
-### New READMEs
-If a new sub-package was added that lacks a README, propose creating one following the
-7-section structure defined in `references/doc-conventions.md`.
-
-### Documentation Index Updates
-New or updated entries in the `docs/README.md` Package Documentation tables. Each entry needs:
-- Linked package path (relative from `docs/`, e.g., `../package/README.md`)
-- One-sentence description
-- Comma-separated list of key topics
-
-### Roadmap Updates
-Status changes in `docs/README-ROADMAP.md`:
-- New package entries added to the appropriate priority tier
-- Status changes (e.g., `Planned` → `Done` with link)
-- New progress notes with date
-
-## Step 5: Confirm with User
-
-Present the full list of proposed changes in a clear summary. Ask the user to confirm
-before applying any changes. Group by category and include enough context for the user
-to evaluate each proposed change.
-
-## Step 6: Apply Changes
-
-After user confirmation, apply the approved documentation updates using Edit and Write tools.
-
-Follow conventions from `references/doc-conventions.md`:
-- Use the 7-section README structure for new READMEs
-- Use element factory style in code examples (not JSX)
-- Use `config` (not `props`) for model constructor args
-- Fold defaults into description column (no separate Default column)
-- Use ✅/❌ markers for correct/incorrect code patterns
-- Use `**Avoid:**` prefix for inline warnings
-
-After applying changes, present a summary of what was updated.