Marinara-Engine-Refactor

Apply Marinara's repo-local version of the Chai agent workflow pack for proof discipline, investigations, feature sizing, refactor handoffs, reviews, PR readiness, reviewer feedback iteration, issue drafting, UI/UX proof, security-sensitive checks, risky-work evidence, debt notes, and final status reports. Use for nontrivial coding work, ambiguous symptoms, refactors, reviews, PR/issue workflows, or any task where an agent must prove claims while preserving Marinara's code separation and module ownership rules.

Onboard developers and coding agents into Marinara. Use when someone asks how to get started, asks for a repo tour, wants the docs run, needs to run/build the app, wants a first testing checklist, or wants a guided workflow for finding and fixing bugs in this repo.

Protect Marinara's layered Tauri and hostable Rust runtime architecture, module ownership, dependency direction, explicit imports, Rust capability boundaries, shared-code placement, HTTP pipeline, and file-splitting discipline. Use when changing folders, imports, shared modules, TypeScript engine layers, Tauri/HTTP command wrappers, Rust capability crates, repositories, adapters, feature APIs, or any code structure that could widen impact area.

Guide Marinara bug fixes toward root-cause repairs with clear impact areas, focused commits, validation, and no band-aid patches. Use for regressions, broken UI actions, failing checks, provider/transport bugs, storage bugs, import/export bugs, generation bugs, mode behavior bugs, and any change where the fix could affect dependent modules.

Enforce Marinara's strict separation between chat/conversation, roleplay, and game mode. Use when changing mode engines, mode UI, autonomous chat, schedules, summaries, roleplay scenes, sprites, encounters, visual novel choices, game turns, game prompts, game state, generation guide routing, prompt assembly, or any shared code that could affect more than one mode.