You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Rule format:
106
106
- 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.
107
107
- 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.
108
108
- 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.
109
-
- GitHub Actions test jobs must use the repo `tests/dotnet-test-progress.rsp` response file and enable TUnit coverage for every runnable test suite so CI measures the same detailed, non-ANSI test output and coverage signal expected locally.
109
+
- GitHub Actions test jobs must use the repo `tests/dotnet-test-progress.rsp` response file and enable TUnit coverage for every runnable test suite so CI measures the same minimal, non-ANSI test output and coverage signal expected locally; do not configure detailed per-test `Standard output` or empty `Error output` blocks as the default log format.
110
110
- 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.
111
111
- Runtime telemetry providers such as Google Analytics, Clarity, and Sentry must not be described as connected or working unless the real production path is verified with actual outbound delivery or loaded vendor SDKs; local harness snapshots, init flags, or stubbed globals are not sufficient proof.
112
112
- Runtime telemetry readiness must be proven against Release-built app artifacts in CI; do not sign off GA, Clarity, or Sentry from Debug-only local runs when the shipped Release pipeline has not validated that path.
@@ -173,7 +173,7 @@ Rule format:
173
173
For this `.NET` repo:
174
174
175
175
- all automated test projects run on `TUnit` and native `Microsoft.Testing.Platform`
176
-
- use `@./tests/dotnet-test-progress.rsp` on repo test commands so `dotnet test` emits detailed, non-ANSI per-test progress logs consistently in terminal and CI text logs
176
+
- use `@./tests/dotnet-test-progress.rsp` on repo test commands so `dotnet test` emits minimal, non-ANSI progress logs consistently in terminal and CI text logs without flooding every test with `Standard output` or empty `Error output` sections
177
177
-`format` is direct `dotnet format`, not `--verify-no-changes` and not a wrapper
178
178
- coverage uses TUnit's native `--coverage` support
179
179
-`LangVersion` is not pinned; use the SDK default unless the repo intentionally changes it later
0 commit comments