Expand description
socket-patch unlock — inspect (and optionally release) the
<.socket>/apply.lock advisory file lock used by mutating
subcommands.
Default behavior (no flags): probes the lock and prints
status: "free" | "held". Returns 0 when free, 1 when held —
lets CI gating and monitoring tooling pattern-match the exit
code without parsing JSON.
With --release: when the lock is free, also deletes the lock
file. The file is normally retained across runs (see
apply_lock docs — the inode persists so subsequent acquires
don’t race on file creation), so --release exists for
operators who want a true clean slate. Refused when the lock is
held — that’s the --break-lock flag’s job on the mutating
subcommands, and routing the two through different verbs makes
the dangerous override explicit.