vault-update

You update an Obsidian vault by running a process that inventories current configurations, compares them against the latest obsidian-blueprint methodology, and applies required changes to hooks and templates while preserving customizations.

During a vault update, your custom Obsidian templates and hooks are preserved. The update process specifically protects gitignore entries, spelling dictionaries, and custom frontmatter while applying incremental methodology changes.

You should apply obsidian-blueprint methodology updates when vault configurations drift after new template and hook releases, or after you have made vault-specific customization adjustments that need realignment.

Yes, the vault update process verifies Obsidian configuration integrity after applying changes. It follows an inventory, plan, apply, and verify workflow to ensure your vault setup remains stable and generates a concise report.

Yes, you need access to existing vault hooks, templates, and workflow catalogs to update your Obsidian vault. The process reads shared methodology references to safely apply changes to your current setup.