One authority.
FAQ and troubleshooting
Platform spec article
FAQ and troubleshooting
Spec standingStandard
-
Hub authority
Context
Decision
Hub owns snapshot/refresh MUST/SHOULD.
Consequences
IDE parity.
Verification anchors
beskid_lsp tests.
-
Invalidation
Context
Stale snapshots.
Decision
Invalidate on focus, manifest, lock; debounce watchers.
Consequences
Config notification.
Verification anchors
session store.
- Contracts and edge cases Strict guarantees for LSP snapshot lifecycle and refresh behavior.
- Design model Conceptual model for `Snapshot and refresh contract` and its subsystem boundaries.
- Examples Observable LSP refresh scenarios for snapshots and diagnostics.
- FAQ and troubleshooting Common LSP snapshot and refresh issues.
- Flow and algorithm End-to-end refresh flow for LSP workspace snapshots and diagnostics.
- Verification and traceability Tests and traceability for the LSP snapshot and refresh contract.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Diagnostics stuck after Project.lock update
Section titled “Diagnostics stuck after Project.lock update”Trigger a manifest save or run Beskid: Rescan workspace (extension command) so the server calls invalidate_compilation_cache and rescans. Verify lock materialization succeeded with beskid lock in a terminal.
Wrong project context for a file
Section titled “Wrong project context for a file”Confirm focused project in the Project view matches the Project.proj owning the file. Multi-root workspaces need the member containing the source path.
Slow initial open
Section titled “Slow initial open”Full workspace scan is O(files); excluded directories are skipped but large trees still cost IO. Narrow workspace roots or exclude generated folders from the VS Code workspace.
Stale hover after mod emit
Section titled “Stale hover after mod emit”Hard-invalidate paths apply when generated sources touch disk. If emit stays in-memory only, invalidation follows document generation counters—bump ANALYSIS_CACHE_VERSION when changing that contract.
BESKID_WORKSPACE_MEMBER_FOR_META_DEFAULT
Section titled “BESKID_WORKSPACE_MEMBER_FOR_META_DEFAULT”Sets default workspace member for meta scheduling when the environment variable is present; must align with extension focus for consistent mod attachment.