[houlianpi]

Summary

Prepare the Python distribution as 0.3.2 after the Android input fixes and public README/landing-page updates. Align the exact-version contract, add the 2026-10-21 changelog entry and release-preparation notes, and retain the private npm package's independent 0.1.0 version.

Related issue

Direct user-authorized release preparation; no separate behavior issue is required. The release notes describe merged changes #39, #41, and #42 without claiming that this metadata update introduces their runtime behavior.

Design document

Direct /spec-driven request. No separate design document was required for a bounded version/metadata update.

SPEC updates

No SPEC delta. Reviewed root SPEC.md Development Rules and Public Product Presentation plus frontend/SPEC.md packaging boundaries. Existing installation, metadata, entrypoint, package-resource, and manual release-verification contracts remain accurate; no runtime/API/configuration/dependency or module-ownership changes.

Changes

• Python version and exact distribution assertion: 0.3.1 to 0.3.2.
• New CHANGELOG section and comparison links; preserve 0.3.1 history.
• New docs/releases/v0.3.2.md with upgrade/Skill refresh instructions, accurate change scope, and remaining publication checks.
• Leave npm version, dependencies, workflows, and runtime source unchanged.

Verification

Passed against the audited snapshot (commit 47063a9):

• Version assertion failed before the metadata bump, then the distribution-contract module passed all 20 tests.
• .venv/bin/python -m pytest — 4782 passed, 11 skipped; one upstream deprecation warning.
• .venv/bin/ruff check . and .venv/bin/ruff format --check . — passed.
• npm run build — passed; generated Control Plane assets remain untracked.
• Pinned hatchling 1.32.0 built wheel and sdist; rebuilt wheel from extracted sdist and compared metadata, entrypoints, and packaged resource bytes.
• Twine check passed for both distributions.
• Installed the built wheel with all dependencies in a fresh external environment through the machine's configured package mirror. Isolated Python import resolved from that environment, not the checkout; both console-script help commands, four platform presets, Skill resources, and packaged static serving passed.
• Copied Skill installation in an isolated temporary project matched bundled bytes and did not initialize a Workspace.
• git diff --check and independent combined SPEC-to-change/change-to-SPEC audit passed with no findings; final identities match the reviewed snapshot.

Local checks used macOS/Python 3.14.7. Final commit CI and supported-platform release checks are not assumed from these local results. An initial offline dependency-cache miss was resolved by the configured-mirror installation.

Evidence

The version contract and release notes are in the diff. Distribution metadata was independently checked as 0.3.2. Local raw test/build/install/audit evidence is retained outside Git; no generated package, environment, log, or report is committed.

Release or documentation impact

This PR prepares source only. It does not create a tag, GitHub release, deployment, workflow run, or PyPI publication. Actual publication is performed through the existing GitHub Release Actions workflow, which currently requires manual dispatch with an explicit publish input and the pypi environment. Creating a tag alone does not trigger that workflow.

Clean public-index first-use, real target/Provider execution, full-video privacy/caption/new-user acceptance, final release matrix and publication/deployed-page verification remain separate requirements documented in the notes.

Checklist

Spec-driven development

• Reviewed root and relevant module SPECs.
• Recorded concrete no-SPEC-delta evidence before implementation.
• Implementation, test, and release documentation agree with existing SPEC.
• Used current SPEC as the implementation authority.

Quality and safety

• Focused and full Python checks, package build, and isolated installation passed.
• Changelog and release-preparation notes updated.
• No credentials, private user data, generated artifacts, environments, or logs committed.
• No new public media or Run artifacts included.
• No large binary added; npm/dependencies/runtime/workflows unchanged.