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
-`RfcLevel.Must` — (default) RFC says MUST / MUST NOT. Only set explicitly if you want to be clear.
120
+
-`RfcLevel.Should` — RFC says SHOULD / SHOULD NOT / RECOMMENDED.
121
+
-`RfcLevel.May` — RFC says MAY / OPTIONAL. Both behaviors are compliant.
122
+
-`RfcLevel.OughtTo` — RFC uses "ought to" (weaker than SHOULD).
123
+
-`RfcLevel.NotApplicable` — No single RFC 2119 keyword applies (best-practice / defensive tests).
124
+
125
+
Check the [RFC Requirement Dashboard](docs/content/docs/rfc-requirement-dashboard.md) for classification guidance and to verify your assignment matches the existing pattern.
126
+
117
127
**Critical rules:**
118
128
- NEVER set `AllowConnectionClose = true` for MUST-400 requirements where the RFC explicitly says "respond with 400".
129
+
- Set `RfcLevel` to match the RFC 2119 keyword in the relevant RFC quote. Default is `Must` — only set explicitly for non-Must tests.
119
130
- Set `Scored = false` only for MAY-level or purely informational tests.
120
131
- Always use `ctx.HostHeader` (not a hardcoded host) in payloads.
121
132
- Tests are auto-discovered — no registration step needed. The `GetTestCases()` yield return is sufficient.
Copy file name to clipboardExpand all lines: docs/content/add-with-ai-agent.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,10 +25,11 @@ Point your AI agent at the repository and reference the `AGENTS.md` file. It con
25
25
26
26
For a new **test**, the agent will:
27
27
28
-
1. Add a `yield return new TestCase { ... }` block to the correct suite file
28
+
1. Add a `yield return new TestCase { ... }` block to the correct suite file, including the correct `RfcLevel` (`Must`, `Should`, `May`, `OughtTo`, or `NotApplicable`)
29
29
2. Add a docs URL mapping entry (if the test is `COMP-*` or `RFC*` prefixed)
30
30
3. Create a documentation page under `docs/content/docs/{category}/`
31
31
4. Add a card to the category index page
32
+
5. Add a row to the RFC Requirement Dashboard
32
33
33
34
For a new **framework**, the agent will:
34
35
@@ -41,4 +42,5 @@ For a new **framework**, the agent will:
41
42
42
43
- The `AGENTS.md` file includes verification checklists — make sure the agent runs them before submitting
43
44
- No changes to CI workflows are needed for either task; tests and servers are auto-discovered
44
-
- For tests, the agent should check the RFC to determine the correct requirement level (MUST/SHOULD/MAY) and validation pattern
45
+
- For tests, the agent should check the RFC to determine the correct `RfcLevel` (MUST/SHOULD/MAY/"ought to"/N/A) and set it on the `TestCase`. The default is `Must` — only set explicitly for non-Must tests
46
+
- The agent should add a row to the [RFC Requirement Dashboard](docs/content/docs/rfc-requirement-dashboard.md) and update all counts
0 commit comments