Fix Dune native package management

[4ad]

Summary

• use Zed's supported * wildcard for the Dune probe executable
• authorize the --root <worktree> arguments added by Use correct project root for Dune package management detection #38

Problem

The Dune package-management probe is currently rejected by Zed's extension capability checks before dune is executed.

Zed only treats * as the command wildcard; ** is matched as a literal command name. Process arguments are also matched positionally and exactly unless a wildcard is present, but the manifest still authorizes only pkg enabled while the extension now runs pkg enabled --root <worktree>.

The resulting process error is converted to false by is_ok_and, so the extension silently falls through to opam exec -- ocamllsp.

Validation

• reproduced the fallback to opam with extension 0.4.0 in a Dune package-management project
• verified dune pkg enabled --root <worktree> exits successfully
• built the extension with cargo check and for wasm32-wasip2 in release mode
• installed the patched extension locally and confirmed Zed starts dune tools exec ocamllsp

Closes #54.

Follow-up to #37 and #38.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @4ad on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[4ad]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[4ad]

Hello? It's been over a week?

[MrSubidubi]

Thanks for this!

About the

Hello? It's been over a week?

Jokes aside - we continouosly try to improve in this area, but due to the sheer volume and us iterating on different approaches are currently unable to stay on top of it. That is not an excuse for it being disappointing in cases, but at the same time does not seem like a problem with any perfect and easy solution. Still, I do think we will find ways for it to get better, yet that will not be of help of people currently stuck in the queue sadly 😅