ci: publish the first immutable demo release after readiness gates

[codeforester]

Problem

The v0.1.0 preparation is complete, but the repository has no GitHub release. Newcomers currently have a moving checkout rather than a tagged reference with immutable artifacts and a known framework floor. Publishing should follow the new correctness and version-identity gates.

Verified evidence

Reviewed on 2026-09-12 at 2de6b83f21ccacae04f8050f5691d0dd8159fda1; the local checkout matches GitHub main.

On 2026-09-12 the GitHub releases endpoint returns an empty list. VERSION, package metadata and the README target 0.1.0. Closed #16 explicitly prepared the release without publishing, and .github/workflows/release-package.yml validates/uploads workflow artifacts without creating a GitHub Release.

Sources:

• VERSION
• README.md
• docs/release-process.md
• .github/workflows/release-package.yml

Acceptance criteria

• After first-release defects and version-identity checks are resolved, prepare a concrete release plan and complete the separately authorized publication step.
• Publish an immutable tag/release with tested source/wheel artifacts and checksums plus exact supported base-cli version evidence.
• Provide a stable install/checkout path in the README and verify it in a clean environment.
• Do not imply that demo 0.1.0 freezes the framework API or requires a framework release.

Related work

Continuation after #16, whose scope explicitly excluded publishing. This issue does not authorize publication by itself.

Project fields

• Status: Backlog
• Priority: P2
• Area: Packaging
• Initiative: Base-CLI Demo
• Size: S
• Assignee: @codeforester
• Milestone: v0.1.0
• Target date: unscheduled