namespace ytLive.Helpers;

/// <summary>
/// Whether this binary is a **development build**.
///
/// <para><b>Why <c>static readonly</c> and not <c>const</c>:</b> a const makes
/// <c>if (!DevBuild.IsDevelopment) return;</c> a compile-time branch, so whichever arm is dead
/// raises CS0162 — in Debug the guard is dead, in Release the body is. A readonly field is set
/// once at type init, so both arms compile clean and the JIT folds the branch away.</para>
///
/// <para><b>This is not the only defence.</b> The developer panel's XAML and code-behind are
/// removed from the Release compile entirely (<c>ytLive.csproj</c>, Page/Compile Remove), so a
/// shipped binary contains no BAML to reveal. This flag is the second lock: it refuses the
/// value even if something else calls the setter.</para>
///
/// <para>Single source for the question. It gates the multi-instance profile
/// (<see cref="InstanceProfile"/>), the scoreboard's debug seeding, and the all-resolutions
/// override (<c>MainViewModel.DeveloperMode</c>).</para>
/// </summary>
public static class DevBuild
{
    /// <summary>True for a Debug compile; false for Release and anything else.</summary>
    public static readonly bool IsDevelopment =
#if DEBUG
        true;
#else
        false;
#endif
}