chore(deps): align dependencies with upstream, including two majors

[IgorShevchik]

Port of nuxt/ui@6bcc97a6 (nuxt/ui#6849). First of six in the current queue.

Taken as an alignment to upstream's versions rather than a replay of the deltas, per instruction — this fork had drifted behind on several packages, so what upstream shipped as a non-major batch includes two major jumps here.

package	ours before	now	note
ai	^6.0.214	^7.0.66	major
@ai-sdk/vue	^3.0.214	^4.0.66	major
@regle/core, @regle/rules	^1.28.0	^1.29.1	we were behind upstream's pre-image too
@nuxtjs/mcp-toolkit	^0.18.1	^0.19.0
@unhead/vue, magic-string, motion-v, ohash, vue-component-type-helpers, vue-tsc, @shikijs/types, shiki, vue-component-meta	—	—	patch/minor, matched upstream

Per PORTING.md §2 the manifests mirror across all b24ui playgrounds, not the two upstream has. playgrounds/demo carries ai, @ai-sdk/vue and vue-tsc and moves with the rest — its vue-tsc sat further behind than everything else at ^3.3.7, which only a per-playground pass finds. playgrounds/repl carries none of them.

One bump held back: nuxt-schema-org

Stays at ^6.2.1. Not a judgement call — the newer versions do not run:

[error] (0 , _kit3.useModuleLogger) is not a function
    at setup (nuxt-schema-org@6.2.9/dist/module.mjs:98:46)

The cause is transitive, not direct, and finding that out took two wrong guesses worth recording:

1. First read was "nuxt-schema-org@6.2.9 is broken against @nuxt/kit@4.5.2". Checking every published version 6.2.1…6.2.9 against the 98 names our kit exports showed none of them import a missing symbol — so the direct dependency is fine.
2. Pinning 6.2.7 then failed one function earlier, on setupNitroRuntimeCompatibility. That is what identified the real constraint: nuxt-site-config. Any bump above 6.2.1 drags it from 4.0.8 to 4.2.3, and 4.2.3 is what calls both functions.

Neither exists in @nuxt/kit@4.5.2, and 4.5.2 is the newest published 4.x — there is no Nuxt version available today that would fix this.

Upstream has the same defect and does not see it. Their lockfile at this commit resolves nuxt-schema-org@6.2.9 on the same @nuxt/kit ^4.5.2. It stays latent because neither CI builds the docs site; here it surfaced in dev:prepare, which prepares docs/ too.

One mechanical note for the next porter: restoring the caret alone was not enough. ^6.2.1 is satisfied by 6.2.7, so pnpm kept the newer resolution and the failure persisted. The lockfile had to be restored from HEAD before reinstalling — after which the manifest entry is byte-identical to before and the resolution is back to 6.2.1 with nuxt-site-config@4.0.8.

Verify (CI=true)

dev:prepare (all four apps) · lint · typecheck · test · build · docs:generate — all green. Tests 6546 passed | 6 skipped across 288 files. 1240 routes prerendered.

typecheck carries the weight for the two majors: it runs nuxt typecheck over docs/, and every ai / @ai-sdk/vue call site lives there — docs/server/api/{ai,chat,completion}.post.ts, docs/modules/bx-assistant/*, and the chat/ and editor/ examples.

Caveat, stated rather than glossed

The AI features compile and prerender, but their runtime paths were not exercised. docs:generate runs with NUXT_PUBLIC_USE_AI=false and no DEEPSEEK_API_KEY, so the assistant is disabled during the build. A v7 behavioural change inside a request handler would not surface in any check run here. Worth a manual pass against a real key before relying on it.

Ledger

cursor → 6bcc97a6, entry added, log at .sync/log/6bcc97a6….md. pr/b24ui_sha are pending-merge, reconciled by the next commit in the queue.

Remaining: ccd48940 (Windows path expectations — applies verbatim, our components.spec.ts has the same defect), f065438d (reka-ui 2.10.3), f3c2ac21 (the Slider fix — applies, as Range; see #423), cf5f15e3 and f6d188bd (showcase; the second has a schema half worth taking).

---

Generated by Claude Code