Diagnostics and workspace analysis

Platform spec node

Diagnostics and workspace analysis

Back to LSP ◎ Open in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs

No architecture decision records under adr/ for this feature yet. Standard features must publish at least one ADR or keep a ## Decisions summary on the hub.

Articles

• Diagnostics and workspace analysis LSP diagnostic and workspace analysis contracts for Beskid editor integrations. article Standard Reviewed Mon May 11
• IntelliSense capabilities and behavior Normative LSP IntelliSense feature contract for Beskid editors. article Standard Reviewed Mon May 11

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 3 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
scope	yes	yes
features	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Area
  LSP

  Parent area

• Feature
  Diagnostics parity (CLI and LSP)

  Common diagnostic provenance rules

• Area
  Compiler Mods

  Meta diagnostics and host policy

Normative platform contract

1. LSP document analysis shall support cached and cold diagnostic paths with equivalent semantic rule outcomes.
2. Workspace scanning and symbol features shall use project graph context rather than isolated file parsing when available.
3. Document analysis snapshots for .bd IntelliSense shall be built with the same CompilationContext / ProgramAssembly path as project-aware diagnostics (build_document_analysis_with_context in beskid_lsp::session::lifecycle), not single-file Resolver::resolve_program alone.
4. Manifest diagnostics for .proj files shall be surfaced through project-specific diagnostic adapters.
5. LSP diagnostics shall preserve severity and code identity from compiler analysis diagnostics.
6. Documentation diagnostics — For .bd buffers where DocumentAnalysisSnapshot is available, the server shall merge doc_diagnostics (documentation mini-language, codes W161x and W162x) with diagnostics from analyze_source_with_compilation_context / semantic rules so editors show a single unified list per URI.
7. Meta diagnostics — Diagnostics emitted during mod analyze/rewrite phases must use the same transport, code strings, and severity mapping as semantic diagnostics from beskid_analysis so CLI and LSP remain interchangeable for CI diffing. The LSP must refresh these diagnostics whenever the mod host invalidates a document generation (see Snapshot and refresh contract).
8. Workspace analysis with Mod projects — When the resolved graph includes Mod nodes, analysis must schedule meta after the same CompilationContext snapshot rules as CLI; the server must not analyze host sources in a mode that skips attached Mod unless a documented power-saving mode is enabled uniformly across commands.

Implementation anchors

• compiler/crates/beskid_lsp/src/diagnostics.rs
• compiler/crates/beskid_lsp/src/workspace_scan.rs
• compiler/crates/beskid_lsp/src/features
• compiler/crates/beskid_analysis/src/doc/validate.rs