chore(release): v1.2.0

[vxcozy]

Summary

Workspace version bump to 1.2.0 + CHANGELOG entry covering the v1.2 rollup.

Shipping in v1.2.0

Visualiser pane (CLI-86 / 87 / 89 / 91):

• Edge-to-edge rendering — removed the 1-col / 2-row inset and disabled DECAWM during the session so the bottom-right cell is safe
• Per-viz grid fill: Pulse scales to longer half-axis, Scope letterboxes with phosphor tint, Wave/Heartbeat/BarsDot paint tinted backgrounds instead of raw black
• Bar-family log/dB + AGC scaling via new scaling.rs so bars reach 80–90% height at normal volumes
• Snappier reactivity across ~15 braille viz (attack 50→25ms, release 2.5→1.2s, EnergyTracker retain 0.88→0.75)

Spotify Settings tab (CLI-90 / 92 / 93):

• Fourth picker tab (4 / Tab) showing Spotify auth status, Connect device name, config paths
• In-TUI OAuth: press a on Settings to sign in without leaving the TUI
• Client-side 5:30 deadline + control-session reconnect recovery so the UI unblocks after daemon crash

Audio diagnostics (CLI-88):

• RUST_LOG=clitunes::audio=trace emits per-60-frame FFT signal-path telemetry
• FftTap::snapshot_from regression test pinning sinusoid-amplitude preservation

Known limitation

Event::AuthStarted.url is always None today — librespot-oauth 0.8 holds the PKCE pkce_verifier privately, so we can't reconstruct a matching authorize URL from outside the crate. SSH / headless users see a pending-state hint that directs them to the clitunes auth subcommand, which prints the URL in their own terminal. Upstream contribution tracked as CLI-94.

Release-sensitivity check

Nothing release-sensitive has changed since v1.1.0:

• No release.yml edits
• No rust-toolchain.toml changes
• No Cargo.toml / Cargo.lock structural changes (only the version bump in this PR)
• No new workspace members, no dep-tree changes

Safe to skip the -rcN dry run per the project's pre-push CI parity rule.

Test plan

• cargo fmt --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace --all-features
• After merge: tag v1.2.0 on the merge commit, push tag, watch release.yml complete all four build targets + release step

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.