Till JS ad5e04a554 feat(sync): F2 — origin-gated conflict-detection ... Closes the false-positive conflict-toast loop on history-replay. Conflict notifications now fire only when the local field meta records origin='user' AND the pull is not an initial hydration round. Origin source-of-truth: - shared-ai/field-meta.ts → originFromActor(actor) maps actor.kind onto the FieldOrigin enum: user→'user', ai→'agent', system+SYSTEM_MIGRATION →'migration', any other system source→'system'. - Dexie creating/updating hooks call it once per write so every persisted field carries the right pipeline tag. - repair-silent-twin + legacy-avatar wrap their writes in runAsAsync(makeSystemActor(SYSTEM_MIGRATION, ...)) so the hook stamps origin='migration'. Future replays of those rows from another device will not surface as conflicts. applyServerChanges options: - New ApplyServerChangesOptions { isInitialHydration?: boolean }. - Push-response and pull-paged-loop callers compute it from the cursor state (`!oldestCursor` / `!cursor`). Pagination resets the flag after the first page. - Conflict-trigger gates on `!options.isInitialHydration && localMeta[k] ?.origin === 'user'` in addition to the prior tests. Tests (sync.test.ts): - New: replay-burst (10 sequential server updates → 0 conflicts) - New: agent-origin local write + server overwrite → 0 conflicts - New: isInitialHydration suppresses everything → 0 conflicts - New: real user edit + server overwrite → 1 conflict - All 25 prior tests still pass. 29/29 vitest sync.test.ts cases green; svelte-check 0 errors over 7647 files. Plan: docs/plans/sync-field-meta-overhaul.md F2 done-criteria met. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-26 21:38:56 +02:00
..
src	feat(sync): F2 — origin-gated conflict-detection	2026-04-26 21:38:56 +02:00
package.json	feat(shared-ai): extract planner + mission types to @mana/shared-ai	2026-04-15 00:01:57 +02:00
tsconfig.json	feat(shared-ai): extract planner + mission types to @mana/shared-ai	2026-04-15 00:01:57 +02:00