jobtrackingapp/JobTrackerApi/Migrations/20260711181039_SyncModelSnapshot.cs

using System;
using Microsoft.EntityFrameworkCore.Migrations;

#nullable disable

namespace JobTrackerApi.Migrations
{
    /// <summary>
    /// Intentionally a no-op. The committed ModelSnapshot had drifted far behind the live schema
    /// (empty -- see JobTrackerContextModelSnapshot.cs history): every table/column added since
    /// the last real migration (2026-03-11) was provisioned exclusively through the idempotent
    /// raw-SQL reconciler in StartupInitializationExtensions.cs, including the ASP.NET Identity
    /// tables themselves, which have never been created by an EF migration in this repo -- see
    /// EnsureIdentityTables' comment ("create Identity tables directly if dotnet ef isn't
    /// available"). `dotnet ef migrations add` scaffolded the honest diff against that stale
    /// snapshot: full CreateTable/AddColumn operations for schema that already exists on every
    /// environment (fresh or established) via that reconciler. Applying that diff for real would
    /// throw "table/column already exists" everywhere. This migration exists only to record itself
    /// in __EFMigrationsHistory and regenerate JobTrackerContextModelSnapshot.cs to match the
    /// current C# model, so `dotnet ef migrations add` produces a real (small) diff for the *next*
    /// schema change instead of scaffolding the whole database again. It changes no data or schema.
    /// </summary>
    public partial class SyncModelSnapshot : Migration
    {
        protected override void Up(MigrationBuilder migrationBuilder)
        {
        }

        protected override void Down(MigrationBuilder migrationBuilder)
        {
        }
    }
}