chore: prepare Python 0.5.7 release

[woltspace-jerpint]

Summary

Prepare the Python 0.5.7 patch release from exact merged Dig commit 345bd9ad00a5fc086a2423563e6360d7ef473380.

• bump Python package version from 0.5.6 to 0.5.7;
• update the container's default Python package pin to 0.5.7;
• replace release notes with the owner-approved SSH Digging scope, safety boundary, and no-migration guidance;
• keep the separately distributed @woltspace/tui unchanged at 0.5.2.

Verification

• focused Python release gate plus Dig: 385 passed, 3 skipped;
• Node suite: 39 passed;
• full historical local suite: 1470 passed, 15 skipped, 16 known pre-existing environment/stale failures; zero Dig or release-diff failures;
• wheel/sdist metadata: twine check passed;
• exact Python/TUI source, identity, version, payload, and Docker-pin verification passed;
• git diff --check passed;
• commit author and committer verified as woltspace-jerpint[bot].

Local candidate artifact SHA-256 values (CI will rebuild its own immutable artifacts):

e6a24ae48794a858b4b182b54be641eae9034b0252c914e72296ed2c8e20154a  woltspace-0.5.7-py3-none-any.whl
3b813bc10159124b010672a4b2d5f907c5950b431d0fc166419000dd41850435  woltspace-0.5.7.tar.gz
e4a8aa760de760e8ccf0a3fc9e133b05bf2c4f7c8d5681146d3442009f87ed3f  woltspace-tui-0.5.2.tgz

The root npm install continues to report its existing high-severity audit item; this release changes no npm dependency or TUI byte.

Release boundary

This PR only prepares reviewed source metadata and notes. Merging does not publish, tag, create a GitHub release, or upgrade a lodge. Actual Python publication must use the reviewed publish.yml workflow from main, target registry=python, and pass the separately protected PyPI environment approval. No npm publication is intended.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
woltspace	Ready	Preview	Sep 20, 2026 8:14pm UTC