Johannes Millan cbeecfd39a fix(sync): multi-tab vector clock staleness + shared code extraction ... Bug fix: - Fix vector clock cache staleness in multi-tab scenarios by clearing cache when acquiring operation write lock. Each browser tab has its own in-memory cache, so Tab B's cache could be stale if Tab A wrote while Tab B was waiting for the lock. Shared code extraction (client/server consistency): - Extract vector clock comparison to @sp/shared-schema - Client wraps shared impl with null handling - Server imports directly from shared - Extract entity types to @sp/shared-schema - Single source of truth for ENTITY_TYPES array - Removes duplicated "must match" comments Files: - packages/shared-schema/src/vector-clock.ts (new) - packages/shared-schema/src/entity-types.ts (new) - src/app/op-log/store/operation-log-store.service.ts (cache clear) - src/app/op-log/capture/operation-log.effects.ts (call cache clear)		2026-01-03 18:05:11 +01:00
..
src	fix(sync): multi-tab vector clock staleness + shared code extraction	2026-01-03 18:05:11 +01:00
tests	feat(sync): add shared schema versioning package for frontend/backend	2025-12-12 20:47:44 +01:00
.gitignore	feat(sync): add shared schema versioning package for frontend/backend	2025-12-12 20:47:44 +01:00
package.json	fix: address code review findings from last 24 hours	2025-12-12 20:47:47 +01:00
tsconfig.json	fix: address code review findings from last 24 hours	2025-12-12 20:47:47 +01:00
vitest.config.ts	feat(sync): add shared schema versioning package for frontend/backend	2025-12-12 20:47:44 +01:00