managarten/apps/mana/apps/web/src/lib/modules/context
Till JS 636138b2d4 refactor(scope): replace _scopeCursor bridge with reactive useScopedLiveQuery hook
The previous fix wired Dexie's `_scopeCursor` infra-table as a side-
channel between Svelte $state (active-space + current-user) and Dexie
liveQuery: every scoped query touched the table on read so liveQuery
subscribed to it, every setActiveSpace bumped the table so liveQuery
re-ran. Worked, but smelled — hidden side-effect inside `scopedTable`,
scope state pretending to be a Dexie row, +1 roundtrip per query, and
`current-user.ts` had to dynamic-import Dexie just to pump the bridge.

Replacement: a Svelte 5 `$effect`-based hook that owns scope-tracking
explicitly. The dependency now lives in the reactive layer (which is
where it belongs), not as a side-effect in the data layer.

What changes:

- New `data/scope/use-scoped-live-query.svelte.ts`. The hook reads a
  module-level `scopeTick` `$state` counter inside its `$effect`.
  Both `onActiveSpaceChanged` (existing) and `onCurrentUserChanged`
  (new, added to `current-user.ts`) bump the tick on real changes.
  Effect re-fires → previous Dexie subscription unsubscribes → fresh
  one created with up-to-date `getInScopeSpaceIds()`. Same return
  shape as `useLiveQueryWithDefault` for drop-in migration.

- `current-user.ts` gains an `onCurrentUserChanged` event bus,
  symmetric to `active-space.svelte.ts#onActiveSpaceChanged`. Stays
  a plain `.ts` (no runes) so it remains a leaf and works in the
  test runner without the Svelte preprocessor — the rename to
  `.svelte.ts` was tried earlier and reverted because of test
  fallout (commit `01e6b9f04`).

- 53 module `queries.ts` files migrated from
  `useLiveQueryWithDefault` → `useScopedLiveQuery`. The choice of
  hook now documents at the call-site whether the query is
  scope-aware. Pure mechanical find-replace — no logic changes.

What goes away:

- `data/scope/cursor.ts` deleted.
- `touchScopeCursor()` calls removed from `scopedTable` /
  `scopedAnd` / `scopedGet`. Functions are pure data-layer again,
  no implicit reactive subscriptions.
- `bumpScopeCursor()` calls removed from `setActiveSpace` and both
  `loadActiveSpace` branches. Setter is pure state-update, no
  Dexie write side-effect.
- `current-user.ts` no longer dynamic-imports `scope/cursor` —
  `setCurrentUserId` is a clean three-line setter again.
- Dexie v46 drops the `_scopeCursor` table (`stores: { _scopeCursor:
  null }`). v45 stays declared so existing browsers' version chain
  remains contiguous; the v46 deletion runs once on next open. No
  user data lost — the table only ever held a transient bumpedAt
  row.

Existing 14 scope regression tests still pass. Type-check + theme-
token validators are clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 12:15:22 +02:00
..
stores feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
collections.ts feat(spaces): rename legacy spaceId → contextSpaceId (v31 migration) 2026-04-20 19:52:44 +02:00
index.ts fix(mana/web): clear remaining type errors — long-tail sweep 2026-04-09 20:25:08 +02:00
ListView.svelte refactor(theming): migrate 6 ListViews + ai-missions badges to theme tokens 2026-04-22 15:23:55 +02:00
module.config.ts fix(mana/web): commit module-registry + module.config.ts files (build-critical) 2026-04-07 19:49:58 +02:00
queries.ts refactor(scope): replace _scopeCursor bridge with reactive useScopedLiveQuery hook 2026-04-25 12:15:22 +02:00
types.ts feat(spaces): rename legacy spaceId → contextSpaceId (v31 migration) 2026-04-20 19:52:44 +02:00