Apply owned output and recover interrupted changes

Plan or apply contained file changes with ownership checks, backups, an exclusive lock, and recovery validation.

Usage

apply_files(root, desired, remove = character(), mode = c("check",
    "plan", "apply"), headers = "# Generated with specmill; do not edit by hand.",
    owned = NULL, validate = NULL)
recover_client(root, mode = c("plan", "apply"))

Arguments

root: Explicit existing client root directory.
mode: Check or plan without writes; apply validated output.
desired: Named list of relative paths and generated text.
remove: Relative paths to remove only if owned.
headers: Reserved compatibility argument; headers alone never establish ownership.
owned: Optional client ownership predicate for existing files.
validate: Optional zero-argument input revalidation called after acquiring the apply lock and before any file changes.

Value

apply_files() returns file/path/action records, including manifest changes. recover_client() returns journal-keyed restoration plans (invisibly for apply), with path, backup, and existed fields. Invalid recovery data or failed restoration raises an error and retains the journal.

Details

Most callers should use generate_client() for reconciliation. apply_files() parses R output before mutation and checks manifest ownership; headers alone do not authorize replacement. A custom owned predicate is an advanced client trust boundary. Apply refuses conflicting protected writes. Recovery plan validates journals and returns restoration actions; recovery apply restores backups and removes completed journals. Confirm no live writer before resolving a stale lock. Never delete journals to bypass recovery. There is no cross-file filesystem transaction.

Note

Ownership is recorded in .specmill/manifest.json. Locks and transaction journals use the .specmill- prefix.