docs: update mercurius report [skip ci]

Author: enisdenjo

implementations/mercurius/README.md

@@ -22,9 +22,9 @@ _* This report was auto-generated by graphql-http_
 12. MUST require a request body on POST
 13. SHOULD use 400 status code on missing {query} parameter when accepting application/graphql-response+json
 14. SHOULD use 400 status code on object {query} parameter when accepting application/graphql-response+json
-15. SHOULD use 400 status code on number {query} parameter when accepting application/graphql-response+json
-16. SHOULD use 400 status code on boolean {query} parameter when accepting application/graphql-response+json
-17. SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json
+15. SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json
+16. SHOULD use 200 status code with errors field on number {query} parameter when accepting application/json
+17. SHOULD use 200 status code with errors field on boolean {query} parameter when accepting application/json
 18. SHOULD allow string {query} parameter when accepting application/graphql-response+json
 19. MUST allow string {query} parameter when accepting application/json
 20. SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json
@@ -112,25 +112,25 @@ The server _SHOULD_ support these, but is not required.
       ```
       </details>
 
-  3. SHOULD use 200 status code with errors field on object {query} parameter when accepting application/json<br />
+  3. SHOULD use 400 status code on number {query} parameter when accepting application/graphql-response+json<br />
 
       <details>
-      <summary>Response status code is not 200</summary>
+      <summary>Response status code is not 400</summary>
 
       ```json
       {
-        "statusText": "Bad Request",
-        "status": 400,
+        "statusText": "OK",
+        "status": 200,
         "headers": {
           "date": "<timestamp>",
           "content-type": "application/json; charset=utf-8",
-          "content-length": "64",
+          "content-length": "61",
           "connection": "close"
         },
         "body": {
           "errors": [
             {
-              "message": "body/query must be string"
+              "message": "Must provide document."
             }
           ],
           "data": null
@@ -139,31 +139,25 @@ The server _SHOULD_ support these, but is not required.
       ```
       </details>
 
-  4. SHOULD use 200 status code with errors field on number {query} parameter when accepting application/json<br />
+  4. SHOULD use 400 status code on boolean {query} parameter when accepting application/graphql-response+json<br />
 
       <details>
-      <summary>Response status code is not 200</summary>
+      <summary>Response status code is not 400</summary>
 
       ```json
       {
-        "statusText": "Bad Request",
-        "status": 400,
+        "statusText": "OK",
+        "status": 200,
         "headers": {
           "date": "<timestamp>",
           "content-type": "application/json; charset=utf-8",
-          "content-length": "110",
+          "content-length": "61",
           "connection": "close"
         },
         "body": {
           "errors": [
             {
-              "message": "Syntax Error: Unexpected Int \"0\".",
-              "locations": [
-                {
-                  "line": 1,
-                  "column": 1
-                }
-              ]
+              "message": "Must provide document."
             }
           ],
           "data": null
@@ -172,7 +166,7 @@ The server _SHOULD_ support these, but is not required.
       ```
       </details>
 
-  5. SHOULD use 200 status code with errors field on boolean {query} parameter when accepting application/json<br />
+  5. SHOULD use 200 status code with errors field on object {query} parameter when accepting application/json<br />
 
       <details>
       <summary>Response status code is not 200</summary>
@@ -184,19 +178,13 @@ The server _SHOULD_ support these, but is not required.
         "headers": {
           "date": "<timestamp>",
           "content-type": "application/json; charset=utf-8",
-          "content-length": "115",
+          "content-length": "64",
           "connection": "close"
         },
         "body": {
           "errors": [
             {
-              "message": "Syntax Error: Unexpected Name \"false\".",
-              "locations": [
-                {
-                  "line": 1,
-                  "column": 1
-                }
-              ]
+              "message": "body/query must be string"
             }
           ],
           "data": null