[Chore] Prepare v3.54.1 release

[roomote]

Opened on behalf of Elliott de Launay. View the task or mention @roomote for follow-up asks.

What problem this solves

The v3.54.0 tag went out from the release branch without the release-facing README consolidation landing on main, and main has accumulated additional fixes since that tag. That leaves the stable release history in an awkward state: the package on main is still 3.54.0, the Marketplace-facing README drifted, and there is no clean patch release prepared from the actual post-3.54.0 mainline state.

Why this change was made

This repurposes the existing follow-up branch into a v3.54.1 release prep. It brings the README headings onto the patch version, generates the 3.54.1 changelog and package bump from the merged post-3.54.0 delta, and keeps the release-process fix that adds an explicit review/confirmation stop before tagging.

User impact

The next stable publish can go out as 3.54.1 with the fixes already merged on main, including the recent Anthropic reasoning fix and onboarding/settings fixes, and the release docs/process will be aligned with what actually ships.

[roomote]

1 issue outstanding. Action required. See task

• Pin the reviewed commit SHA in .roo/commands/release.md before tagging so the new confirmation pause cannot publish a later main commit by mistake.
• Refresh the Marketplace release notes instead of only renaming the heading to v3.54.1; the section still describes the initial Zoo Code launch, and the same mismatch remains in the localized README copies.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!