Module checks 

Concrete doctor checks.

Re-exports

pub use copy_dirs_dockerignore_collision::CopyDirsDockerignoreCollisionCheck;

pub use database_url_sqlite_in_prod::DatabaseUrlSqliteInProdCheck;

pub use db_connection::DbConnectionCheck;

pub use deploy_env_parity::DeployEnvParityCheck;

pub use dirty_git_tree::DirtyGitTreeCheck;

pub use docker_template_drift::DockerTemplateDriftCheck;

pub use generated_artifacts::GeneratedArtifactsCheck;

pub use local_env_parity::LocalEnvParityCheck;

pub use migrations::MigrationsCheck;

pub use toolchain::ToolchainCheck;

Modules

copy_dirs_dockerignore_collision

Deploy preflight (Phase 128 D-04): flag copy_dirs entries that .dockerignore would silently exclude from the Docker build context.

database_url_sqlite_in_prod

Database URL not sqlite in prod (SCOPE §12.8): if .env.production exists and its DATABASE_URL starts with sqlite:, hard-error.

db_connection

DB connection check (D-03): inspect DATABASE_URL and probe via the project’s existing db:status subprocess (mirrors commands::db_status).

deploy_env_parity

Deploy env parity (SCOPE §12.5): every key in .env.production appears as a commented entry in .do/app.yaml’s envs scaffold.

dirty_git_tree

Dirty git tree (SCOPE §12.9): warn when git status --porcelain has output or when there are unpushed commits relative to upstream.

docker_template_drift

Doctor check: flag when the committed Dockerfile has drifted from what the current scaffolder would generate.

generated_artifacts

Generated artifacts (SCOPE §12.7): warn-level presence check for Dockerfile, .dockerignore, .do/app.yaml.

local_env_parity

Local env parity (SCOPE §12.4): every key in .env.example is present in .env.

migrations

Migrations check (D-04): pending vs applied count via cargo run -- db:status.

toolchain

Toolchain check (D-02): rustc/cargo version vs rust-toolchain.toml.