Expand description
hlock sync: rehydrate a locked harness setup (SPEC §7.8.5).
Syncing is a Plan of Steps, each satisfied (already true here),
auto (hlock can do it), or manual (it needs the user, and the step says
exactly what to run and why). Planning is side-effect free; run_step
performs one auto step. Package-manager installs and model downloads are
only auto when the caller opts in (install, pull); otherwise they’re
manual steps with the command to run.
Structs§
- Plan
- Step
- Sync
Options - Where a sync materializes the setup.
Enums§
- Action
- One concrete thing an
autostep does.
Functions§
- dockerfile
- A Dockerfile and entrypoint for a plan built with
SyncOptions::docker. Files the plan writes under<context>/homeare copied to the image’s home; secrets stay placeholders in the image and are filled from-eat start-up. - plan
- Build the sync plan for a lock. Nothing is changed.
- rehydrate_
skill - An Agent Skill (
SKILL.md) that walks an agent through the plan’s remaining steps. - run_
step - Perform one
autostep and describe what happened.