[Pepps233]

Summary

Prepare the v0.4.1 patch release from merged changelog audit #305.

Reasoning

The standard release script prepared and validated the release, but its atomic push to protected main was rejected. Promote these exact generated commits through a PR without changing branch rules. Preserve release commit 8b7e52dc6 with a merge commit (do not squash or rebase); only after that source is present on remote main may its existing local v0.4.1 tag be pushed to trigger publication.

Changes

• Bump all workspace versions and internal workspace requirements from 0.4.0 to 0.4.1.
• Regenerate version-only root/example locks, CLI shrinkwrap, and installation locks; external dependency versions and integrity values are unchanged.
• Date the audited changelogs and add fresh Unreleased sections in the next-cycle commit.
• Exclude the owner's local AGENTS.md change and all credentials/build artifacts.

Testing

• Standard release preparation ran once from synchronized main at 2029a88fd.
• Model-data hydration/validation and generated-lock checks passed.
• Full npm run check, npm run build:offline, ./test.sh, and git diff --check passed.
• All 34 release outputs reviewed; semantic validation confirmed version-only JSON changes and dated changelog headings.
• Pre-bump candidate passed isolated npm/pnpm/Bun package/lifecycle acceptance and real ChatGPT print/interactive replies in npm- and Bun-installed CLIs.
• Release publication has not started: protected atomic push failed and remote tag absence was verified. CI must validate this PR before promotion.

This PR description is AI-generated.