Preserve explicit TreeFocus overrides across Obsidian reloads

[Copilot]

Explicit folder/file focus overrides could be dropped on reload because startup cleanup treated non-rendered File Explorer items as orphaned. This led to intermittent loss of saved focused views despite paths still existing in the vault.

• Problem

  • Startup cleanup derived validity from current File Explorer render state, which is transient/incomplete during reload.
  • Valid persisted overrides were removed when their nodes were not yet present in the explorer tree.

• Change

  • Reworked orphan detection in performPluginCleanupTask() to validate persisted override paths against vault existence, not UI visibility.
  • Cleanup now removes only entries whose paths are truly absent from the vault.

• Behavioral impact

  • Persisted fileOverwrites survive reloads unless the underlying file/folder was actually deleted.
  • Eliminates random reset behavior while keeping orphan cleanup semantics intact.

const availableExplicitPaths = [...PluginSettings.getExplicitModePaths()];
const orphanedExplicitPaths = availableExplicitPaths.filter(
  (path) => this.app.vault.getAbstractFileByPath(path) === null
);

[Copilot]

Pull request overview

This PR fixes intermittent loss of persisted explicit TreeFocus overrides across Obsidian reloads by changing startup cleanup to validate overrides against vault existence rather than transient File Explorer render state.

Changes:

• Reworked performPluginCleanupTask() orphan detection to use app.vault.getAbstractFileByPath(path) === null.
• Removed File Explorer traversal during cleanup so explicit overrides aren’t dropped just because nodes aren’t rendered yet.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.