/**
 * `harn sync`: keep a curated subset of `.harnery/` live across machines
 * via rclone (typically a Google Drive remote, but any rclone remote works).
 *
 * Scope: a deliberately small set of file types: durable identities,
 * archived journals, council manifests. The high-churn machine-local
 * state (ledgers/, .pid-map/, active/, .last-intent.*) stays put.
 *
 * Subcommands:
 *   init:    interactive: `rclone config` walks through Google OAuth, then
 *            we record the chosen remote name in ~/.config/harnery/sync.json
 *   status:  diff local vs remote (rclone check --one-way)
 *   push:    local to remote (rclone copy)
 *   pull:    remote to local (rclone copy)
 *   list:    show what's in the remote
 *
 * Power users override via env (HARNERY_SYNC_REMOTE, HARNERY_SYNC_PREFIX) or by
 * editing the config file. Like `harn backup`, this surfaces rclone rather
 * than abstracting it.
 */
import type { Command } from "commander";
import type { EmitContext } from "../commander.js";
export declare function registerSyncCommand(program: Command, emit: EmitContext): void;
//# sourceMappingURL=sync.d.ts.map