Reference: diagnostic ID policy
Reference: diagnostic ID policy
Section titled “Reference: diagnostic ID policy”Machine-readable registry: contracts/diagnostics/registry.v1.yaml.
Principles
Section titled “Principles”- Append-only codes — Once published in a stable release, a diagnostic
codestring is not repurposed; deprecate via alias messages instead. - Namespaced owners
vox-compiler—E####style,lint.*,typecheck.*,vox/<category>/<slug>for newer namespaces (mesh language spine plan).vox-code-audit— hierarchical rule IDs such asskeleton/untested-pub-api,stub/todo,security/hardcoded-secret/*,ai-laziness/*.
- Disjoint prefixes — Audit rule IDs must not exactly equal any compiler
codelisted invox_compiler::typeck::diagnostics::codes::ALL_COMPILER_DIAGNOSTIC_CODES(enforced bycrates/vox-compiler/tests/audit_rule_collision.rs). The YAML registry summarizes reserved prefixes for humans.
Consumers
Section titled “Consumers”- CLI JSON diagnostics (
VoxCompilerDiagnosticPayload) —crates/vox-compiler/src/typeck/diagnostics.rs. vox check --for-llmenvelope —crates/vox-cli/src/pipeline.rs.- LSP
Diagnostic.code—crates/vox-lsp/src/lib.rs.