dsh-time-machine

LIMITATIONS

Known limitations

- Host-local Git repositories and bounded UTF-8 regular files only. Binary, oversized, linked, ignored-untracked and nested-repository contents are excluded. Snapshot exclusions are surfaced. - A turn captures workspace changes, including concurrent human edits; it cannot attribute authorship. Stop external writers before restoring. File hashes and cooperative locks do not provide atomic isolation from arbitrary outside processes. - Restoration is per-file, journaled, and conflict checked; multi-file replacement is not atomic. An interruption requires `/time_machine recover`. Existing user edits that differ from the journal block recovery. - Git index, commits, databases, deployments, empty directories, ACLs and extended attributes are not restored. Checkpoints preserve ordinary mode bits; Windows semantics differ. - An interrupted turn baseline is compared with current disk on the next access, potentially including intervening manual edits. Capture failures warn but do not block ordinary agent work. - Lists show the current session's latest 50 records. Older ids remain addressable. Cross-session browsing, automatic retention, branch switching and full-text search are deferred. Stored source history must be protected as project data. - Exact DSH peer versions are required. No compatibility exemption or runtime installation is performed automatically.