The tests passed. Production didn’t.
The graph was mocked in CI because starting a real one for every run was too slow and too heavy. The mock didn’t know about the unique constraint, so the duplicate customer turned up in production instead.
Galactus DB answers its first query 0.8 seconds after docker run and idles at about 11 MB (Galactus DB 2.4.3 on an Intel Core i9-13900K, image already pulled). That makes it practical for every test run to start its own database, load the production schema and throw the whole thing away afterwards. Constraints, indexes and query plans then behave in CI the way they will in production.
// At the start of the test run: the same schema as production
CREATE CONSTRAINT customer_email IF NOT EXISTS
FOR (c:Customer) REQUIRE c.email IS UNIQUE;
CREATE (:Customer {email: 'test@example.com'});
CREATE (:Customer {email: 'test@example.com'}); // fails here, as it would in productionQuickstart