frontmatter-guard

To validate YAML frontmatter, you can use an automated audit and fix workflow that detects missing markers, parse failures, and slug mismatches, then auto-repairs them while generating .bak file backups to ensure safe metadata mutation.

YAML frontmatter parsing fails during ingestion due to missing opening or closing frontmatter markers, null bytes, nested quote issues, or structural formatting errors that prevent the YAML parser from reading the metadata block correctly.

Auditing a large repository involves running a maintenance pass across all brain pages to surface frontmatter issues like missing markers and slug mismatches, ensuring metadata consistency and reliable downstream processing before ingestion occurs.

The frontmatter repair process does not permanently destroy original files, as it creates .bak backups when mutating content to safely preserve the unmodified source data before applying any automated frontmatter corrections.

Fixing slug mismatches across multiple sources requires running a validation workflow aligned with central frontmatter integrity rules, automatically detecting and correcting identifier discrepancies to ensure metadata consistency across the corpus.

Null bytes break YAML frontmatter ingestion because they corrupt the text encoding structure, causing the YAML parser to fail when attempting to read the metadata block, which necessitates an automated validation and repair process to strip invalid characters.