Feature hub authority
Platform spec ADR
Feature hub authority
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”Sibling articles under this feature previously restated requirements in inconsistent forms.
Decision
Section titled “Decision”This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Section titled “Consequences”Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
Section titled “Verification anchors”site/website/src/content/docs/platform-spec/compiler/build-pipeline/diagnostics-parity/index.mdxarticle bundle under the same feature directory.