V12__add_guest_order_columns.sql used PostgreSQL partial indexes:
CREATE UNIQUE INDEX ... ON orders(guest_token) WHERE guest_token IS NOT NULL
CREATE INDEX ... ON orders(guest_email) WHERE guest_email IS NOT NULL
H2 (the in-memory DB used by tests/dev, per application.yml) does not support
partial indexes -- the WHERE clause throws JdbcSQLSyntaxErrorException. Flyway
therefore failed to run V12 at Spring context startup, so the ApplicationContext
could not load, failing all 80 @SpringBootTest tests (:backend:test) and
aborting CI before coverage verification ever ran. This was the actual root
cause of the PR's red CI -- not a coverage shortfall.
Verified locally (Temurin JDK 21): ./gradlew :backend:jacocoTestCoverageVerification
now BUILD SUCCESSFUL; all 188 tests pass; bundle coverage 80.8% line / 64.9%
branch (thresholds 70% / 60%).
Semantics preserved: both H2 and PostgreSQL treat NULLs as distinct in a
UNIQUE index, so user-owned orders (NULL guest_token) never collide while
non-NULL guest tokens stay unique -- the same guarantee the partial index
provided, but portable across both databases.
Migration is not yet on master, so editing V12 in this PR is safe (no
checksum mismatch against origin/master).
afe70125f1