[2026-06-01] taiga sync: .stignore family/documents/vault-sync-2026-05-13-08-01.md family/documents/vault-sync-2026-05-20.md family/documents/vault-sync-2026-05-21.md family/documents/vault-sync/2026-05-13-sync.md

family/documents/vault-sync-2026-05-20.md

@@ -0,0 +1,31 @@
+---
+title: Vault synchronization report
+date: 2026-05-20 18:00
+tags:
+  - vault
+  - sync
+  - cron
+---
+
+Vault synchronization run completed: exit code 0.
+Host: Тайга home server.
+Script: /opt/data/sync-vault.sh
+Log location: /tmp/vault-sync.log
+
+Summary:
+- Script finished without a shell error (exit code 0).
+- The log shows repeated stash operations on the 'main' branch with IDs like sync-stash-1778688086, sync-stash-1778691635, etc.
+- The log contains numerous entries indicating files were deleted from the vault notes (example: .obsidian/hotkeys.json, Untitled 1.md, Untitled 2.md, Untitled 3.md).
+- Several files under wiki/ and work/Projects were listed as modified or deleted across multiple stash cycles.
+- After stash cycles, the log shows lines like "Nothing to commit" and occasional "Changed"/"Deleted" entries.
+
+Observations:
+- The vault appears to have undergone mass deletions and modifications during this sync pass. These changes could be intentional clean-up or automation side-effects. Given the volume, a review is recommended.
+- The final state indicates there is no pending changes to commit in some cycles, but in others there are many deletions and modifications pending commit.
+
+Recommended next actions:
+- Review the diff of recent commits to confirm which files were deleted or modified and whether this aligns with expected maintenance.
+- If unintended, consider restoring from last known good commit or stash, and adjust the sync script to avoid mass deletions.
+- Consider archiving or snapshotting the Obsidian vault state before running automated syncs in the future.
+
+If you want, I can export the raw /tmp/vault-sync.log for archival or attach a full diff report to the vault as another note.