svelte/migration/component-migration

Replace each store import with slice selectors and action creators, create one readable per selector at component initialization, swap `$foo` template references to `$foo$`, and convert set/update calls into store.dispatch with the appropriate action.

Use the selector's one-shot mode: call selectFoo.select(store.state) with an already-initialized Store instance captured outside the handler. Never call selectFoo() inside a callback, since creating a readable requires component initialization timing.

Readable selector calls like selectDraft() create a subscription that requires component initialization context. Inside callbacks that context is gone, so the call fails. Use selectDraft.select(store.state) for a plain one-shot read instead.

No. Writing to both the legacy writable and dispatching Redux actions creates two state owners, so rollback and selector reads disagree. Each piece of state must have a single owner: dispatch through the configured Store instance only.

Swap store imports for selectors and actions, create readables at init time, rename template references to $foo$, convert mutations to store.dispatch, use select(store.state) for one-shot reads, then re-run the component's existing tests before committing.