Activate Stack CLI 0.5.3 across distribution channels

[konojunya]

Background

Stack CLI 0.5.3 is now available from the immutable GitHub Release, crates.io, and the official Homebrew tap. The source repository still advertised 0.5.2 as the active release, and the Aqua smoke fixture still selected the previous archive set.

Implementation Approach

• Mark 0.5.3 as the active release in the machine-readable distribution contract and public installation guidance.
• Pin the Aqua fixture to the four published 0.5.3 archives and their verified SHA-256 checksums.
• Refresh the bundled Stack diagram skill from the final documentation revision.
• Keep package-manager ownership explicit: Homebrew, Aqua, and Cargo perform upgrades; the CLI does not self-update.

Release evidence:

• CLI source: d66ff06fc75337e7d4e966108e7793dddd6b1e53
• GitHub Release: https://github.com/stack-sh/cli/releases/tag/v0.5.3
• Cargo publication run: https://github.com/stack-sh/cli/actions/runs/34019883289
• Native release run: https://github.com/stack-sh/cli/actions/runs/34020068590
• Homebrew tap source: c8808224006020c38eed95d2e9af7a1f94743ad5
• Homebrew main verification: https://github.com/stack-sh/homebrew-tap/actions/runs/34020550184
• Documentation source: 16b8ac60219f5051bdb0319048e9b6200d3a614a
• Documentation manifest SHA-256: a0e1dc79a73553c6b6cc0bcf7ba8a5b5d134a63eedca3d181e41c1614faa5853

Testing Approach

• npm run skills:check
• node --test scripts/*.test.mjs (82 tests)
• python3 -m unittest discover -s scripts -p 'test_*.py' (15 tests)
• Rust 1.85 formatting, all-feature tests, and Clippy with warnings denied
• cargo publish --locked --dry-run --allow-dirty
• Standalone SVG render validation
• Exact Aqua checksum inventory validation for all four release targets

Review Perspectives / Points of Concern

• The Aqua registry revision intentionally remains unchanged because its generic package mapping already supports 0.5.3; only the selected version and generated checksum lock advance.
• No immutable release artifact is replaced.
• The generated skill is byte-for-byte synchronized from the pinned public documentation manifest.