fix(cargo-wdk): workspace resolution in build and clean actions to match cargo

[svasista-ms]

TBD

Resolves #477

[Copilot]

Pull request overview

This PR updates cargo-wdk’s build and clean flows to better match Cargo’s workspace resolution behavior (Issue #477), especially when invoked from within a workspace subdirectory.

Changes:

• Pass the Metadata provider into CleanAction and use cargo metadata to detect workspaces before falling back to “emulated workspace” scanning.
• Add a NotAbsolute error variant for clean to mirror build’s handling of unexpected non-absolute paths.
• Add/adjust CleanAction unit tests for the new workspace-detection behavior.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
crates/cargo-wdk/src/cli.rs	Wires Metadata into CleanAction::new(...) so clean can query cargo metadata.
crates/cargo-wdk/src/actions/clean/mod.rs	Adds workspace detection via cargo metadata before emulated workspace scanning.
crates/cargo-wdk/src/actions/clean/error.rs	Adds NotAbsolute error variant for workspace root resolution failures.
crates/cargo-wdk/src/actions/build/mod.rs	Adds workspace-root inference attempt when Cargo.toml is not in the current directory.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 94.75806% with 13 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.02%. Comparing base (66223e9) to head (e5525cf).

Files with missing lines	Patch %	Lines
crates/cargo-wdk/src/actions/build/mod.rs	61.53%	4 Missing and 1 partial ⚠️
crates/cargo-wdk/src/actions/clean/mod.rs	93.67%	4 Missing and 1 partial ⚠️
crates/cargo-wdk/src/cli.rs	0.00%	0 Missing and 2 partials ⚠️
crates/cargo-wdk/src/actions/mod.rs	99.35%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #706      +/-   ##
==========================================
+ Coverage   80.47%   81.02%   +0.54%     
==========================================
  Files          26       26              
  Lines        5722     5951     +229     
  Branches     5722     5951     +229     
==========================================
+ Hits         4605     4822     +217     
- Misses        989      998       +9     
- Partials      128      131       +3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

crates/cargo-wdk/src/actions/mod.rs:149

• find_workspace_root always returns cargo_metadata.workspace_root, which for a workspace member subdirectory (e.g. member/src/) will typically be the workspace root, not the nearest package root. In BuildAction::run this causes cargo wdk build from inside a member subtree to build/package every workspace member (because it later runs from the workspace root), which diverges from cargo build’s “nearest Cargo.toml” behavior and can significantly increase build time.

    absolute(cargo_metadata.workspace_root.as_std_path()).ok()

crates/cargo-wdk/src/actions/mod.rs:147

• The is_emulated_workspace early-return makes find_workspace_root return None even when cargo metadata successfully identifies a real workspace, solely because the current directory contains non-member Cargo.toml children. That preserves “emulated workspace” behavior, but it also means cargo wdk build/clean can still diverge from cargo inside an actual workspace (cargo would ignore those excluded projects and operate on the workspace it found). If the PR goal is to “match cargo”, consider gating this behavior behind an explicit flag or removing it when a workspace is detected.

This issue also appears on line 149 of the same file.

    let is_emulated_workspace = dirs.iter().any(|entry| {
        entry.is_dir
            && fs.exists(&entry.path.join("Cargo.toml"))
            && absolute(&entry.path).is_ok_and(|child_dir| {
                !member_dirs
                    .iter()
                    .any(|member| member.starts_with(&child_dir))
            })
    });
    if is_emulated_workspace {
        return None;
    }

crates/cargo-wdk/src/actions/build/mod.rs:178

• New workspace-root resolution logic in BuildAction::run isn’t covered by the existing build action unit tests (there don’t appear to be tests for the “no Cargo.toml in cwd but inside a workspace” path, or for ensuring a member subdirectory builds only the selected package vs the whole workspace). This path is central to #477 and can regress behavior/perf without a test.

        // Standalone driver/driver workspace support
        if self.fs.exists(&self.working_dir.join("Cargo.toml")) {
            return self.run_from_workspace_root(&self.working_dir);
        }

        let dirs = self.fs.read_dir_entries(&self.working_dir)?;

        if let Some(workspace_root) = super::find_workspace_root(
            self.metadata,
            self.fs,
            &self.working_dir,
            &dirs,
            self.locked,
            self.features,
        ) {
            debug!(
                "Working directory {} lies inside the workspace rooted at {}; running build from \
                 workspace root",
                self.working_dir.display(),
                workspace_root.display()
            );
            return self.run_from_workspace_root(&workspace_root);
        }