Critical Failure: Vault Empty

Error: CRITICAL FAILURE: Scanned X files but 0 were published.

The Problem

The system scanned your vault but found zero notes marked with publish: true and visibility: public.

This is almost always a sign of a structural or configuration error rather than a genuine lack of content.

The Why

• Corrupted Frontmatter: A syntax error in your YAML frontmatter (e.g., missing :, unquoted strings with special characters) can cause the entire file to fail parsing. If this happens to your main notes, the system ignores them.
• Missing Flags: You may have forgotten to add publish: true to your notes.
• Sync Issues: The Obsidian vault might not be correctly linked or synchronized in the build environment.

The Solution

1. Check the logs: Look immediately preceding this fatal error for specific parsing warnings.
2. Validate YAML: Ensure your frontmatter is strictly valid YAML.
3. Verify Flags: Check a few representative notes to ensure publish: true is set.
4. Local Build: Run pnpm run build locally to see the exact file failing to parse.