mwart-process

What problem does it solve?

Prevents breaking changes and inconsistent UI outcomes when migrating legacy Blade screens to the oimpresso MWART Inertia/React architecture by enforcing a single, mandatory 5-phase path.

Core Features & Use Cases

• End-to-end migration guardrails (MWART canônico, único caminho): enforces the required sequential phases PLAN → BACKEND BASELINE → FRONTEND INCREMENTAL → QA → CUTOVER, with explicit denial of premature edits.
• Safe enforcement before code changes: blocks any Edit/Write to resources/js/Pages/<Mod>/<Tela>.tsx or controllers calling Inertia::render(<Mod>/<Tela>) unless RUNBOOK and SPEC exist and backend baseline is marked done.
• Quality and risk controls per phase: requires dual/feature-flag strategy, Pest baseline coverage, audit thresholds, smoke and canary validation, and a monitored cutover with DB backup and rollback plan.

Quick Start

Ask the AI to migrate the Blade screen into MWART by following the mwart-process canônico using the required RUNBOOK and SPEC, producing a dual+flag backend baseline, then an incremental Inertia/React implementation with audits and QA until cutover readiness.