[Zacgoose]

This pull request improves how post-execution scripts are run for sequential jobs, ensuring they execute on the correct (pinned) worker and preventing potential deadlocks when the worker pool is full. It also enhances logging for PowerShell worker warmup scripts and adds a targeted test to verify the new behavior.

Orchestration and Worker Management:

• Ensures that post-execution scripts for sequential runs are executed on the same pinned worker instead of requesting a new one, preventing deadlocks in worker pool exhaustion scenarios (OrchestratorService.cs). [1] [2] [3] [4]
• Updates the RunPostExecutionAsync and RunScriptAsync methods to accept and use an optional PowerShellWorker parameter, so the correct worker is used for post-execution. [1] [2] [3]

PowerShell Worker Logging:

• Improves warmup diagnostics by streaming warning, information, and error log records in real-time as the warmup script runs, preserving message order and timestamps (PowerShellWorker.cs).

Testing:

• Adds a new test to verify that post-execution for sequential jobs runs on the pinned worker, and tracks which worker was used for post-execution (HungWorkerRecycleTests.cs, OrchestrationHarness.cs). [1] [2] [3]