changelog: add release notes for v0.20260909.0

[berendt]

Highlights include per-service OpenStack CLI plugins, richer
osism baremetal clean RAID handling, and stalled-task reporting
for osism wait. SONiC ConfigDB validation gains broad leafref and
composite-key checks, CI validation of shipped artifacts, and
several fixes for false positives and schema mismatches. Other
fixes cover kolla-ansible fact routing, ansible task chain error
handling, and proxy/CA environment preservation. Numerous dependency
updates round out the release.

Generated with generate-changelog-input.sh using claude-sonnet-5.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="12" />
<code_context>
+
+### Added
+- Install OpenStack CLI per-service plugins so `osism openstack` command groups like loadbalancer, dns, baremetal, share, and coe are available (osism/python-osism#2622)
+- Add `--raid`/`--no-raid` options to `osism baremetal clean` and create the raid configuration after cleaning per node (osism/python-osism#2609)
+- Report what a stalled task last did while `osism wait` is waiting for it, including line count and time since last output (osism/python-osism#2624)
+- Validate leafref references encoded in composite ConfigDB row keys (e.g. port channel, VLAN and BGP membership), significantly extending SONiC ConfigDB cross-table validation coverage (osism/python-osism#2626)
</code_context>
<issue_to_address>
**nitpick:** The release notes state that `osism baremetal clean` provides `--raid`/`--no-raid` options and creates RAID configuration after cleaning each node, but the final command interface has replaced `--no-raid` with `--raid {delete,keep,recreate}` and only the `recreate` mode builds a RAID configuration. Users following the Added entry therefore invoke a nonexistent option or get an incorrect description of the resulting RAID behavior.

**Triggers:** When a user follows the Added entry rather than the later Changed entry.

**Suggested fix:** Rewrite the Added entry to describe the final `--raid {delete,keep,recreate}` interface, or explicitly label it as the earlier behavior superseded by the Changed entry.

```suggestion
- Add `--raid {delete,keep,recreate}` to `osism baremetal clean` for deleting, keeping, or rebuilding a node's RAID configuration (osism/python-osism#2609)
```
</issue_to_address>

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

nitpick: The release notes state that osism baremetal clean provides --raid/--no-raid options and creates RAID configuration after cleaning each node, but the final command interface has replaced --no-raid with --raid {delete,keep,recreate} and only the recreate mode builds a RAID configuration. Users following the Added entry therefore invoke a nonexistent option or get an incorrect description of the resulting RAID behavior.

Triggers: When a user follows the Added entry rather than the later Changed entry.

Suggested fix: Rewrite the Added entry to describe the final --raid {delete,keep,recreate} interface, or explicitly label it as the earlier behavior superseded by the Changed entry.

Suggested change

	- Add `--raid`/`--no-raid` options to `osism baremetal clean` and create the raid configuration after cleaning per node (osism/python-osism#2609)
	- Add `--raid {delete,keep,recreate}` to `osism baremetal clean` for deleting, keeping, or rebuilding a node's RAID configuration (osism/python-osism#2609)