Verification and traceability

Platform spec article

Verification and traceability

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

Test anchors

Concern	Location
Resolver + graph	compiler/crates/beskid_tests/src/analysis/resolve.rs
Analysis services	compiler/crates/beskid_tests/src/analysis/pipeline/core.rs
Document analysis build	beskid_analysis::services unit/integration tests

Traceability

Requirement	Evidence
ANALYSIS_CACHE_VERSION bump forces rebuild	Lifecycle tests or manual protocol check when version changes
Skip directories during scan	should_skip_dir_for_scan unit coverage in workspace_scan.rs
Invalidation on manifest change	backend.rs configuration handler paths
Diagnostic debounce	Revision counter logic in schedule_publish_diagnostics

Manual verification

1. Open multi-file project; edit one file; confirm diagnostics update after pause.
2. Change Project.proj; confirm all open files refresh.
3. Compare beskid analyze output to LSP Problems for same snapshot generation.

Spec updates

Changes to cache keys, skip lists, or debounce intervals must update this article and the VS Code extension status contract when user-visible phases change.