Harness Migration

First confirm a broken harness/ ledger actually has a generation mismatch rather than some other fault. If it does, replay it into a freshly initialized current-format repository; the source is never written to. New destination initialization has the identity prerequisites documented in harness-install; an isolated daemon root does not provide a signed-in identity. Replay is the only supported migration path — there is no in-place repair tool.

This skill assumes nothing is installed. It fetches the current source into a throwaway directory and runs everything from there. A Harness installation already on the machine — including a running daemon — is left untouched.

Before anything: confirm this is the right document