error-registry.yml

Per-rule severity overrides for validation, in a single file at the project root next to codocation.yml. The file holds only the rules you changed; everything else uses the defaults below. This catalog mirrors the plugin's registered DiagnosticCode values; only these codes are valid severity-override keys.

severities:
  MD_004: error
  NAV_002: suppressed

Values: error (blocks build and deploy), warning, weak-warning, suppressed (the rule stops reporting). The plugin's Severity.INFO is presented here as weak-warning.

Rules and default severities

Code	Default	Checks
NAV_001	error	A navigation entry points to a missing page
NAV_002	warning	A page is in no navigation, so it will not appear on the site
NAV_003	warning	The same page appears several times in one section
NAV_004	error	The navigation file is malformed
NAV_005	error	A nested section where only flat items are allowed (header/footer)
NAV_006	error	An item combines page, section, and href
NAV_007	error	A bare path used as a key instead of `page:`
NAV_008	error	More than one page marked as home
NAV_009	error	An item kind not allowed in this section
NAV_010	error	An invalid navigation item field
NAV_011	warning	The documentation has no description

Markdown

Code	Default	Checks
MD_001	error	The page has no title
MD_002	error	The frontmatter is invalid
MD_003	warning	An unknown frontmatter field (with a did-you-mean hint)
MD_004	error	An internal path or namespace is invalid, or a canonical page, image, attachment, or asset target is missing
MD_005	warning	A link points to a heading that does not exist
MD_006	weak-warning	The title is set twice (frontmatter and an H1)
MD_007	warning	More than one top-level heading
MD_008	error	A link target is not included in the current site's tree
MD_009	error	A link target exists, but its location is not published

Configuration

Code	Default	Checks
CFG_001	error	A configured branding or media file is missing, including the logo or favicon
CFG_002	error	Two sites share one base path
CFG_003	error	A configuration file has an invalid setting

Localization

Code	Default	Checks
I18N_001	error	A page is missing from a requested locale
I18N_002	error	A page is marked `fallback` in the default locale
I18N_003	error	A page is marked `fallback` while a requested-locale file exists
I18N_004	error	A locale-shaped directory is not configured

Landing sections

Code	Default	Checks
LAND_001	error	The legacy `sections:` frontmatter key (moved into body directives)
LAND_002	error	A `:::` directive has no closing fence
LAND_003	error	An unknown section name
LAND_004	error	A malformed attribute (not `key="value"`)
LAND_005	warning	An attribute the section does not recognize
LAND_006	error	A required attribute is missing
LAND_007	warning	An invalid button value (use "primary" or "secondary")
LAND_008	error	A closing fence with no open directive
LAND_009	warning	A card outside a features/steps container
LAND_010	warning	An invalid section background value (use `tinted`)
LAND_011	error	A button annotation is detached from its link

Definitions

Code	Default	Checks
GLOS_001	error	A glossary term is not defined
GLOS_002	warning	A glossary term is defined more than once
KEYS_001	error	A keyboard shortcut action is not defined
KEYS_002	warning	A keyboard shortcut action is defined more than once

Failures without a stable registry code

Some structural validation and reader failures currently have no registered diagnostic code. Unknown or incomplete definition payloads, invariant definition changes, and reader failures such as an absent or unparseable codocation.yml, invalid default-locale selection, a missing required site/locale tree, or a fallback page with no default-locale source are reported outside the code table until a stable code is implemented. Legacy paths are never read and do not receive a fabricated migration code. Use only the registered codes above when writing error-registry.yml overrides.