fix(363): nullable-reference remediation of UtilitiesCS/Extensions via per-file #nullable enable

[drmoisan]

Summary

Remediates pre-existing nullable-reference-type debt (CS86xx diagnostics) across the
UtilitiesCS/Extensions/ directory tree under a per-file #nullable enable opt-in
architecture. This is the Wave-0 child of the utilitiescs-nullable-remediation epic and
targets the shared extension methods whose nullability annotations become cross-module
contracts consumed by downstream epic children (OutlookObjects, EmailIntelligence, Dialogs).

Closes #363.

This is null-annotation and null-safety remediation only. There are no behavior changes,
no refactors, and no API redesign.

What changed

• Added a #nullable enable pragma to 23 .cs files under UtilitiesCS/Extensions/ and
  brought each to zero CS86xx diagnostics under the per-file pragma gate with
  TreatWarningsAsErrors. (2 files, IAsyncEnumerableExtensions.cs and NullExtensions.cs,
  were already #nullable enable and were verify-only — not in the diff.)
• Applied nullable annotations (?), null guards, and justified null-forgiving operators
  (!, each with a // why comment) that reflect actual null behavior.
• Expressed unconstrained-generic null-state via out TValue? / T? (no post-condition
  attributes). Kept value-type / Enum-constrained generics free of reference-nullable
  annotations.

Files touched (all UtilitiesCS/Extensions/): ArrayExtensions, AsyncSerialization,
CompilerServicesExtensions, DfDeedle, DfDeedle.FrameUtilities, DfMLNet,
DictionaryExtensions, DrawingExtensions, EnumExtensions, ExceptionExtensions,
ExtToChar, IControlExtensions, IEnumerableExtensions, IListExtensions,
ImageExtensions, JsonExtensions, JsonSerializerExtensions, LazyExtension,
QueueExtensions, StreamExtensions, StringExtensions, TraceExtensions,
WinFormsExtensions.

Architecture constraints honored

• Per-file #nullable enable opt-in only. No project-level <Nullable> element was added to
  UtilitiesCS/UtilitiesCS.csproj (the csproj is unchanged). Enforcement is per-file pragma only.
• Target is net481 / C# 12. No nullable post-condition attributes ([NotNullWhen],
  [MaybeNullWhen], [NotNullIfNotNull], [MaybeNull], [AllowNull], [DisallowNull],
  [DoesNotReturn], [MemberNotNull]) and no System.Diagnostics.CodeAnalysis polyfill were
  introduced (they are unavailable / fail CS0518 on net481).
• ArrayExtensions.cs was not split (annotation-only). DfDeedle.EmailRecord remains a plain
  private struct; = default reference-type field initializers became = default!.

Downstream contract

WinFormsExtensions.cs Clone<T>() overloads and Clone(this RowStyle/ColumnStyle) are
unchanged (non-null returns), preserving the contract consumed by dialogs-misc #374. Batch D
public nullability annotations are complete and correct.

Acceptance criteria

• AC1 (PASS): every CS86xx-emitting Extensions file carries #nullable enable and compiles
  with zero nullable diagnostics under the per-file pragma with TreatWarningsAsErrors.
• AC2 (PASS): no project-level <Nullable> element in UtilitiesCS.csproj.
• AC3 (PASS): no behavior change; 5702/5702 MSTest pass.
• AC4 (PASS): no coverage regression on changed lines (zero new executable lines;
  per-file covered/total identical baseline vs post-change).
• AC5 (PASS): public signatures remain behavior-compatible; annotations reflect actual null
  behavior and are safe cross-module contracts.

Verification (C# toolchain, exact order)

• dotnet tool run csharpier . — clean (no residual formatting).
• msbuild TaskMaster.sln /t:Build ... /p:EnableNETAnalyzers=true /p:EnforceCodeStyleInBuild=true
  — build succeeded, 0 errors.
• msbuild UtilitiesCS/UtilitiesCS.csproj /t:Rebuild ... /p:TreatWarningsAsErrors=true
  (per-file pragma gate, no /p:Nullable=enable) — CS86xx = 0 across all 25 Extensions files.
• pwsh scripts/vscode/Invoke-MSTestWithCoverage.ps1 — 5702/5702 passed; line coverage
  83.78%, branch 76.34% (unchanged vs baseline).

Review

Feature-review produced policy-audit, code-review, and feature-audit artifacts; all three are
PASS with a total blocking_count of 0. Artifacts and per-batch evidence are committed under
docs/features/active/utilitiescs-nullable-extensions/.

Epic context

Base branch: epic/utilitiescs-nullable-remediation-integration (Wave-0 child of the
utilitiescs-nullable-remediation epic).

🤖 Generated with Claude Code

https://claude.ai/code/session_01UXCu1xPtNbJs2HwKxgS9Bv