chore(sync): reconcile the e2a253ec, d4f2ca02 and a7f26a32 entries with #455

.sync/nuxt-ui.json

@@ -1585,20 +1585,20 @@
       "summary": "docs(table): pin TanStack Table links to v8 (nuxt/ui #6864) — PORT, applies in full minus a page we lack. Upstream rewrites every tanstack.com/table/latest to /table/v8 because latest now resolves to a major the documented API no longer matches, widens two labels to name the version, and corrects one link: the column-pinning section pointed at the row-pinning API. Applies here for the same reason, checked not assumed — this fork depends on @tanstack/vue-table ^8.21.3, so every latest link documents an API our Table does not implement. 18 links across two files: docs/content/docs/2.components/table.md (17) and skills/b24-ui-nuxt/references/recipes/data-tables.md (1); both labels widened as upstream did. We inherit the mislabelled link too — our line 523 in 'With column pinning' read '[Pinning APIs](…/features/row-pinning)' and is now '[Column Pinning APIs](…/features/column-pinning)'. Worth noting because it is a content error rather than a version pin, and a sweep of latest -> v8 alone would have carried it forward. Not applicable: docs/content/docs/1.getting-started/3.migration/2.v3.md — our migration directory holds only 1.v2.md, this fork has no v3 migration page. Verified with lint, test and docs:generate; documentation only, zero /table/latest remain and 18 /table/v8."
     },
     "e2a253ec9496efa5ac3c7b9635ccf20a3458a704": {
-      "pr": "pending-merge",
-      "b24ui_sha": "pending-merge",
+      "pr": 455,
+      "b24ui_sha": "3b1b017e6e204274ca4eead3ae2fa9e03d05e879",
       "decision": "port",
       "summary": "docs(header): prevent focus on toggle button animations (nuxt/ui) — PORT of the half that exists here. Upstream swaps class=\"outline-none\" for tabindex=\"-1\" on the three motion.line elements of the animated hamburger icon, in two files. The two attributes are not variants of each other: outline-none hides the focus ring and leaves the element in the tab order, so the lines stayed focusable and the only evidence of it disappeared; tabindex=\"-1\" removes them from it, which is the intent — an SVG line inside a button is decoration. Only docs/app/components/content/examples/header/HeaderToggleAnimatedExample.vue exists in this fork; there is no HeaderToggleButton.vue under docs/app/components/content/, and searching for motion-v across docs/app, playgrounds and src returns exactly two files — this example and src/runtime/components/prose/Img.vue, whose Motion usage has neither outline-none nor focusable children. The example is structurally identical to upstream's down to the :variants/:animate/:custom triple and the 1/2/3 indices, so the swap is verbatim on all three elements."
     },
     "d4f2ca02322cd9ad5b2c2fe235aa445f88042997": {
-      "pr": "pending-merge",
-      "b24ui_sha": "pending-merge",
+      "pr": 455,
+      "b24ui_sha": "3b1b017e6e204274ca4eead3ae2fa9e03d05e879",
       "decision": "port",
       "summary": "fix(theme): replace deprecated bare tailwind aliases (nuxt/ui #6865) — PORT, adapted: one of the two renames is not value-preserving in this fork. Tailwind v4 keeps the v3 bare spellings as deprecated aliases and upstream replaces the two it used — backdrop-blur -> backdrop-blur-sm and rounded -> rounded-sm — across six theme files. The catch is that the bare aliases are hardcoded while the named ones read a theme variable. Compiled with this repo's own Tailwind 4.3.3: .backdrop-blur emits blur(8px), .backdrop-blur-sm emits blur(var(--blur-sm)); .rounded emits 0.25rem, .rounded-sm emits var(--radius-sm). --blur-sm is Tailwind's own 8px and this fork does not override the blur scale, so the first rename is exact. --radius-sm is 8px here: src/runtime/air-design-tokens/tw-style/radius.css replaces the whole radius scale with the Air design system's, so taking upstream's line verbatim would have doubled the corner radius on every InputDate and InputTime segment. The same file defines --radius-2xs: 4px, which is what bare rounded emits, so rounded-2xs is the value-preserving name — and it matches the design system's own field radius, --ui-field-border-radius: var(--ui-border-radius-2xs), also 4px. A deprecation cleanup preserves the value, not the class name. Applied to every bare occurrence in the fork, which is a larger set than upstream's because two files are fork-local: header.ts (1), table.ts (4), table-wrapper.ts (6, one inside a commented line, changed with the rest so the comment does not read as a different rule), input-date.ts (1), input-time.ts (1), plus two docs examples carrying the same aliases (ScrollAreaExternalScrollExample, useConfettiCustomPlaceExample). chat-prompt.ts and content/content-toc.ts need nothing — neither of our copies contains backdrop-blur. Deliberately not touched: bare `ring`, which is not deprecated in v4 (.ring and .ring-1 compile identically, verified in the same probe), and outline-none, which in v4 is a real utility meaning outline-style: none — upstream's commit does not touch either. Verified by compiling a probe stylesheet and reading the emitted declarations rather than by trusting the upgrade guide, and by the generated docs CSS, where --blur-sm:8px and --radius-sm:8px are what the site ships; snapshots moved 814 lines removed / 814 added, and after normalising the two renamed tokens zero lines differ."
     },
     "a7f26a320535da1fbe77a7066e53386423da4d3a": {
-      "pr": "pending-merge",
-      "b24ui_sha": "pending-merge",
+      "pr": 455,
+      "b24ui_sha": "3b1b017e6e204274ca4eead3ae2fa9e03d05e879",
       "decision": "no-op",
       "summary": "docs(showcase): add brusnika-lms.com (nuxt/ui #6863) — NO-OP: four lines in docs/content/showcase.yml plus a screenshot, adding a site built with Nuxt UI to their gallery. This fork keeps its own showcase.yml listing sites built with Bitrix24 UI, so the entry is content, not code. Same call as d0cfc2b1, 78cc1ce5, cf5f15e3, 2beb2345 and a630c943. The one showcase commit that was not a no-op is f6d188bd, which introduced the screenshotOptions field — shared schema. This commit uses that field rather than introducing it, and screenshotOptions is already supported here (docs/modules/showcase.ts and docs/content.config.ts both carry it), so nothing structural is left to take."
     }