Module release_handles 

running-process maintenance release-handles --path <PATH>.

Phase 1 of #228 (issue #230). The goal is to make rm -rf <PATH> reliable on Windows even when a daemon process is holding handles inside <PATH> — see soldr#710.

Per-platform behaviour

• POSIX: no-op. Linux/macOS use delete-on-close semantics, so rm -rf always succeeds; the subcommand exits 0 with an informational message.
• Windows: scaffold-only in Phase 1. The full handler depends on the manifest registry that ships in Phase 2 (#231). Until then the subcommand returns a successful “no manifests to scan yet” result so downstream callers (clud-pr, soldr cleanup) can start wiring the call site without changing their exit-code handling later.

Why ship the POSIX no-op now?

Cross-platform tooling (soldr’s clud-pr workflow, CI helpers) can call the subcommand unconditionally and get the right behaviour on every host. Without the no-op surface, every caller would need its own cfg(unix) short-circuit.

Structs

ReleaseHandlesAuthorization

Inputs used to authorize a future daemon-side release-handles request.

ReleaseHandlesOutcome

Result of one release-handles invocation.

Enums

ReleaseHandlesAuthorizationError

Errors emitted by authorize_release_handles_request.

ReleaseHandlesError

Errors emitted by run_release_handles.

Functions

authorize_release_handles_request

Authorize a daemon-side release-handles request.

run_release_handles

Run the release-handles subcommand. Cross-platform entrypoint called by runpm maintenance release-handles.