Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/fr/pages/advanced/error-handling.md">

<violation number="1" location="docs/fr/pages/advanced/error-handling.md:97">
P2: Custom agent: **Flag AI Slop and Fabricated Changes**

The timeout example contradicts the surrounding text: it says `clarifyTimeoutError: true` enables `ETIMEDOUT`, but the example sets `clarifyTimeoutError: false`, which misrepresents the documented behavior.</violation>
</file>

<file name="docs/zh/pages/advanced/interceptors.md">

<violation number="1" location="docs/zh/pages/advanced/interceptors.md:108">
P2: Custom agent: **Flag AI Slop and Fabricated Changes**

Example claims complete interceptor execution output, but no request is ever made to trigger the interceptors.</violation>
</file>

<file name="docs/es/pages/advanced/x-www-form-urlencoded-format.md">

<violation number="1" location="docs/es/pages/advanced/x-www-form-urlencoded-format.md:32">
P2: Custom agent: **Flag AI Slop and Fabricated Changes**

The example references an undefined `url`, making the new docs snippet incomplete and low-quality.</violation>
</file>

<file name=".github/PULL_REQUEST_TEMPLATE.md">

<violation number="1" location=".github/PULL_REQUEST_TEMPLATE.md:20">
P3: Custom agent: **Flag AI Slop and Fabricated Changes**

Standalone dash under the Changes section is placeholder filler text shipped in the template.</violation>
</file>

<file name="docs/pages/advanced/error-handling.md">

<violation number="1" location="docs/pages/advanced/error-handling.md:97">
P2: The timeout example contradicts the documented behavior by setting `clarifyTimeoutError` to `false` while describing the `true` configuration for `ETIMEDOUT`.</violation>
</file>

<file name="docs/es/pages/advanced/error-handling.md">

<violation number="1" location="docs/es/pages/advanced/error-handling.md:97">
P2: El ejemplo contradice la explicación: para demostrar `ETIMEDOUT` debe usar `clarifyTimeoutError: true`, no `false`.</violation>
</file>

<file name="docs/pages/advanced/x-www-form-urlencoded-format.md">

<violation number="1" location="docs/pages/advanced/x-www-form-urlencoded-format.md:32">
P2: The new docs example uses an undefined `url` variable, so the sample code fails at runtime.</violation>
</file>

<file name="docs/zh/pages/advanced/x-www-form-urlencoded-format.md">

<violation number="1" location="docs/zh/pages/advanced/x-www-form-urlencoded-format.md:32">
P2: 示例中的 `url` 未定义，会导致复制示例后运行时报错。请改为显式 URL 字符串或先定义 `url` 变量。</violation>
</file>

<file name="docs/fr/pages/advanced/x-www-form-urlencoded-format.md">

<violation number="1" location="docs/fr/pages/advanced/x-www-form-urlencoded-format.md:32">
P3: The example uses an undefined `url` identifier, so the snippet will throw a ReferenceError when copied. Use a concrete URL or define the variable in the snippet.</violation>
</file>

<file name="docs/zh/pages/advanced/error-handling.md">

<violation number="1" location="docs/zh/pages/advanced/error-handling.md:95">
P3: The example sets `clarifyTimeoutError` to `false` even though the comment says to set it to `true` to get `ETIMEDOUT`. This is inconsistent and will mislead readers about how to enable ETIMEDOUT.</violation>
</file>

<file name="docs/zh/pages/advanced/request-config.md">

<violation number="1" location="docs/zh/pages/advanced/request-config.md:6">
P2: The new security warning incorrectly implies `maxBodyLength` protects against response decompression bombs; only `maxContentLength` applies to response size.</violation>

<violation number="2" location="docs/zh/pages/advanced/request-config.md:48">
P3: The compatibility note for reviver `context` is inaccurate: this is not an ES2023+ baseline feature.</violation>

<violation number="3" location="docs/zh/pages/advanced/request-config.md:367">
P2: `silentJSONParsing: true` is documented incorrectly: Axios swallows parse errors but keeps the original response string rather than setting `response.data` to `null`.</violation>
</file>

<file name="docs/pages/advanced/request-config.md">

<violation number="1" location="docs/pages/advanced/request-config.md:219">
P2: The new XSRF guidance is inaccurate: sending the XSRF header is controlled by `withXSRFToken`, not strictly by also setting `withCredentials`.</violation>
</file>