Cut 0.32.0

The [Unreleased] section as it stood becomes the release, in two parts. A warm
launch now says what it skipped: an attach to a workspace devpod already has
prints how far behind its checkout is, computed from dl's own clone and reaching
no network, so "this devcontainer boots correctly" cannot be concluded against a
container built before the repository had a `.devcontainer/`. And `dl --prune`
reclaims the per-workspace launch locks, which nothing short of `--purge`
removing the whole cache directory had ever reached.

The lock half needed two guards, not one. Unlinking an `flock`'d file is safe
only if every side asks, after its lock, whether the path still names the inode
it just locked -- the acquisition, so a run whose file went out from under it
queues again against the live one, and the sweep, so it does not unlink a file
somebody else created and is holding. A sweep that only took the lock would
still have removed a live launch's file, because an inode already unlinked has
no holders and locking one always succeeds.

**0.32.0 and not 0.30.0.** 0.30.0 remains cut on `feat/aid-appendable-agent-flag`
and has still not landed, so it stays skipped on the published channels for
c1ef6f5's reason: taking the number here would collide with its tag or ask that
branch to re-cut.

Mechanical otherwise. The README's conda badge and its `dl --version` transcript
move with the version, which test_readme_cli_doc holds, and the lockfile follows
the workspace version for dl, aid and devlaunch-test-support.

Cut on a release branch so the version bump is a reviewable diff and the publish
fires on the merge.

Claude-Session: https://claude.ai/code/session_01U4SpX4ixqQG5R8hErsPMot

Author: blooop

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.32.0] - 2026-09-04
+
 ### Added
 
 - **A launch that attaches to a workspace devpod already has now says how far

README.md

@@ -19,7 +19,7 @@ one argument instead of a clone, a config file and a build command.
 [![GitHub pull-requests merged](https://badgen.net/github/merged-prs/blooop/devlaunch)](https://github.com/blooop/devlaunch/pulls?q=is%3Amerged)
 [![GitHub release](https://img.shields.io/github/release/blooop/devlaunch.svg)](https://GitHub.com/blooop/devlaunch/releases/)
 [![PyPI](https://img.shields.io/pypi/v/devlaunch)](https://pypi.org/project/devlaunch/)
-[![Conda](https://img.shields.io/badge/conda-v0.31.0-brightgreen?logo=anaconda)](https://prefix.dev/channels/blooop/packages/devlaunch)
+[![Conda](https://img.shields.io/badge/conda-v0.32.0-brightgreen?logo=anaconda)](https://prefix.dev/channels/blooop/packages/devlaunch)
 [![License](https://img.shields.io/github/license/blooop/devlaunch)](https://opensource.org/license/mit/)
 [![Platform](https://img.shields.io/badge/platform-linux--64-blue)](https://github.com/blooop/devlaunch/releases)
 [![Pixi Badge](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/prefix-dev/pixi/main/assets/badge/v0.json)](https://pixi.sh)
@@ -276,7 +276,7 @@ clone, and [docs/cleanup.md](docs/cleanup.md) says what it carries one past and
 
 ```bash
 $ dl --version
-dl 0.31.0
+dl 0.32.0
 ```
 
 `--devcontainer <variant|path>` picks a non-default `devcontainer.json`. A bare name means

rust/Cargo.lock

@@ -11,7 +11,7 @@ members = [
 # The single source of the version (docs/rust-rewrite-plan.md: cutover ships
 # 0.1.0, version read from Cargo.toml).
 [workspace.package]
-version = "0.31.0"
+version = "0.32.0"
 edition = "2024"
 license = "MIT"
 repository = "https://github.com/blooop/devlaunch"