Skip to content

wit: pin nexum:host to crate-local wit-deps#481

Open
mfw78 wants to merge 1 commit into
feat/m5-dep-sync-cifrom
feat/m5-wit-local-l1
Open

wit: pin nexum:host to crate-local wit-deps#481
mfw78 wants to merge 1 commit into
feat/m5-dep-sync-cifrom
feat/m5-wit-local-l1

Conversation

@mfw78

@mfw78 mfw78 commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

What

Adds a crate-local wit-deps manifest (wit/deps.toml + wit/deps.lock) for nexum:host, kept empty since the package is a leaf. Extends the zero-leak gate to fail if the manifest ever declares a dependency.

Why

S2a of the split: bindgen! must resolve WIT crate-locally, not via a workspace-ancestor walk, before nexum-runtime can be carved out as L1. An empty, locked manifest proves and pins the leaf property ahead of the cut.

Testing

  • scripts/check-venue-agnostic.sh (new check 5: manifest/lock presence + emptiness)
  • cargo check --workspace --all-features

AI Assistance

Drafted with Claude Code; reviewed and tested by mfw78.

Closes #404

…t-deps manifest

The runtime bindgen and every L1 fixture module already resolve
wit/nexum-host inside the nexum group; check in an empty wit/deps.toml
plus its lock to pin the leaf, and teach the zero-leak gate to fail if
either ever declares a dependency.

@lgahdl lgahdl left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small and correct. Checked the new check-5 regex (^\s*[^#[:space:]]) against both files: deps.toml's comment-only line starts with # immediately so it's correctly excluded (pass), and the empty deps.lock blob correctly produces no match (pass, ripgrep exits 1 on empty input). A real future dependency entry (a [dependencies] header or a key = value line, with or without leading whitespace) would correctly match and fail, since neither starts with #. No polarity/stale-pattern bug like the ones in this script's earlier checks. Approving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants