.NET Configuration

Requirement The root global.json MUST set the first feature band of the manifest .NET major release as its SDK version and roll forward with latestMajor.

Rationale Any SDK from that major release builds the workspace, so a patch or feature band release needs no change to the workspace. The manifest names the major release, and Directory.Build.props sets its target framework.

Requirement apps/api/Directory.Build.props MUST set the target framework of the manifest .NET stack release, and enable nullable types, implicit usings, and warnings as errors.

Rationale One file then owns the settings that would otherwise drift between projects.

Requirement apps/api/Directory.Packages.props MUST enable central package management and carry the exact manifest pins.

Rationale Individual project files then reference package names without versions, so no project can drift.

Requirement The root .config/dotnet-tools.json MUST pin every local .NET tool that a documented command invokes.

Rationale When a tool ships in the manifest .NET stack release, its pin matches that release, so local and CI runs use one version.

Requirement A configuration section MUST bind to a named options class validated for required fields, ranges, and formats at startup.

Rationale Reading a required setting through a raw configuration lookup defers the failure to the first request that needs it. This binding realizes litespec/workspace/config#validate-backend-configuration-at-startup.