Examples

Platform spec article

Examples

Back to Snapshot and refresh contract ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0001-hub-authority Hub authority Accepted

   Hub authority

   Context

   One authority.

   Decision

   Hub owns snapshot/refresh MUST/SHOULD.

   Consequences

   IDE parity.

   Verification anchors

   beskid_lsp tests.

   Open full ADR page

2. 0002-invalidation-on-focus-and-manifest Invalidation Accepted

   Invalidation

   Context

   Stale snapshots.

   Decision

   Invalidate on focus, manifest, lock; debounce watchers.

   Consequences

   Config notification.

   Verification anchors

   session store.

   Open full ADR page

Articles

• Contracts and edge cases Strict guarantees for LSP snapshot lifecycle and refresh behavior. article Standard
• Design model Conceptual model for `Snapshot and refresh contract` and its subsystem boundaries. article Standard
• Examples Observable LSP refresh scenarios for snapshots and diagnostics. article Standard
• FAQ and troubleshooting Common LSP snapshot and refresh issues. article Standard
• Flow and algorithm End-to-end refresh flow for LSP workspace snapshots and diagnostics. article Standard
• Verification and traceability Tests and traceability for the LSP snapshot and refresh contract. article Standard

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

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

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).

Related spec docs

• Feature
  Snapshot and refresh contract

  Parent feature hub

• Feature
  Workspace and project explorer

  Focused project drives context cache

Focused project switch

1. User selects a workspace member in Project view.
2. Extension sends focused Project.proj URI to the LSP.
3. Server invalidates compilation_context_cache and schedules refresh_workspace_scan.
4. Diagnostics on open .bd files refresh against the new graph.

Edit loop

1. didChange updates buffer text and hash.
2. Analysis rebuilds snapshot with current CompilationContext.
3. After ~120ms quiet period, textDocument/publishDiagnostics fires.

Close and reopen

1. didClose removes open buffer entry.
2. hydrate_disk_after_close reads file from disk into workspace_index.
3. Reopen uses didOpen → fresh open snapshot (disk index entry removed).

CI parity check

Run beskid analyze --project <same Project.proj> and compare diagnostic codes to the Problems panel for the same file generation—discrepancies indicate cache or focus mismatch, not intentional divergence.