Module launch 

hlock launch: start a harness session that matches a lock (SPEC §7.8.6).

prepare verifies the installed harness, materializes the locked setup into an isolated config root (the same path as hlock sync --prefix), and returns the command and environment to exec. Launching a different harness than the lock’s translates the portable components (MCP servers, skills, instruction files, and the model where the target can reach it) into the target’s formats, and reports what doesn’t carry over.

Structs

LaunchOptions

LaunchPrep

What to exec, and what happened while preparing it.

Constants

ENV_DIR

Default directory for isolated launch environments.

Functions

env_prefix

Where a lock’s isolated environments live: ENV_DIR, or ENV_DIR/<stem> for a lock not named harness.lock, so two locks never share a root.

mcp_entry

One MCP server in a target harness’s config shape.

prepare

Prepare a launch: verify, materialize, and build the command to exec. args are passed through to the harness (or, for a code harness, joined into the prompt).