Specification over implementation notes
Platform spec ADR
Specification over implementation notes
Spec standingStandard
- Diagnostics parity (CLI and LSP) - Contracts and edge cases Required parity behavior and accepted differences between diagnostic surfaces.
- Diagnostics parity (CLI and LSP) - Design model Provenance model for parse and semantic diagnostics across compiler surfaces.
- Diagnostics parity (CLI and LSP) - Examples Practical examples comparing CLI and LSP diagnostics for equivalent failures.
- Diagnostics parity (CLI and LSP) - FAQ and troubleshooting Troubleshooting mismatched diagnostics between command-line and editor surfaces.
- Diagnostics parity (CLI and LSP) - Flow and algorithm Diagnostic generation flow for CLI frontend, lowering, and LSP analysis paths.
- Diagnostics parity (CLI and LSP) - Verification and traceability Source anchors and tests used to prevent diagnostic drift between compiler surfaces.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Section titled “Decision”Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Section titled “Consequences”Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_analysis/