vittrade-batch-gate

Run a completion gate that reviews the diff for bloat, applies any required design-domain audits, then executes flutter analyze and focused flutter test commands from flutter_app/. Report the exact commands with PASS/FAIL evidence rather than a summary claim.

At minimum run flutter analyze and focused flutter test commands for the touched modules. When the changed scope affects routes, shared layouts, or repositories, escalate to the broader route, layout, repository, or full test gates.

Design-domain audits run only when the batch plan explicitly names design domains. In that case, read the design-domain guidance and execute the exact audit commands from the Flutter design system reference document.

The batch must not be reported complete when analyze or required tests fail. Windows line-ending or formatting failures are treated as a diagnosis task rather than a reason to weaken or skip the gate.

No. The gate explicitly forbids expanding into the next batch within the same session, keeping each batch scoped, reviewable, and independently verifiable.