Drift risk.
FAQ and troubleshooting
Platform spec article
FAQ and troubleshooting
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).
Why does analyze pass in the IDE but fail in CI?
Section titled “Why does analyze pass in the IDE but fail in CI?”The CLI runs the full project graph and lock policy. Ensure CI calls beskid lock (or checks in Project.lock) and sets BESKID_CORELIB_ROOT when not using the bundled corelib layout. Compare against the focused Project.proj the extension sends to the LSP.
build cannot find corelib / Std
Section titled “build cannot find corelib / Std”Verify BESKID_CORELIB_ROOT points at a tree containing beskid_corelib/Project.proj, or run beskid corelib materialization. Superrepo checkouts should resolve via compiler/corelib/beskid_corelib discovery in resolver.rs.
Diagnostics differ between analyze and build
Section titled “Diagnostics differ between analyze and build”build runs lowering and may surface codegen-only failures. Start with analyze; if clean, inspect AOT/link logs. Mod generator failures appear in both when semantic gates run.
run works locally but not in containers
Section titled “run works locally but not in containers”Confirm the JIT runtime matches the target triple and that syscall-backed corelib surfaces are available in the image. Release AOT (build) is the supported path for minimal runtime images.
Where are mod artifacts cached?
Section titled “Where are mod artifacts cached?”beskid mod subcommands and the analysis cache under the package/object store documented in Compiler Mods. Stale caches: use documented clean/rebuild policy from the mod manifest artifactPolicy.