local-runtime-harness

To set up a local development environment for reproducible testing, run the `./scripts/dev` command, which automates app booting, environment configuration via `.env.example`, and local service management using Docker Compose.

The best way to manage local services like databases during development is by using Docker Compose configurations, which this approach adds locally alongside health checks and logs to ensure service reachability and inspectability.

You add health checks and diagnostics to your dev server by utilizing runtime scripts that verify the main app or API is reachable, ensuring local logs are inspectable for runtime debugging and behavior verification.

Yes, you can automate resetting state and reproducing bugs in a local runtime by executing the provided local runtime scripts, which are designed specifically for inspecting behavior and resetting state locally.

Local runtime inspection requires generating environment documentation to ensure reproducibility, specifically producing a `.env.example` file and `docs/development` to guide local environment setup and configuration.

Local development scripts fail to reproduce bugs consistently when environment configuration is incomplete, making it necessary to use generated `.env.example` files and Docker Compose services to ensure a reproducible and inspectable local state.