Linux golden-home capture and restore
The complete preparation, saving, restoration and timeout-recovery procedure is
Linux provisioning at .yoke/docs/verification/test-machines/linux-host-provisioning.md.
Its audit distinguishes live evidence from unverified steps.
Omitting --destination captures beside the current golden in
<user>-home-YYYYMMDDTHHMMSSZ, using UTC, just like automatic harness refresh.
Later captures on the same day get a new name. An exact collision with the
registered golden refuses golden_capture_destination_collision; retry after
the UTC second changes or pass a different absolute --destination. An explicit
destination is used as given. The first capture requires an explicit destination.
Required desktop browser state
Desktop Chromium browser sign-ins are kept live through Linux reset and are never captured into golden snapshots. The existing snap Chromium sign-in store under ~/snap/chromium/common/chromium is preserved only when present; reset must not restore stale sign-in state from an older golden. Chromium is stopped before preservation so its on-disk state is flushed.
Require a reset receipt and real browser sign-in proof against the selected release before relying on this contract. This procedure alone does not prove that a candidate or installed release implements it.
Linux reset gives systemd user service mutations the relay's shared 180-second
operation budget; inventory queries retain their 30-second limit. A
linux_yoke_service_command_timeout names the command and budget. Its job may
still be running: inspect the reported job before retrying the sealed baseline.
Failed archive operations retain bounded, redacted native exit/stdout/stderr in
the receipt and exploratory-mission preparation, even without a JSON receipt.
Before writing, capture refuses golden_capture_insufficient_space when the
destination filesystem cannot hold the home's file bytes, and tells you to
remove every other snapshot beside the registered goldens (keep each project's
golden for this machine and its .probes and .manifest files) and retry
yoke test-machine golden-capture. After the new golden is registered, older
snapshots in that parent are deleted, except a golden another project registered
for the same machine. A parent named for the test user holds only that user's
snapshots. golden_snapshot_retention_failed means the new golden is already
registered and leftovers remain.
Linux and Windows/WSL2 reset probe yoke, uv and uvx separately on login
and SSH shells. Only a framed absolute resolved path counts as present;
unrelated shell startup output does not. tool_resolution retains each tool's
state (absent, present, probe-failed), shell and resolution exit codes,
resolved path, and bounded redacted stdout/stderr. reset_tool_probe_failed
requires repairing the named shell or SSH probe before retrying; surviving
paths refuse as reset_absence_not_proved. Presence summaries are unknown
(null) when probes failed without observing a path.