Fix VM API reference to use app.prod.validmind.ai

[jamadriz]

Summary

• Update /reference/vm-api.html RapiDoc spec-url, server-url, and default-api-server from api.prod.validmind.ai to app.prod.validmind.ai
• Update the get-api-json Makefile target so local swagger downloads use the same host

Test plan

• Open https://docs.validmind.ai/reference/vm-api.html (or preview build) and confirm the API reference loads without swagger fetch errors
• Run make get-api-json in site/ and verify reference/vm-api-swagger.json downloads successfully

Made with Cursor

[github-actions]

Pull requests must include at least one of the required labels: internal, highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

PR Summary

The changes in this PR update the VM API endpoints from using the domain api.prod.validmind.ai to app.prod.validmind.ai in two key locations:

1. In the Makefile (target: get-api-json), the URL used to fetch the VM API Swagger specification has been updated. This ensures that the API spec is fetched from the new VM API endpoint.

2. In the QMarkdown documentation file (site/reference/vm-api.qmd), the attributes for the rapi-doc component (i.e., spec-url, server-url, and default-api-server) have been updated to reflect the new domain. This ensures that the interactive API documentation displays data from the updated endpoint.

These changes are intended to point the tooling and documentation to the current API infrastructure without altering the underlying API functionalities or data schemas.

Test Suggestions

• Manually verify that the Makefile successfully downloads the Swagger JSON from the new URL and that an appropriate error message is printed if the fetch fails.
• Load the QMarkdown page in a browser to ensure the rapi-doc component successfully fetches the new API spec and renders the API documentation correctly.
• Perform integration tests to confirm that all API calls from the application are routed correctly and that the change in the domain does not introduce connectivity issues.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview