[Bash2.0][Docs] API reference .md serves 198 bytes with zero endpoints, but llms.txt advertises it as "All endpoints"

### What's wrong

`/llms.txt` tells agents:

```
- [REST API reference — OSS](https://kestra.io/docs/api-reference/open-source.md): All endpoints
for flows, executions, logs, triggers, namespaces, storage, and more
- [REST API reference — Enterprise](https://kestra.io/docs/api-reference/enterprise.md): Additional
endpoints for tenants, users, roles, audit logs, and worker groups
```

Both URLs return 200 — and contain no endpoints at all.

`https://kestra.io/docs/api-reference/open-source.md` in full, **198 bytes**:

```
# Open Source API Reference for Kestra

import ApiDoc from "~/components/content/ApiDoc.astro"

API Reference of the Open-Source edition of Kestra.

## Explore the Kestra Open Source API

```

`https://kestra.io/docs/api-reference/enterprise.md`, **212 bytes**, is the same shape with `ApiDocee.astro`.

Two defects in one output:

1. **The advertised content is absent.** The API reference lives inside the `` component, which the Markdown renderer does not expand. Zero of the operations are present.
2. **Build-time source leaks into published output.** `import ApiDoc from "~/components/content/ApiDoc.astro"` is internal build detail being served to the public as documentation.

### Expected

The Markdown for these pages should contain the API operations (rendered from the same OpenAPI spec the HTML page uses), or `llms.txt` should stop describing them as "All endpoints" and point at the OpenAPI spec URL instead.

### Why it matters

"Which endpoint do I call?" is the single most common thing an agent needs from API docs. Right now the machine-readable answer is an Astro import statement.

### Repro

```
curl -s https://kestra.io/docs/api-reference/open-source.md
curl -s https://kestra.io/docs/api-reference/enterprise.md
```

Start with llms.txt and the open-source and enterprise API reference sources that produce the shown Markdown, then inspect how the ApiDoc.astro component is handled. Reproduce both URLs with curl and compare them with the HTML API pages or their OpenAPI source. Done means the Markdown exposes the advertised endpoint reference without leaking the internal import, or the links and descriptions are corrected to point to the OpenAPI specification.

Written by the indexing model from the issue text.