mvsep-rs

Implement one mvsep-rs backend rewrite batch as the code-writing role. Use when the user asks to write code for a selected migration batch, create AppBackend seams, move config/formats/algorithm cache/transfer/tasks to the rewritten backend, or prepare a batch for independent review. Do not use for review-only requests.

Review one mvsep-rs rewrite batch quality gate without writing production code. Use when the user asks for behavior parity review, error tracing review, async or ergonomics review, data structure or algorithm review, Rust style audit, frontend UX audit, or promotion readiness for a mvsep-rs migration batch.

Coordinate the mvsep-rs gradual backend rewrite. Use when the user asks to continue, plan, implement, audit, or route work for replacing the old Tauri backend with the rewritten Rust backend; when updating migration state, project constraints, rewrite docs, or multi-agent rewrite workflow; or when deciding the next mvsep-rs migration batch.