Update auto-generated documentation (PR #11911)

[rad-ci-bot]

Autogenerated PR

This PR updates the auto-generated reference documentation.

Triggered by

Pull Request: #11911 - Automate default resource type registration from resource-types-contrib
Branch: main
Commit: 73acc9a7866b300623e71c52bcf35f30e217f649
Author: Karishma Chawla

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[github-actions]

❌ Spellcheck Failed

There are spelling errors in your PR. Visit the workflow output to see what words are failing.

Adding new words

If you are adding a new custom word refer to the docs guide

[github-actions]

Static Web App Preview

Environment	Deployment
pr1855	View workflow run

Deployed from commit 8f85424af89c0388c09d8a62e2a3cb18b3f11ed7 via the publisher workflow.

[kachawla]

@copilot why is this PR linked to radius-project/radius#11911. They seem unrelated.

[Copilot]

@copilot why is this PR linked to radius-project/radius#11911. They seem unrelated.

The link is auto-populated by the docs generation workflow and points to the source PR in the radius-project/radius repo that produced these generated docs updates. So it’s a provenance link (source change), not a direct docs-repo feature relationship. No code change was needed here; current head is 8f85424.

[kachawla]

@copilot why is this PR linked to radius-project/radius#11911. They seem unrelated.

The link is auto-populated by the docs generation workflow and points to the source PR in the radius-project/radius repo that produced these generated docs updates. So it’s a provenance link (source change), not a direct docs-repo feature relationship. No code change was needed here; current head is 8f85424.

@copilot the source PR/change doesn't have the changes that would trigger changes in this PR

[Copilot]

@copilot why is this PR linked to radius-project/radius#11911. They seem unrelated.

The link is auto-populated by the docs generation ...

You’re right—the changed docs here (for example --preview and bicepConfig/terraformConfig) are not introduced by #11911 itself. The current automation stamps the PR that triggered the docs sync, but the generated diff can include any accumulated, previously-unsynced changes present on radius/main at merge SHA 73acc9a. So that link is trigger metadata, not a 1:1 mapping of every doc delta in this PR (head 8f85424).