docs(sync): register new components in every docs and playground registry

[IgorShevchik]

Linked issue

Follow-up to #441 (Splitter) and #443 (ProgressGroup).

Type of change

• Documentation (updates to the documentation or readme)
• Chore (updates to the build process or auxiliary tools and libraries)

Description

Splitter and ProgressGroup each shipped with src/, tests, a docs page and the nuxt playground — and each was missing four further registries. None of them can fail a build, which is why both ports passed the full gate twice with the gaps in place.

docs/nuxt.config.ts → pages. Neither route was listed. The page still prerenders, because the crawler follows the sidebar link, so nothing looked wrong. But that array is the declared list the /raw/<page>.md routes are generated from (@memo need add pages for raw/***.md), and skills/b24-ui-nuxt/references/components.md links to exactly those URLs. Writing the guard below turned up two older instances of the same omission — empty and page-card-group — both registered here as well.

playgrounds/demo. No page for either component, so the Demo link a docs page is supposed to carry had nothing to point at. Both are written the way the other 79 demo pages are — <PlaygroundPage> with #controls, the theme's variants driven through <Matrix> — rather than copied over from the nuxt playground, which is a scratch page with a different job. Both names added to the demo useNavigation.ts in place, and the Demo link added to both docs pages.

Front matter. description: was Nuxt UI's sentence verbatim on Splitter and near-verbatim on ProgressGroup; both rewritten, keywords: added. Splitter's Reka link used iconName: RekaIcon, a name that has never existed in src/runtime/dictionary/icons.ts — resolveIcon() returns undefined for it and the template renders the link with no icon, silently. The convention on the other 34 pages is an avatar, /b24ui/avatar/rekaui.svg, and that is what it uses now.

test/utils/docs-component-registries.spec.ts holds the mechanically checkable part: page ↔ pages entry in both directions, every iconName: on a component page resolvable in the dictionary, every Demo link and every demo nav entry resolving to a file that exists. It deliberately does not demand a demo page per component — 33 of 120 pages carry no Demo link by choice — and it cannot tell a rewritten description from a copied one. Those stay checklist items, which .sync/PORTING.md §6 now spells out as eleven places a new component has to appear.

Verification

• Four mutations against the new spec, each red: dropping the splitter route, adding a route with no page behind it, restoring iconName: RekaIcon, renaming the demo page away. Green on the tree as committed.
• Gate with CI=true: dev:prepare · lint · typecheck · test (6804 passed) · build, plus docs:generate with deploy.yml's env (1259 routes) and demo:generate (87 routes).
• Both demo pages loaded in a browser off demo:generate's output — the demo app is ssr: false, so a prerendered shell proves nothing: the splitter renders two panel groups, the progress group six segments, no console errors.

Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

---

Generated by Claude Code