Drift risk.
Verification and traceability
Platform spec article
Verification and traceability
Spec standingStandard
-
Hub authority
Context
Decision
Hub owns MUST/SHOULD.
Consequences
Articles defer.
Verification anchors
trudoc.
-
Shared pipeline
Context
CLI/LSP divergence.
Decision
Use beskid_analysis aligned with LSP.
Consequences
Parity.
Verification anchors
pipeline tests.
- Contracts and edge cases Strict guarantees and failure modes for build, analyze, and run CLI behavior.
- Design model Conceptual model for `Build, analyze, and run contract` and its subsystem boundaries.
- Examples Concrete CLI invocations for build, analyze, and run workflows.
- FAQ and troubleshooting Common questions and fixes for build, analyze, and run CLI behavior.
- Flow and algorithm Lifecycle and execution flow for `Build, analyze, and run contract`.
- Verification and traceability Tests and traceability for the build, analyze, and run CLI 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).
Automated coverage
Section titled “Automated coverage”| Area | Location |
|---|---|
| Pipeline + workspace resolution | compiler/crates/beskid_tests/src/analysis/pipeline/core.rs |
| Project graph / corelib layout | compiler/crates/beskid_tests/src/projects/corelib/ |
| CLI integration | Tests adjacent to compiler/crates/beskid_cli/src/commands/*.rs where present |
Traceability matrix
Section titled “Traceability matrix”| Contract clause | Verification |
|---|---|
Shared CompilationContext | Pipeline tests assert identical diagnostics for CLI vs in-process analysis hooks |
| Lock policy enforcement | Workspace tests with missing/stale Project.lock |
| Implicit corelib | layout.rs and parser rejection tests for noCorelib |
| Mod round caps | Compiler-mod integration tests under compiler/crates/beskid_tests mod suites |
Release checks
Section titled “Release checks”Compiler CI builds the beskid binary and runs the workspace test crate. Changing command surfaces must extend an existing integration test or add a focused CLI test rather than relying on manual smoke runs only.
Spec maintenance
Section titled “Spec maintenance”When adding subcommands or flags, update this feature bundle, the CLI area index, and any pipeline phase registry entries in the same change set.