dify - 💡(How to fix) Fix Swagger exporting adds a bogus `payload` to GET endpoint documentation [1 pull requests]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

main branch (203b3a94)

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

1. Import the Swagger JSON exported by the server into the Swagger Editor.
2. Navigate to e.g. /apps/{app_id}/advanced-chat/workflow-runs

<img width="2100" height="1153" alt="Image" src="https://github.com/user-attachments/assets/03a39a2d-5476-4285-b9c5-de3b39135dfc" />

✔️ Expected Behavior

All query params are enumerated in the "Parameters" section

❌ Actual Behavior

Most query params are placed into a payload part as a JSON-like schema (like how you usually call into Elasticsearch), which does not exist at runtime.