Svelte 5 Deep-Proxy Signal Barrier for Web Worker Structured Clones

--- description: Svelte 5 Deep-Proxy Signal Barrier for Web Worker Structured Clones - Svelte 5 wraps reactive objects created via `$state` in deep reactivity proxies tightly coupled to the Universal Signal runtime graph. Passing or serializing these proxies directly across Web Worker boundaries triggers DataCloneError exceptions or corrupts reactivity tracking, causing permanent state desynchronization. All state exiting or entering thread contexts must traverse an explicit barrier via `$state.snapshot()`. globs: src/**/*.{svelte,svelte.ts,ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-worker-proxy-transfer-barrier" --- # Svelte 5 Deep-Proxy Signal Barrier for Web Worker Structured Clones > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Direct Inter-Thread Serialization of Svelte 5 Live Signal Proxies via postMessage or structuredClone ## System Constraints You are a Principal Engineer enforcing strict memory isolation and reactivity invariants in Svelte 5. Svelte 5 deep-proxy runes ($state) cannot cross thread boundaries via postMessage, structuredClone, or worker communication channels without corrupting signal graphs or throwing DataCloneError. Mandate the use of $state.snapshot() before outbound serialization, and re-instantiation of runes upon inbound worker receipt. ## Strict Guidelines - Engineers MUST ALWAYS invoke `$state.snapshot()` on any Svelte 5 reactive object or collection prior to passing it to `worker.postMessage()`, `structuredClone()`, or Comlink RPC channels. - Engineers MUST NOT pass raw `$state()` or `$state.raw()` proxies into inter-thread message ports, transfer lists, or Worker constructors. - Engineers MUST re-hydrate incoming Worker payload transfers into fresh `$state()` instances within the consumer module if UI reactivity is required. - Worker boundaries MUST enforce a typed Data Transfer Object (DTO) schema using standard interfaces without Svelte Rune symbol metadata. - Components and domain stores NEVER pass reactive state directly into OffscreenCanvas or background computational task pools without traversing an isolated barrier function. ## Bad vs Good Implementations ### Enforcing $state.snapshot() Transfer Barrier on Worker Dispatch #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: In Svelte 5, `$state` returns a deep reactive proxy registered in the active signal graph. Calling `worker.postMessage` directly on `this.taskState` invokes the Structured Clone algorithm on an active proxy with runtime signal tracking symbols, causing `DataCloneError` in compliant browsers or breaking the reactivity graph upon mutation. ```typescript import { workerPool } from './worker-pool'; interface TaskState { id: string; computations: number[]; status: 'idle' | 'running' | 'done'; } // Anti-pattern: Sending live reactive proxy directly to Web Worker export class TaskCoordinator { private taskState = $state<TaskState>({ id: 'tx-1001', computations: [10, 20, 30], status: 'idle' }); public runWorkerCalculation(worker: Worker): void { this.taskState.status = 'running'; // CRITICAL BUG: taskState is a deep signal proxy. // Throws DOMException: DataCloneError or causes reactivity desync. worker.postMessage({ type: 'EXECUTE', payload: this.taskState }); } } ``` #### Production Standard (Correct) > **Standard**: Invoking `$state.snapshot(this.taskState)` severs the reactive signal bindings and produces a pristine, un-proxied JavaScript object. This guarantees safe traversal across the Web Worker Structured Clone boundary while preserving type safety and preventing runtime exceptions. ```typescript import { workerPool } from './worker-pool'; interface TaskState { id: string; computations: number[]; status: 'idle' | 'running' | 'done'; } type TaskDTO = Readonly<TaskState>; // Production standard: Strict snapshot barrier before thread traversal export class TaskCoordinator { public taskState = $state<TaskState>({ id: 'tx-1001', computations: [10, 20, 30], status: 'idle' }); public runWorkerCalculation(worker: Worker): void { this.taskState.status = 'running'; // Snapshot strips proxy metadata and returns a deep raw clone safe for cloning const serializedPayload: TaskDTO = $state.snapshot(this.taskState); worker.postMessage({ type: 'EXECUTE', payload: serializedPayload }); } public handleWorkerResult(event: MessageEvent<{ computations: number[] }>): void { // Re-bind inbound static plain object into Svelte's reactive graph this.taskState.computations = event.data.computations; this.taskState.status = 'done'; } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Deep-Proxy Signal Barrier for Web Worker Structured Clones

Svelte 5 Deep-Proxy Signal Barrier for Web Worker Structured Clones defines an industrial-grade behavioral standard for frontend engineering. Svelte 5 wraps reactive objects created via `$state` in deep reactivity proxies tightly coupled to the Universal Signal runtime graph. Passing or serializing these proxies directly across Web Worker boundaries triggers DataCloneError exceptions or corrupts reactivity tracking, causing permanent state desynchronization. All state exiting or entering thread contexts must traverse an explicit barrier via `$state.snapshot()`. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Direct Inter-Thread Serialization of Svelte 5 Live Signal Proxies via postMessage or structuredClone Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Direct Inter-Thread Serialization of Svelte 5 Live Signal Proxies via postMessage or structuredClone	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS invoke `$state.snapshot()` on any Svelte 5 reactive object or collection prior to passing it to `worker.postMessage()`, `structuredClone()`, or Comlink RPC channels.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.