Dev log reveals four silent failures: fake tests, wrong JSON, bad health checks, broken deploys

A developer's single-day work across six repositories uncovered a recurring theme of false positives — passing tests and green signals that certified nothing real. An ACME SSL client was sending a JSON array instead of an empty object, causing every certificate issuance to fail with a malformed error that went undetected because mock tests never actually encoded payloads. An HAProxy stats parser was matching server names against an incorrect backend naming pattern, causing all backends to report as unhealthy despite HAProxy itself showing them fully operational — a bug hidden by fixtures shaped to match the parser's wrong behavior rather than real output. A recurring deploy failure was dismissed as cosmetic, when in fact it was silently blocking downstream optimization stages from running on every release. The day's primary effort involved redesigning a VM provisioning control plane to verify machine identity before making changes, using a self-written manifest, a pre-pipeline probe with explicit refusal states, and a version ledger to make upgrades auditable.