Reduce CI browser suite contention

Author: KSemenenko

AGENTS.md

@@ -130,7 +130,7 @@ Browser test execution rules:
 - Use one `dotnet test` process at a time for the browser suite.
 - The browser suite self-hosts the built WASM assets on a dynamically assigned loopback HTTP origin.
 - Each browser-suite host startup MUST request a fresh OS-assigned loopback port via `http://127.0.0.1:0`. Never pin or reuse a fixed browser-test port across runs.
-- Inside that single process, the browser suite may run up to `4` parallel TUnit workers.
+- Inside that single process, the browser suite may run up to `4` parallel TUnit workers locally; when repeated full-suite CI runs prove resource contention, lower the CI worker cap instead of weakening browser assertions.
 - Do not run `PrompterOne.Web.UITests` in parallel with another `dotnet build` or `dotnet test` command.
 - Browser acceptance tests must stay on the production-shaped runtime path; do not add or keep `?wasm-debug=1` or similar debug-query scenarios in automated acceptance coverage unless the user explicitly asks for that path.
 - Do not add Python or ad-hoc runner scripts to bootstrap browser verification. The repo test commands must self-host the app and execute the flows end to end on their own.

tests/PrompterOne.Web.UITests/AGENTS.md

@@ -31,7 +31,7 @@
 - This suite is the primary acceptance gate for the product.
 - Major workflows must be covered by long scenario tests, not only narrow regression tests.
 - Major scenario tests must save screenshots under `output/playwright/`.
-- This suite resolves its origin at runtime and uses one `dotnet test` process with up to `4` parallel TUnit workers.
+- This suite resolves its origin at runtime and uses one `dotnet test` process with up to `4` local parallel TUnit workers; lower the CI worker cap only when repeated full-suite runs prove resource contention.
 - Do not keep separate concurrent `dotnet build` or `dotnet test` processes alive against the same test assets.
 - Prefer `PrompterOne.Shared.Contracts.AppRoutes`, `UiTestIds`, and other named constants over inline route or selector strings.
 - Use dedicated test attributes first. Prefer `data-test-id`, allow `data-test`, and keep existing `data-testid` contracts until a deliberate migration replaces them. Raw text, role-name, and CSS selectors are allowed only when no stable dedicated test hook exists yet and the missing contract is fixed in the same task.

tests/PrompterOne.Web.UITests/GoLive/GoLiveFlowTests.cs

@@ -686,13 +686,6 @@ private static bool HarnessHasPublishedKind(JsonElement? harnessState, string ki
         return false;
     }
 
-    private static string SerializeDiagnosticState(JsonElement? state)
-    {
-        return state.HasValue
-            ? JsonSerializer.Serialize(state.Value)
-            : "null";
-    }
-
     private readonly record struct LayoutBounds(double X, double Y, double Width, double Height);
 
     [Test]

tests/PrompterOne.Web.UITests/GoLive/GoLiveOutputFailureRollbackTests.cs

@@ -132,14 +132,12 @@ private static Task SeedLiveKitOnlyOperationalSettingsAsync(Microsoft.Playwright
     private static async Task WaitForRuntimeSessionClearedAsync(Microsoft.Playwright.IPage page)
     {
         var deadline = DateTimeOffset.UtcNow.AddMilliseconds(BrowserTestConstants.Timing.ExtendedVisibleTimeoutMs);
-        JsonElement? lastRuntimeState = null;
 
         while (DateTimeOffset.UtcNow < deadline)
         {
-            lastRuntimeState = await page.EvaluateAsync<JsonElement?>(
-                BrowserTestConstants.GoLive.GetRuntimeStateScript,
-                BrowserTestConstants.GoLive.RuntimeSessionId);
-
+            var lastRuntimeState = await page.EvaluateAsync<JsonElement?>(
+        BrowserTestConstants.GoLive.GetRuntimeStateScript,
+        BrowserTestConstants.GoLive.RuntimeSessionId);
             if (!lastRuntimeState.HasValue)
             {
                 return;

tests/PrompterOne.Web.UITests/Infrastructure/TestAssemblyConfiguration.cs

@@ -2,9 +2,10 @@
 
 namespace PrompterOne.Web.UITests;
 
-public sealed record UiTestParallelLimit : IParallelLimit
+public sealed class UiTestParallelLimit : PrompterOne.Testing.EnvironmentAwareParallelLimitBase
 {
-    public int Limit => UiTestParallelization.DefaultWorkerLimit;
+    protected override int CiLimit { get; } = 2;
+    protected override int LocalLimit { get; } = UiTestParallelization.DefaultWorkerLimit;
 }
 
 internal static class UiTestParallelization

tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj

@@ -20,6 +20,7 @@
   <ItemGroup>
     <ProjectReference Include="../../src/PrompterOne.Web/PrompterOne.Web.csproj" ReferenceOutputAssembly="false" />
     <ProjectReference Include="../../src/PrompterOne.Shared/PrompterOne.Shared.csproj" />
+    <ProjectReference Include="../PrompterOne.Testing/PrompterOne.Testing.csproj" />
   </ItemGroup>
 
 </Project>