Knowledge sync, EventV2 authority, registry, and eviction invariants

Sync flows only through EventV2 publication and replay, which owns sequencing, claiming, persistence, recovery, and projections; avoid ad hoc bus publication or sync-owned writes. Keep persistence enabled for remote sync or replay participants. Sync only temporal messages referenced by distillations. Never push scope_id; remote conflict keys use server-derived scope and table IDs. Remote temporal application must reject ownership collisions, atomically upsert archived content and queue work under suppression, preserve local distilled/restored state, invalidate vectors only for changed content, and strip boundary-only columns. Eviction and dead-entry pruning may remove only unpromoted project-scoped knowledge, never promoted or cross-project rows; eligibility starts below confidence 0.2. Guard idle sweeps, freeze shared memoized arrays, and run registry contract tests for synced tables, migrations, and agents.