KrakenJS Missing Production Config Issue

Goal: ensure that KrakenJS loads the NODE_ENV‑specific configuration file (e.g., production.json) in production to enable view caching, strict error handling, and security middleware.

Constraint/uncertainty: When the file is absent, KrakenJS silently falls back to the base config and defaults, disabling those features without emitting a clear warning, making it difficult to detect misconfiguration during deployment.

Does KrakenJS provide any log or error when the environment‑specific file is missing? Should the framework treat a missing file as a fatal error in production? Is there a recommended way to enforce presence of the file via build or deployment checks?