ci stuff

Author: KSemenenko

.github/workflows/deploy-github-pages.yml

@@ -62,6 +62,13 @@ jobs:
         with:
           global-json-file: global.json
 
+      - name: Expose GitHub Actions Runtime
+        uses: actions/github-script@v7
+        with:
+          script: |
+            core.exportVariable('ACTIONS_RUNTIME_TOKEN', process.env['ACTIONS_RUNTIME_TOKEN']);
+            core.exportVariable('ACTIONS_RESULTS_URL', process.env['ACTIONS_RESULTS_URL']);
+
       - name: Test supporting suites
         run: |
           dotnet test --project "$CORE_TEST_PROJECT"
@@ -94,10 +101,6 @@ jobs:
     needs: build_browser_suite
     runs-on: macos-latest
 
-    env:
-      BROWSER_TEST_LOG_DIR: output/test-results/browser-suite
-      BROWSER_TEST_LOG_PATH: output/test-results/browser-suite/browser-suite.log
-
     permissions:
       contents: read
 
@@ -110,6 +113,13 @@ jobs:
         with:
           global-json-file: global.json
 
+      - name: Expose GitHub Actions Runtime
+        uses: actions/github-script@v7
+        with:
+          script: |
+            core.exportVariable('ACTIONS_RUNTIME_TOKEN', process.env['ACTIONS_RUNTIME_TOKEN']);
+            core.exportVariable('ACTIONS_RESULTS_URL', process.env['ACTIONS_RESULTS_URL']);
+
       - name: Restore solution
         run: dotnet restore "$SOLUTION_FILE"
 
@@ -120,31 +130,7 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        id: browser_tests
-        shell: bash
-        run: |
-          set -o pipefail
-          mkdir -p "$BROWSER_TEST_LOG_DIR"
-          dotnet test --project "$UI_TEST_PROJECT" 2>&1 | tee "$BROWSER_TEST_LOG_PATH"
-
-      - name: Summarize browser suite
-        if: always()
-        shell: bash
-        env:
-          BROWSER_TEST_OUTCOME: ${{ steps.browser_tests.outcome }}
-        run: |
-          bash ./scripts/ci/write-browser-suite-summary.sh \
-            "$BROWSER_TEST_LOG_PATH" \
-            "$BROWSER_TEST_OUTCOME" \
-            "Run Browser Suite" >> "$GITHUB_STEP_SUMMARY"
-
-      - name: Upload browser test logs
-        if: always()
-        uses: actions/upload-artifact@v7
-        with:
-          name: browser-test-logs-release-pipeline
-          path: ${{ env.BROWSER_TEST_LOG_DIR }}
-          if-no-files-found: ignore
+        run: dotnet test --project "$UI_TEST_PROJECT"
 
       - name: Upload Playwright artifacts
         if: always()

.github/workflows/pr-validation.yml

@@ -54,6 +54,13 @@ jobs:
         with:
           global-json-file: global.json
 
+      - name: Expose GitHub Actions Runtime
+        uses: actions/github-script@v7
+        with:
+          script: |
+            core.exportVariable('ACTIONS_RUNTIME_TOKEN', process.env['ACTIONS_RUNTIME_TOKEN']);
+            core.exportVariable('ACTIONS_RESULTS_URL', process.env['ACTIONS_RESULTS_URL']);
+
       - name: Test supporting suites
         run: |
           dotnet test --project "$CORE_TEST_PROJECT"
@@ -83,10 +90,6 @@ jobs:
     needs: build_browser_suite
     runs-on: macos-latest
 
-    env:
-      BROWSER_TEST_LOG_DIR: output/test-results/browser-suite
-      BROWSER_TEST_LOG_PATH: output/test-results/browser-suite/browser-suite.log
-
     steps:
       - name: Checkout
         uses: actions/checkout@v6
@@ -96,6 +99,13 @@ jobs:
         with:
           global-json-file: global.json
 
+      - name: Expose GitHub Actions Runtime
+        uses: actions/github-script@v7
+        with:
+          script: |
+            core.exportVariable('ACTIONS_RUNTIME_TOKEN', process.env['ACTIONS_RUNTIME_TOKEN']);
+            core.exportVariable('ACTIONS_RESULTS_URL', process.env['ACTIONS_RESULTS_URL']);
+
       - name: Restore solution
         run: dotnet restore "$SOLUTION_FILE"
 
@@ -106,31 +116,7 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        id: browser_tests
-        shell: bash
-        run: |
-          set -o pipefail
-          mkdir -p "$BROWSER_TEST_LOG_DIR"
-          dotnet test --project "$UI_TEST_PROJECT" --verbosity normal 2>&1 | tee "$BROWSER_TEST_LOG_PATH"
-
-      - name: Summarize browser suite
-        if: always()
-        shell: bash
-        env:
-          BROWSER_TEST_OUTCOME: ${{ steps.browser_tests.outcome }}
-        run: |
-          bash ./scripts/ci/write-browser-suite-summary.sh \
-            "$BROWSER_TEST_LOG_PATH" \
-            "$BROWSER_TEST_OUTCOME" \
-            "Run Browser Suite" >> "$GITHUB_STEP_SUMMARY"
-
-      - name: Upload browser test logs
-        if: always()
-        uses: actions/upload-artifact@v7
-        with:
-          name: browser-test-logs-pr-validation
-          path: ${{ env.BROWSER_TEST_LOG_DIR }}
-          if-no-files-found: ignore
+        run: dotnet test --project "$UI_TEST_PROJECT" --verbosity normal
 
       - name: Upload Playwright artifacts
         if: always()

AGENTS.md

@@ -104,6 +104,8 @@ Rule format:
 - Editor top-toolbar search must remain visible in narrow layouts; when width runs out, the other toolbar groups should become explicitly horizontally scrollable/reachable before search is allowed to disappear.
 - Do not push branches or `main` without an explicit user command for that push; local commits are allowed, but network publish actions require clear approval in the current conversation.
 - When a CI test job fails, times out, or is cancelled, the workflow summary must still state which tests failed or that the run ended before per-test failure data was available; do not leave browser-suite failures represented only by generic job annotations.
+- Do not add or raise CI timeout settings as a fix for browser-suite instability or slow runs; fix the underlying failure path cleanly instead of masking it with workflow or step timeouts.
+- For TUnit reporting in GitHub Actions, prefer TUnit's built-in HTML report and the documented `actions/github-script` runtime exposure step over repo-local custom summary scripts or ad-hoc log parsers.
 - Public web hosting is split by role: the standalone PrompterOne app in this repo must publish on `app.prompter.one`, while the marketing landing site for `prompter.one` lives in the separate `PrompterOne-LandingPage` repository.
 - For deploy-only, domain, CI, or static-site hosting tasks, do not spend time on unrelated app/browser test suites unless the user explicitly asks or the runtime behavior itself changes; prefer workflow, build, and publish-config validation only.
 - Repo-wide .NET SDK and test-runner selection belong in the root `global.json`; do not split `global.json` test-runner opt-ins per project or subfolder once the user asks for a global test-platform policy.