Release base-cli 0.2.0 with the consumer-neutral API

[codeforester]

Context

The source tree now contains the completed consumer-neutral refactor through #32, including the public CliProfile API and removal of Base-specific package residue. However, PyPI still publishes only base-cli==0.1.0, whose wheel predates those changes.

A clean installation of the published package therefore does not match the current source contract that Base consumes.

Scope

• Update VERSION to 0.2.0 (the refactor removes/changes the old implicit Base integration surface).
• Move the completed [Unreleased] changelog entries into the 0.2.0 release section.
• Run the package validation workflow and clean-environment smoke tests.
• Merge the release PR, create the matching v0.2.0 tag, and publish the reviewed artifact to PyPI through the protected Package workflow.
• Verify pip install base-cli==0.2.0 exposes CliProfile and the current public API.

Dependencies

• Blocks the Base dependency bump issue that will update requirements-dev.txt from base-cli==0.1.0 to base-cli==0.2.0.
• The Base bump should land only after the PyPI publication and a clean-venv smoke test succeed.

Acceptance criteria

• PyPI lists base-cli==0.2.0.
• A clean environment can install it without a sibling checkout.
• The installed package exposes the current API used by Base, including CliProfile, register_record_schema, and CommandFilterNormalizer.
• The release tag and package metadata match VERSION exactly.