workspace-unfreeze

# Workspace unfreeze ## Contract | Field | Bound contract | |---|---| | Trigger | The user runs /workspace-unfreeze on a frozen path | | Authority | Human-gated: requires explicit human invocation, previews the target marker file and the deletion consequence, and asks before deleting the freeze lock marker file; otherwise reversible local: deletes only the freeze lock marker file; rollback is recreating the marker file. No remote mutation. | | Side effect | Deletes the freeze lock marker file for the named path. The deletion is unrecoverable, but the marker is re-creatable by re-creating the `<path>.freeze-lock` file beside the path with content naming the target path | | Done | The named path is editable again (no freeze lock marker present for it) | ## Inputs - **Path** (required): the frozen path to unfreeze. ## Procedure 1. Receive the path argument from the explicit /workspace-unfreeze invocation. Do not act on any model-generated or inferred path. Done when: the path argument is confirmed as human-supplied. 2. Resolve the marker path from the invocation: accept an explicit marker path from the human, or derive it from the freeze convention: a marker file named `<path>.freeze-lock` beside the frozen path, whose content names the target path. Verify the resolved file exists and names the target path. If it does not, treat as Marker not found. Never glob or scan for candidate markers. Done when: the marker file path is resolved and verified, or the path is confirmed ...