porting-to-rs

Porting TypeScript to Rust without spec drift requires enforcing a spec-first workflow that reads and implements against the canonical Rust spec document, rather than copying current TS structure. This prevents behavioral divergence during the porting process.

Ensuring concurrency safety when porting to Rust requires strict refcount and lock discipline, forbidding unsafe code, and enforcing sync-only core constraints. These guardrails prevent race conditions and maintain memory safety during parallel execution.

Yes, full-mode Rust porting requires a HALT step for architecture discussion and user approval before any code changes. This ensures deterministic planning and prevents unauthorized modifications to the Rust workspace.

Maintaining parity tests when adding Rust functionality involves running rule-referenced tests, clippy and fmt self-checks, and widening parity-test scenarios when applicable. This ensures the Rust implementation matches canonical spec behavior.

No, the Rust port implementation forbids unsafe code entirely. It enforces sync-only core constraints and strict refcount and lock discipline to guarantee memory safety and concurrency safety without unsafe blocks.

Preventing cross-repo drift when porting to Rust requires using migration-status tracking, porting-deferred lists, flowcharts, and TLA+ research. These tools avoid reintroducing deferred concerns or violating handle-protocol, lock, and refcount invariants.