[jasperblues]

Prod Guide has run on Postgres (Cloud SQL) since 2026-11-07, so postgres becomes the default Spring profile. It's step 6 of docs/CUTOVER_TO_POSTGRES.md.

• application.yml: spring.profiles.active: postgres, so ./mvnw spring-boot:run, an IDE run and the jar all start on Postgres. Prod is unchanged: its Cloud Run service sets SPRING_PROFILES_ACTIVE=postgres itself.
• Neo4j users now name their profile:
  • Export Seed's Neo4j job (-Dspring.profiles.active=neo4j);
  • the Docker Compose guide service, which runs beside the neo4j container (SPRING_PROFILES_ACTIVE=neo4j);
  • the hub's all-in-one image, in embabel/embabel-hub#93. Merge that first.
• README: Postgres is marked the default and listed first in the backend table. There's a "Running locally on Postgres" section (docker compose --profile postgres up -d, then ./mvnw clean spring-boot:run). The switching examples, Docker Compose and Neo4j-only sections say where the neo4j profile is needed.

./mvnw clean test: 213 tests, 0 failures, 3 skipped. Every Spring test names its own profile.

This replaces the unpushed postgres-local-default branch, which only changed the default for spring-boot:run.