Sibling articles under this feature previously restated requirements in inconsistent forms.
Dependency workspace and lockfile - FAQ and troubleshooting
Platform spec article
Dependency workspace and lockfile - FAQ and troubleshooting
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Dependency workspace and lockfile.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/build-pipeline/dependency-workspace/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Dependency workspace and lockfile.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_analysis/
-
This feature hub specifies how manifests become prepared dependency workspaces and how `Project.lock` is synchronized un
Context
This feature hub specifies how manifests become prepared dependency workspaces and how
Project.lockis synchronized under--lockedand--frozen.Decision
The reference compiler must implement Dependency workspace and lockfile as documented in this feature hub and its article bundle.
Consequences
Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
compiler/crates/beskid_analysis/
- Dependency workspace and lockfile - Contracts and edge cases Normative behavior for lock mismatch, missing registry artifacts, and policy flags.
- Dependency workspace and lockfile - Design model Data model for compile plans, prepared workspaces, lock records, and dependency source roots.
- Dependency workspace and lockfile - Examples Concrete examples for frozen and locked workflows with project dependencies.
- Dependency workspace and lockfile - FAQ and troubleshooting Operational troubleshooting for lockfile synchronization and dependency workspace preparation.
- Dependency workspace and lockfile - Flow and algorithm Workflow from compile-plan construction to workspace materialization and lockfile synchronization.
- Dependency workspace and lockfile - Verification and traceability Source anchors and test evidence for compile-plan and lockfile behavior.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Why did lock command update files unexpectedly?
Section titled “Why did lock command update files unexpectedly?”Run with --frozen to prevent lockfile writes; normal mode allows synchronization.
Why does locked mode fail in CI but not locally?
Section titled “Why does locked mode fail in CI but not locally?”Local dependency graph or manifest may differ from committed lockfile.
Where are dependency sources materialized?
Section titled “Where are dependency sources materialized?”Under the workspace object tree (for example obj/beskid/deps/src) managed by workflow services.