Lock alignment.
FAQ and troubleshooting
Platform spec article
FAQ and troubleshooting
Spec standingStandard
-
Hub authority
Context
Decision
Hub owns workspace and lock rules.
Consequences
CLI/IDE defer.
Verification anchors
resolution tests.
-
CLI lock mutations
Context
Resolver bypass risk.
Decision
fetch/lock must use CLI resolver.
Consequences
Matches VSC-0002.
Verification anchors
CLI integration.
- Contracts and edge cases Workspace and lockfile guarantees for tooling operators.
- Design model Conceptual model for workspace manifests, lockfiles, and materialized dependency roots.
- Examples Workspace and lockfile examples for tooling workflows.
- FAQ and troubleshooting Workspace and lockfile troubleshooting for tooling users.
- Flow and algorithm Lock synchronization, fetch, and update flows for workspace tooling.
- Verification and traceability Tests and traceability for workspace and lock tooling contracts.
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).
Project.lock out of date
Section titled “Project.lock out of date”Run beskid lock or beskid update from the project root. If manifests changed on another branch, merge lock conflicts explicitly—do not hand-edit materialized_root without understanding fetch layout.
Registry alias not found
Section titled “Registry alias not found”Add the alias to Workspace.proj registry { } blocks or use the default URL. Verify beskid pckg config points at the same host (PckgClientConfig).
Member project not in graph
Section titled “Member project not in graph”Check member.path is relative to the workspace root and ends with Project.proj. Typos in member.id break --workspace-member CLI flags.
LSP uses wrong dependency roots
Section titled “LSP uses wrong dependency roots”Delete .beskid cache only when documentation recommends it; otherwise refresh lock and rescan workspace. Ensure focused project matches the lock’s root_manifest.
Workspace publish rejected by pckg
Section titled “Workspace publish rejected by pckg”Server validators (WorkspacePackageManifest, PackageArtifactValidator) enforce readme, docs, and member consistency—align local beskid pckg pack output with pckg client contract before retrying upload.