fix(createRegistry): skip values/keys/entries cache when reactive

[johnleider]

Summary

Skip the keys() / values() / entries() cache in createRegistry when the registry is created with reactive: true. The cache was silently dropping Vue's iteration dependency on warm re-runs, so a computed iterating a reactive registry would lose its Map-iteration dep after any re-run that hit the cache — subsequent mutations then failed to propagate.

Background

Alternative fix for the bug in #208. That PR works around the symptom by mutating the existing ticket in `upsert` via `Object.assign` so its `shallowReactive` proxy fires — which happens to land on a different live dep path (per-ticket `.value`). The underlying iteration-dep hole stays open for any other consumer.

This PR fixes the hole at the source:

• `reactive: true` now does what its JSDoc promises — iteration reactivity included.
• `upsert`'s existing replace-the-object behavior is fine; no change needed there.
• Every `reactive: true` consumer (`useNotifications`, `createInput`, `createForm`, `createBreadcrumbs`) benefits from the same fix.

Why the cache broke dep tracking

function values (): readonly E[] {
  const cached = cache.get('values')
  if (!isUndefined(cached)) return cached as readonly E[]  // no reactive read
  const values = Array.from(collection.values())           // reactive read
  cache.set('values', values)
  return values
}

Vue's computed re-tracks deps on every run. When a computed iterated `values()`:

• Cold cache → `Array.from` on the `shallowReactive` Map forms an iteration dep.
• Warm cache → early return, no iteration, no dep.

`select()` doesn't `invalidate()`, so any re-run triggered by a ref change after the initial render dropped the iteration dep. Subsequent `upsert`s then had nothing listening.

Reactive consumers tend to have small collections (UI state), so skipping the cache in that mode has negligible cost. Non-reactive registries keep the cache unchanged.

Follow-ups (separate PRs)

• `useTheme` — enable `reactive: true` internally so consumers don't have to opt in.
• `useLocale` — same.
• `useFeatures` — same; `variation()` currently reads through a non-reactive registry.

[pkg-pr-new]

Open in StackBlitz

commit: ca8e4f3