Constellation Sync 0.6.0

- Remove Obsidian configuration sync completely. The vault configuration directory and .github/ are always excluded; configuration files left remotely by earlier versions are ignored and left untouched.

• Keep local-delete versus remote-edit conflicts unresolved until the user explicitly restores the remote version or deletes it remotely.
• Validate local and remote paths, including cross-platform case and Unicode collisions, so unsafe names cannot block or corrupt the rest of a sync.
• Stage downloads and local deletions until the remote side is confirmed, and use a single atomic Git Data update for large change sets.
• Harden persisted settings parsing, restore the 5-second default push delay, and expand CI, release validation, and regression coverage.

All devices should upgrade before resuming synchronization.

Constellation Sync 0.5.2

• graph.json is hard-excluded from config sync: the graph view rewrites it on every interaction, turning each cycle into a mid-sync change while carrying little value. The exclusion applies on every device once updated — no manual unchecking needed — and stale selections migrate out automatically. Existing graph.json files are frozen, not deleted.
• Stale artifacts (conflict copies from first adoption, frozen plugin data files) were removed from the sync branch.

Constellation Sync 0.5.1

• The local push debounce now defaults to 5 seconds (was 30 s): with the default 15 s check interval, the worst-case cross-device latency drops to roughly 20 seconds. Devices that explicitly picked 15 s or 60 s keep their choice.

Constellation Sync 0.5.0

Performance release.

• Routine checks no longer fetch the full remote file tree every cycle: the engine re-reads only the branch head through the strong-consistency channel and reuses the cached snapshot while the head is unchanged (git trees are content-addressed by head, so a matching head guarantees an exact tree). Steady-state polling drops from three REST calls plus a full-tree JSON parse to a single small read — the biggest cost on large vaults and on mobile.
• The dashboard snapshot no longer deep-clones the entire settings object (including the base manifest) on every status change; large read-only pieces are shared and only the small mutable arrays are copied.

Constellation Sync 0.4.10

• Desktop background sync no longer stalls when the Obsidian window is minimized or hidden: the remote check was gated on window visibility, so configuration edits and remote changes sat unsynced until the window was restored. Mobile keeps the visibility gate, since mobile OSes suspend background work.

Constellation Sync 0.4.9

• The delay between a local edit and its push (the debounce) is now configurable in the dashboard: 5 s, 15 s, 30 s (default) or 60 s. Combined with the 15 s check interval, end-to-end latency between devices can be brought down to roughly 20 seconds.

Constellation Sync 0.4.8

• Plugin sync is removed: the enabled community plugins list and per-plugin settings no longer sync, and everything under the plugins folder is hard-excluded. Stale selections migrate out automatically; existing files on devices and on the branch are left untouched (frozen, not deleted).
• Config defaults are now platform-aware: mobile skips hotkeys by default since hardware-modifier shortcuts barely apply there. Each device keeps its own selection, so Mac, Windows and mobile can differ.

Constellation Sync 0.4.7

• Fixed sync failures on macOS when empty folder chains were pruned: the adapter refuses to remove directories without the recursive flag there (EISDIR). Pruning now removes recursively after verifying the directory is empty, and a failed prune leaves an empty folder behind instead of failing the whole sync.
• Removing a path that turns out to be a directory falls back to recursive removal.

Constellation Sync 0.4.6

• The scan spinner now spins for at least one full rotation (~1 s): a local scan finishes in milliseconds and the previous flash read as "nothing happened".

Constellation Sync 0.4.5

• The metrics label "Last successful sync" is now "Last content sync" (上次内容同步): the timestamp intentionally refers to the last time real changes were carried over, not the latest no-change check.