Developer adds CI to four repos, first run exposes hidden env and dependency bugs

A developer set up basic CI pipelines across four small applications that had previously run without any automated checks. On the very first run, two repos failed to boot because their .env.example files contained unquoted spaces that the dotenv parser rejected — a flaw masked on the developer's machine by a long-standing local environment file. A third issue emerged when a required encryption key was intentionally left blank in the example file, causing a clean-checkout environment to crash on boot. Dependency audits run in the same pipelines flagged at least one high-severity advisory in a build-tool chain that had never been caught because npm audit had never been enforced in a blocking step. None of the bugs were logic errors; all existed in the gap between a developer's accumulated local state and what a fresh checkout actually contains.