One API project owns the domain; health checks per house pattern (ADR-0009)

[KaliCZ]

Two things, per request: the health-check setup used in DemoPage/hampap, and the collapse of the Domain + ServiceDefaults projects into the API project.

Based on the fix/naming-rule-private-constants branch (PR #5) — GitHub will retarget this to main automatically once #5 merges.

Single API project (ADR-0009, supersedes ADR-0001)

A feature folder now owns its whole slice — entities, handlers + error enums, controller, DTOs, mapping — instead of being split across Api and Domain:

src/ProductReviews.Api/
├── Features/{Catalog,Reviews,Votes,Profile}/   # complete slices
├── Persistence/                                # DbContext, configurations, migrations, seeding
├── Infrastructure/                             # one concern per file
└── Program.cs

• ProductReviews.ServiceDefaults is gone: OTel lives in Infrastructure/Observability.cs, health in Infrastructure/Health.cs; service discovery was dropped (nothing used it) and HTTP resilience moved onto the Zitadel userinfo client — per-client, not ConfigureHttpClientDefaults (rule Bump the nuget group with 1 update #14).
• Migration IDs untouched — existing dev databases keep working; only the namespace moved.
• "Domain never sees HTTP" is now a review rule, not a compiler edge — spelled out in ADR-0009 and CLAUDE.md rule Product Reviews showcase: StrongTypes end to end #1.
• ProductReviews.Domain.Tests → ProductReviews.Api.UnitTests.

Health checks (house pattern)

• /alive — liveness only: the version check (commit hash from the assembly SourceRevisionId, embedded by the SDK), no dependencies — a shared Postgres/Zitadel outage never reads as a dead process.
• /health — full readiness: EF Core AddDbContextCheck<ReviewsDbContext> (database, the Aspire integration''s duplicate check disabled) + zitadel probing the OIDC discovery document with a 5 s timeout. Zitadel failures report Degraded, not Unhealthy: reads survive an identity-provider outage.
• Both endpoints answer "<status> <commit>" — greppable by a blue/green deploy gate, no per-check detail leaked.

Verification

• dotnet build: 0 warnings, 0 errors
• dotnet test: 43/43 (13 unit + 30 integration, incl. two new wire-level health tests: /alive → Healthy <commit> with no Zitadel configured; /health → Degraded <commit> with DB up and no identity provider)
• Playwright E2E against the full restructured stack: 8/8 in 30 s

🤖 Generated with Claude Code