[azure.ai.rle] Dev registry update for 0.3.0-preview

[Azure SDK Bot (azure-sdk)]

Dev registry update for the azd-ext-azure-ai-rle_0.3.0-preview release.

[azure-pipelines]

Azure Pipelines:
22 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Updates the development extension registry for the RLE 0.3.0-preview release.

Changes:

• Adds updated RLE command metadata and examples.
• Registers six platform artifacts with verified release checksums.

Suppressed comments (1)

cli/azd/extensions/registry.dev.json:286

• azd-code-reviewer: show also accepts zero arguments and falls back to the environment saved in .azd-rle.json (Use: "show [environment-name]"), while this usage presents the name as mandatory. Use [environment-name] here and in azure.ai.rle/extension.yaml.

              "usage": "$env:AZD_AI_RLE_ENABLE = \"true\"; $env:FOUNDRY_PROJECT_ENDPOINT = \"https://<account>.services.ai.azure.com/api/projects/<project>\"; azd ai rle show <environment-name>"

[Jon Gallant (jongio)]

Verified all six sha256 checksums in this entry against the published 0.3.0-preview release assets. All six match, and each entryPoint matches the binary inside its archive. The metadata block is a verbatim copy of the extension.yaml packaged in those artifacts, so this file reflects what actually ships.

Two non-blocking notes.

The suggestion above to change <environment-name> to [environment-name] for invoke and show is right about the commands. invoke.go:42 declares Use: "invoke [environment-name]" and show.go:27 declares Use: "show [environment-name]", so both args are optional. But this isn't the file to fix it in. This entry is generated from cli/azd/extensions/azure.ai.rle/extension.yaml, and the same strings are baked into the extension.yaml shipped inside the 0.3.0-preview artifacts. Editing the registry here would desync it from the released artifact and get overwritten by the next generated registry PR. The fix belongs in the extension's extension.yaml so it flows into the next release.

Separately, main's dev registry jumps from 0.1.0-preview straight to 0.3.0-preview. The 0.2.0-preview registry update (#9351) was merged into farhannawaz/rle-control-plane rather than main, so that version never landed here. Likely fine since 0.3.0 supersedes it, but worth knowing if anyone expects to install 0.2.0-preview from the dev registry.

[JeffreyCA]

/check-enforcer override