docs(api-v2): sync API reference from Frontdoor v2.10.0

[runpod-docs-sync]

Automated from runpod/rphttp2@v2.10.0.

• Source ref: v2.10.0
• Source commit: 56647ac1a04fa1e8a205d2dddf05f0e0893068e2
• Workflow run: 33668012814

api-reference-v2/openapi.json, the endpoint MDX files under api-reference-v2/, and the API v2 navigation groups in docs.json are generated together from Frontdoor's canonical spec/openapi.yaml. Do not edit them independently.

[lavanya-gunreddi]

@Promptless Don't remove or overwrite existing description fields in MDX files. If a description already exists on a page, keep it unchanged. For MDX files that are missing a description, add one that matches the tone and style of existing descriptions and accurately describes the page content. Keep all descriptions between 110 and 160 characters.

[promptless]

Got it — I'll audit the changed api-reference-v2/ MDX files in this PR: existing description fields will be left untouched, and I'll add a 110–160 character description to any page that's missing one, matching the tone of the existing ones. I'll follow up here with what changed.

[promptless]

Update: I looked into it. The automated Frontdoor sync in this PR stripped the curated description frontmatter from 44 endpoint pages (those descriptions still exist on main), and 2 newly added Serverless build endpoints never had one. Plan: restore the 44 descriptions verbatim from main and author 2 new ones matching the sibling Serverless pages' tone — all within 110–160 characters. Drafting the changes now.

[promptless]

Done — the fix is now on this PR. Every description that already existed was left untouched. The 44 endpoint descriptions this sync had stripped are restored exactly as they were on main, and the two new Serverless build endpoints (get-a-serverless-endpoint-build, list-serverless-endpoint-builds) now have descriptions in the same style. All are within 110–160 characters. Nothing else changed — openapi.json, docs.json, and the page bodies are unchanged.

One thing worth flagging: api-reference-v2/ is regenerated from Frontdoor's canonical spec on every sync, and that generation step is what dropped these descriptions in the first place. This commit fixes the current PR, but the same descriptions will be stripped again on the next sync unless the generator is updated to preserve existing description frontmatter (or to source descriptions from the spec). We'd recommend addressing that in the upstream sync workflow (runpod/rphttp2) so it doesn't recur.