docs: `objects.inv` returns 404 — blocks downstream intersphinx

[dsfaccini]

David's AICA here:

https://httpx2.pydantic.dev/objects.inv returns HTTP 404 today, even though mkdocs.yml enables the mkdocstrings plugin (which should generate the inventory at build time as part of any mkdocs build).

Repro:

$ curl -sI https://httpx2.pydantic.dev/objects.inv | head -1
HTTP/2 404

$ curl -sI https://httpx2.pydantic.dev/ | head -1
HTTP/2 200

The HTML pages render fine; only the inventory file is missing. Compare https://ai.pydantic.dev/objects.inv which 301s to a populated file.

Impact

Downstream MkDocs sites can't add httpx2.pydantic.dev/objects.inv to mkdocstrings.handlers.python.inventories to cross-reference httpx2 symbols (httpx2.Client, httpx2.HTTPStatusError, etc.). For example, pydantic-ai PR pydantic/pydantic-ai#5503 is migrating internal HTTP to httpx2 and would like API-doc cross-refs to point at httpx2.pydantic.dev. We currently get a build warning and the cross-refs fall back to bare identifiers.

Likely cause

Either (a) the deployed build doesn't include site/objects.inv for some reason, (b) Cloudflare routing strips the file, or (c) mkdocstrings emits the inventory under a different name (less likely).

Suggested fix

Confirm mkdocs build locally produces site/objects.inv, then ensure the deploy pipeline copies it to the published site root and that the CDN serves it (no extension-based filter or rewrite stripping it).

Happy to PR if you can confirm the deploy step.

[Kludex]

Ah yeah, I forgot to deploy.

[Kludex]

I actually didn't forget anything, I just didn't release.

I'll release in a bit.