docs(changelog): credit Control UI fixes

[steipete]

What Problem This Solves

The clean landing branches for #100719 and #100725 intentionally exclude CHANGELOG.md so their already-proven runtime patches do not repeatedly conflict with OpenClaw's high-traffic release-notes hunk. Their user-visible fixes and contributor credit still need release-note coverage.

Why This Change Was Made

Keep the two code PRs as one focused runtime commit each, then own their changelog entries in this maintainer-only closeout. This preserves release notes and contributor attribution without coupling exact-head UI CI to unrelated concurrent changelog edits.

User Impact

No runtime change. The next release notes describe the corrected per-agent default-model label and canonical inbound-image preview behavior.

Evidence

• Entries match the final reviewed behavior and link the replacement PRs, original contributor PRs, and canonical issues.
• Contributor thanks remain attached to the relevant fix.
• git diff --check passed.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ea4b6ab6d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove changelog entries for unmerged fixes

When publishing a release from this tree, these two new entries advertise #100719 and #100725 as shipped Control UI fixes even though GitHub currently marks both PRs open and their referenced head commits are not present in the reviewed history. That would produce release notes claiming unavailable behavior and contributor credit before the runtime fixes actually land; please add these entries only with, or after, the corresponding fixes are merged.

Useful? React with 👍 / 👎.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: docs(changelog): credit Control UI fixes This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[steipete]

Land-ready maintainer closeout for exact head 403b941a742:

• Scope: CHANGELOG.md only, two additions, zero deletions; GitHub reports one changed file.
• Local proof: git diff --check origin/main...HEAD passed.
• Native gate: OPENCLAW_TESTBOX=1 scripts/pr prepare-run 100740 passed in docs/changelog-only mode and verified the pushed tree.
• Exact-head checks: Real behavior proof passed; dependency and security-sensitive guards passed.
• Runtime proof remains on fix(ui): show selected agent default model #100719 and fix(ui): proxy canonical inbound media previews #100725; this PR only records those landed user-visible fixes and contributor credit.

Known proof gaps: none for this changelog-only follow-up.

[steipete]

Merged via squash.

• Prepared head SHA: 403b941a742a5baef5e2713ec64bd750cf2b8918
• Landed commit: fa1a40a3c793ac1a94d7a8946655883790b7829d