Till JS 80dbb3b3b6 feat(spaces): migrate calendar module to scoped-db wrapper (pilot) ... First module to consume the scope layer — proves the model end-to-end on a real query path. Changes in calendar/queries.ts: - db.table('calendars') → scopedForModule<LocalCalendar>('calendar', 'calendars') - db.table('timeBlocks') → scopedForModule<LocalTimeBlock>('calendar', 'timeBlocks') - db.table('events') → scopedForModule<LocalEvent>('calendar', 'events') - applyVisibility() wrapper runs on each read to drop private records authored by other members of a shared space. Scope wrapper tweaks: - getInScopeSpaceIds is now lenient during boot: if no active space has loaded yet, falls back to the user's personal sentinel so sentinel- stamped records from the v28 migration still render. Returns [] only when fully unauthenticated, which yields an empty-match filter. - applyVisibility is no longer generic-constrained — T is inferred exactly as the input type; visibility/authorId are read via runtime duck-typing so arbitrary record shapes pass through cleanly. Known follow-ups: - Root-layout bootstrap (load active space + reconcile sentinels on login) is intentionally not wired up yet — needs a separate pass on the already-crowded (app) layout to avoid collateral damage. - Four legacy tables (conversations, documents, spaceMembers, memoSpaces) carry a pre-existing `spaceId` field that points to the older context-space concept, not our multi-tenancy space. Renaming those to contextSpaceId is a tracked follow-up in the RFC — calendar is unaffected. Plan: docs/plans/spaces-foundation.md (updated with the legacy-spaceId note + lenient-scope rationale). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-20 16:42:10 +02:00
..
landing	docs: add Apr 16 devlog, remove duplicate devlogs, update MODULE_REGISTRY	2026-04-17 15:27:00 +02:00
web	feat(spaces): migrate calendar module to scoped-db wrapper (pilot)	2026-04-20 16:42:10 +02:00