ideas-funnel:lint

You can find orphan pages by running a vault linting scan that calculates inbound link density to detect pages with zero backlinks. This process flags isolated content, ensuring all wiki entries remain discoverable and structurally connected.

To validate markdown frontmatter schema rules, run an automated linter that enforces field requirements across Source, Concept, Entity, Bridge, Conflict, and Landing page types. This checks v1-to-v2 frontmatter transitions to maintain knowledge base hygiene.

Phantom entries and missing files in index.md occur due to index sync failures where the metadata registry diverges from actual vault contents. A vault linter detects these mismatches by comparing raw pages against index metadata.

Yes, you can safely lint a team knowledge base without modifying page content by using a non-destructive linter. These tools only write targeted frontmatter flags like ^stale and backlink_density, never deleting files or altering page bodies.

You migrate long timeline arrays in markdown frontmatter by running a vault linter that performs timeline sidecar migration. This process moves overly long arrays into separate sidecar files to maintain index integrity and schema compliance.