Fix benchmark pipeline hang: force exit after report generation

The benchmark-report command hangs indefinitely after BenchmarkDotNet
and report generation complete because the Microsoft.Agents.AI hosting
framework leaves non-daemon threads running that prevent the process
from exiting. On self-hosted agents with no job timeout (default 0),
this causes the pipeline run to hang until manually cancelled.

Two fixes:
- Add Environment.Exit(0) after benchmark-report completes to kill
  lingering hosting threads
- Add timeoutInMinutes: 45 to the benchmark job as a safety net

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: sharpninja

azure-pipelines-benchmark-report.yml

@@ -23,9 +23,9 @@ stages:
     jobs:
       - job: benchmark
         displayName: Run slow-lane validation and generate report
+        timeoutInMinutes: 45
         pool:
           name: Default
-        timeoutInMinutes: 0
         steps:
           - checkout: self
 
@@ -75,7 +75,6 @@ stages:
         displayName: Deploy static benchmark site
         pool:
           name: Default
-        timeoutInMinutes: 0
         steps:
           - checkout: none
 

src/BitNetSharp.App/Program.cs

@@ -27,6 +27,11 @@
         reportDirectory,
         commitHash);
     Console.WriteLine($"Saved benchmark comparison report to {outputPath}");
+
+    // Force exit: BenchmarkDotNet and the Microsoft.Agents.AI hosting framework
+    // may leave non-daemon threads running that prevent the process from exiting
+    // cleanly, causing CI pipeline jobs to hang indefinitely on self-hosted agents.
+    Environment.Exit(0);
     return;
 }