chore(yargs-extra): Add CHANGELOG.md

[sea-grass]

This PR adds a changelog for yargs-extra.

(vibed)

[greptile-apps]

Greptile Summary

• Adds a new yargs-extra/CHANGELOG.md for @bpinternal/yargs-extra.
• Documents retrospective release notes from 0.0.3 through 0.0.21.
• Covers dependency, tooling, packaging, README, and CommonJS-related changes.

Confidence Score: 4/5

The change is documentation-only and does not affect runtime behavior, but the changelog needs release-history corrections before it is reliable for consumers auditing package changes.

The modified surface is small and limited to one changelog, with the main risk being inaccurate historical attribution rather than code execution impact.

yargs-extra/CHANGELOG.md

T-Rex Logs

What T-Rex did

• T-Rex attempted to verify the changelog's absence on the base by running git cat-file for 57d427...:yargs-extra/CHANGELOG.md, which exited with code 128.
• T-Rex then verified the post-change state by listing HEAD, confirming yargs-extra/CHANGELOG.md exists, and validating with git cat-file -e (exit code 0) and git show reading the content at HEAD.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(yargs-extra): Add CHANGELOG.md" | Re-trigger Greptile}

[greptile-apps]

Correct release attribution The changelog lists changes under release headings that do not match when they actually landed. The check:type rename appears under 0.0.10, but that release only bumped the version and dependency versions; likewise, the package manager metadata and engine constraints appear under 0.0.6, but those were added while the package was still at 0.0.5. Consumers using this changelog to audit release boundaries can get the wrong version for script, pnpm, and engine changes. Please move these entries to the releases where they occurred, or remove them from the incorrect sections.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Missing earlier releases This changelog says it covers notable changes starting at 0.0.3, but the package history includes earlier published versions. 0.0.1 introduced the package, and 0.0.2 changed @types/yargs between dependency groups. Consumers using this changelog to audit release history will miss those pre-0.0.3 changes unless they are documented or explicitly marked as intentionally omitted.