preflight-modulo

To prevent code drift when modifying multi-tenant module files, enforce a three-phase pre-flight workflow that mandates reading SPEC.md and charter artifacts before editing controllers, services, entities, or migrations. This ensures all changes comply with established module rules.

A pre-flight workflow for module development safety hooks is a mandatory three-phase process (PRE-FLIGHT, DURING, POST) that blocks file editing until required briefings and prohibitions are read, ensuring changes are committed, pushed, and documented via PRs and tests.

Enforce ADR compliance before editing Inertia TSX pages by consulting decisions-search for relevant Architecture Decision Records and reading memory/proibicoes.md primary rules during the pre-flight phase to block rule-violating edits.

Yes, the pre-flight workflow applies to database migrations and observer edits. It enforces safe handling for any database-related actions and requires reading module-specific RUNBOOK and CAPTERRA documents before modifying files under the Modules directory.

Maintain git commit discipline across multi-tenant module updates by applying workflow guardrails that enforce incremental commit and push steps during the POST phase, ensuring every modification is logged through a complete PR and test documentation cycle.