Multi-path corelib discovery
Platform spec ADR
Multi-path corelib discovery
Spec standingStandard
- Contracts and edge cases Normative guarantees and known edge cases for `Corelib discovery and packaging`.
- Design model Conceptual model for `Corelib discovery and packaging` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Corelib discovery and packaging` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Corelib discovery and packaging`.
- Flow and algorithm End-to-end control flow for corelib discovery, materialization, and packaging.
- Verification and traceability How `Corelib discovery and packaging` requirements map to tests and implementation anchors.
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).
Context
Section titled “Context”Developers run from superrepo, installed CLI, or CI without divergent roots.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
BESKID_CORELIB_ROOT | Points at root containing beskid_corelib/Project.proj |
| Walk | Ancestor search for compiler/corelib/beskid_corelib |
| Bundle | beskid_cli ensure_corelib_ready materializes embedded tree |
Consequences
Section titled “Consequences”Missing roots fail fast with resolver diagnostics.
Verification anchors
Section titled “Verification anchors”corelib_runtime.rs; resolver.rs tests.