chore: add Spectral lint to lint:openapi script

Runs Spectral's OpenAPI linter (custom rules in .spectral.yaml) as part
of the lint:openapi pipeline, after Redocly bundle and lint.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: pengying

.github/workflows/lint.yml

@@ -7,13 +7,15 @@ on:
       - 'openapi.yaml'
       - 'openapi/**'
       - '.markdownlint.json'
+      - '.spectral.yaml'
       - 'mintlify/**'
   pull_request:
     branches: [ main ]
     paths:
       - 'openapi.yaml'
       - 'openapi/**'
       - '.markdownlint.json'
+      - '.spectral.yaml'
       - 'mintlify/**'
   # Allow manual triggering
   workflow_dispatch:

.spectral.yaml

@@ -76,12 +76,11 @@ rules:
   # ============================================================
 
   # Request bodies must use $ref, not inline schemas.
-  # Note: Spectral resolves $refs in the bundled spec, so some component-level
-  # false positives appear — the real violations are on paths.* entries.
   no-inline-request-schema:
     description: Request body schemas must use $ref, not inline definitions
     message: "Use $ref for request body schema instead of inline definition. See openapi/README.md#avoid-inline-schemas-in-request-and-response-definitions"
     severity: error
+    resolved: false
     given: "$.paths[*][get,post,put,patch,delete].requestBody.content[application/json].schema"
     then:
       field: "$ref"
@@ -92,6 +91,7 @@ rules:
     description: Response body schemas must use $ref, not inline definitions
     message: "Use $ref for response schema instead of inline definition. See openapi/README.md#avoid-inline-schemas-in-request-and-response-definitions"
     severity: error
+    resolved: false
     given: "$.paths[*][get,post,put,patch,delete].responses[*].content[application/json].schema"
     then:
       field: "$ref"