remove timeouts

Author: KSemenenko

.codex/skills/dotnet-codeql/references/workflow.md

@@ -276,13 +276,7 @@ strategy:
         name: web
 ```
 
-### Timeout Configuration
 
-```yaml
-jobs:
-  analyze:
-    timeout-minutes: 60
-```
 
 ## Security Permissions
 

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

@@ -26,7 +26,6 @@ jobs:
   build_supporting_suites:
     name: Restore + Build Supporting Suites
     runs-on: ubuntu-latest
-    timeout-minutes: 15
 
     permissions:
       contents: read
@@ -50,7 +49,6 @@ jobs:
     name: Run Supporting Suites
     needs: build_supporting_suites
     runs-on: ubuntu-latest
-    timeout-minutes: 15
 
     permissions:
       contents: read
@@ -72,7 +70,6 @@ jobs:
   build_browser_suite:
     name: Restore + Build Browser Suite
     runs-on: macos-latest
-    timeout-minutes: 30
 
     permissions:
       contents: read
@@ -96,7 +93,10 @@ jobs:
     name: Run Browser Suite
     needs: build_browser_suite
     runs-on: macos-latest
-    timeout-minutes: 30
+
+    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
@@ -120,7 +120,31 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        run: dotnet test --project "$UI_TEST_PROJECT"
+        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
 
       - name: Upload Playwright artifacts
         if: always()

.github/workflows/pr-validation.yml

@@ -44,7 +44,6 @@ jobs:
     name: Run Supporting Suites
     needs: build_supporting_suites
     runs-on: ubuntu-latest
-    timeout-minutes: 15
 
     steps:
       - name: Checkout
@@ -84,6 +83,10 @@ 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
@@ -103,7 +106,31 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        run: dotnet test --project "$UI_TEST_PROJECT" --verbosity normal
+        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
 
       - name: Upload Playwright artifacts
         if: always()

AGENTS.md

@@ -102,6 +102,8 @@ Rule format:
 - Editor footer status metrics must keep a stable one-row layout while cursor or count values change; line, column, word, and duration updates must not make neighboring status chips jump or reflow.
 - Editor footer status chrome should read like a quiet IDE status strip: one compact row, low emphasis, and no oversized chip or outlined-block treatment for static metrics.
 - 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.
 - 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.