T2: Identity persistence + EF Core migration

[devin-ai-integration]

Summary

Implements the persistence layer for the Identity microservice:

• IdentityDbContext configured with DbSet<AppUser> and DbSet<AppRole>, mapping to Users and Roles tables with unique indexes on UserName and Email
• EF Core InitialCreate migration generated under Identity.Infrastructure/Data/Migrations/
• Auto-migration at startup in Program.cs:

  using (var scope = app.Services.CreateScope())
  {
      var db = scope.ServiceProvider.GetRequiredService<IdentityDbContext>();
      db.Database.Migrate();
  }

Build passes (dotnet build -c Release); zero references to forbidden symbols. Migration verified against PostgreSQL (tables Users and Roles created).

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/0f07b7a8f1014aec962930431c54da9f
Requested by: @mbatchelor81

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🚩 Automatic migration on startup runs unconditionally in all environments

The db.Database.Migrate() call at src/Services/Identity/Identity.API/Program.cs:19 runs in all environments (dev, staging, production), unlike other services (Order, Customer) which have no auto-migration. In scaled-out production deployments, multiple instances will attempt to migrate concurrently. PostgreSQL + EF Core handle this safely via advisory locks, so it won't corrupt data, but it adds startup latency and is a pattern divergence from other services. If this is intentional for the T2 persistence task, consider gating behind IsDevelopment() or an environment variable before merging to production branches.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

This is intentional per the T2 task specification — the auto-migration placement was explicitly required. PostgreSQL + EF Core advisory locks make concurrent startup safe. Gating behind an environment check can be considered in a follow-up if needed before production deployment.