chore(deps): update reka-ui to 2.10.5 (nuxt/ui@8034f83)

.sync/dep-parity.json

@@ -1,6 +1,6 @@
 {
   "$note": "Upstream's pinned versions for every dependency both trees declare in the SAME section, snapshotted at `cursor`. The sync ports deltas, which is correct per commit and lets a one-time divergence become permanent: once a version is off upstream's line, every later `chore(deps)` batch skips it, because those ports bump only where this fork already matched upstream's pre-image. `prettier` sat at ^3.8.4 against upstream's ^3.9.6 for that reason, through four ported batches, until this file was written. Section-aware on purpose: 18 packages are declared on both sides but in different sections — the whole `@tiptap/*` family is a peer `^3` upstream and a dependency `^3.29.2` here, and `ai` is a peer there and a devDependency here. Those are structural divergences, not drift, and comparing a peer range against a dependency range says nothing. They are absent from this file by construction rather than by omission. Guarded by `test/utils/dep-parity.spec.ts`. Refresh with `node .sync/dep-parity.mjs <path-to-nuxt-ui-mirror> [cursor]`, which preserves `exceptions`.",
-  "cursor": "7f0250eab69d04c42e137aa85c103e3dc83eec60",
+  "cursor": "8034f8371de179ec939ed559fd9a4748b79fd454",
   "manifests": {
     "package.json": {
       "dependencies": {
@@ -53,7 +53,7 @@
         "motion-v": "^2.4.4",
         "ohash": "^2.0.12",
         "pathe": "^2.0.3",
-        "reka-ui": "2.10.4",
+        "reka-ui": "2.10.5",
         "scule": "^1.3.0",
         "tailwind-merge": "^3.7.0",
         "tailwind-variants": "^3.2.2",

.sync/log/8034f8371de179ec939ed559fd9a4748b79fd454.md

@@ -0,0 +1,54 @@
+# port — nuxt/ui@8034f8371de179ec939ed559fd9a4748b79fd454
+
+**Upstream:** chore(deps): update pnpm.catalog.default reka-ui to v2.10.5 (#7017)
+
+**Decision:** port — `reka-ui` is exact-pinned here *because* upstream pins it
+(PORTING §2, AGENTS.md "Dependency pins are not ours to move"); it moves only
+through a port like this one. The catalog line matched upstream's pre-image
+(`reka-ui: 2.10.4`), and the change is the same single line.
+
+## Lockfile
+
+The lockfile delta is exactly `reka-ui@2.10.4` → `reka-ui@2.10.5`: no other
+package version added or removed, 9 insertions / 9 deletions — the same size as
+upstream's own lockfile diff for this commit. `pnpm install --frozen-lockfile`
+passes.
+
+## Release-age policy
+
+Checked before installing, since PORTING §2 warns that `pnpm` silently appends a
+too-young version to `minimumReleaseAgeExclude`. `reka-ui@2.10.5` was published
+2026-09-21T13:18Z, three and a half days before this port, and
+`pnpm-workspace.yaml` is byte-identical after `pnpm install` apart from the
+catalog line itself — no exclusion was written.
+
+## What 2.10.5 touches
+
+A patch release, but a wide one. Comparing the two published tarballs'
+`dist/` (source maps excluded), the changed areas are `shared`, `Tree`,
+`Tooltip`, `Listbox`, `Drawer`, `Dialog`, `Select`, `PinInput`, `NumberField`,
+`Menu`, `DismissableLayer`, `Collection`, `utils` and `date`. Mapped onto the
+components here, by what each imports from `reka-ui`: `Modal` and `Slideover`
+(Dialog), `Tooltip`, `Select`, `CommandPalette` and `Listbox` (Listbox),
+`PinInput`, `InputNumber` (NumberField), `DropdownMenu` and `ContextMenu` (reka
+builds both on its Menu), and `Drawer`, which goes through `vaul-vue` and so
+renders reka's Dialog rather than reka's own Drawer. Reka's `Tree` has no
+counterpart in this fork. With that spread, the full suite — snapshots
+included — is the actual check on this port, not a formality.
+
+## Observed, not changed
+
+A second copy, `reka-ui@2.9.9`, is in the tree and was before this port. It is
+not the library's: `pnpm why` traces it to the docs site only —
+`nuxt-schema-org@6.2.1` → `nuxtseo-layer-devtools@5.3.0` → a bundled
+`@nuxt/ui@4.8.2`. `nuxt-schema-org` is held at `^6.2.1` by a written
+`dep-parity` exception, so this copy goes when that hold is lifted, not here.
+
+## Result
+
+The full gate with `CI=true` — `dev:prepare` · `lint` · `typecheck` · `build` ·
+`test:coverage` (365 files, 8205 passed, 6 skipped) · `test:module` — is green,
+and **no snapshot changed**: under `CI=true` vitest fails a mismatch rather than
+writing it, and the tree was clean afterwards. So 2.10.5's changes to Dialog,
+Tooltip, Listbox, Select, PinInput, NumberField and Menu alter no markup any
+component here renders in its specs.

.sync/nuxt-ui.json

@@ -1,7 +1,7 @@
 {
   "upstream": "nuxt/ui",
   "branch": "v4",
-  "cursor": "7f0250eab69d04c42e137aa85c103e3dc83eec60",
+  "cursor": "8034f8371de179ec939ed559fd9a4748b79fd454",
   "_cursor_note": "cursor = last upstream commit ported into b24ui. The sync is manual by decision: one commit at a time, oldest-first, each with a `.sync/log/<sha>.md` journal and an entry in `processed`. There is no dispatcher, no porter workflow and no kill-switch — `.sync/PORTING.md` is the whole procedure. `processed` is maintained per port (backfilled #68-#72 on 2026-06-09).",
   "processed": {
     "2799fa6f2b25ce3eb15e050f3ef7c57d0d9a2fdb": {
@@ -2225,6 +2225,12 @@
       "b24ui_sha": "fab024e2",
       "decision": "port",
       "summary": "fix(EditorToolbar): use tooltip text as `aria-label` on icon-only buttons (#7009) — an icon plus a tooltip, the documented configuration, left the button with no accessible name, since a tooltip never reaches assistive technology. Adds `'aria-label': baseProps.label ? undefined : item.tooltip?.text` to `getButtonProps`' defaults. Adapted: this fork's toolbar has no `variant`/`activeVariant`, so the key went into the fork's own defaults object. Upstream's tests added first with `@bitrix24/b24icons-vue` icons: 4 red before the fix. Mutations removing the label guard or letting the tooltip override an author's `aria-label` are each caught."
+    },
+    "8034f8371de179ec939ed559fd9a4748b79fd454": {
+      "pr": "pending-merge",
+      "b24ui_sha": "pending-merge",
+      "decision": "port",
+      "summary": "chore(deps): update pnpm.catalog.default reka-ui to v2.10.5 (#7017) — `reka-ui` is exact-pinned here because upstream pins it and moves only through a port; the catalog line matched upstream's pre-image. Lockfile delta is exactly `reka-ui@2.10.4` → `2.10.5`, same 9+/9- size as upstream's, and `--frozen-lockfile` passes. Release-age checked first: 2.10.5 was published 2026-09-21, so no `minimumReleaseAgeExclude` entry was written. A wide patch — the tarball diff touches Tree, Tooltip, Listbox, Drawer, Dialog, Select, PinInput, NumberField, Menu, DismissableLayer and Collection — so the full suite with snapshots is the real check. The pre-existing `reka-ui@2.9.9` copy belongs to the docs site's `nuxt-schema-org` devtools layer, not the library."
     }
   }
 }

pnpm-workspace.yaml

@@ -120,7 +120,7 @@ catalog:
   pathe: ^2.0.3
   playwright-core: 1.56.1
   prettier: ^3.9.8
-  reka-ui: 2.10.4
+  reka-ui: 2.10.5
   scule: ^1.3.0
   shiki: ^4.4.3
   shiki-transformer-color-highlight: ^1.1.0