Implement pnpm workspace filter

[lucieleblanc]

Summary

Addresses APP-3496 — adds workspace package name completions for pnpm's --filter/-F option, inspired by the pnpm-shell-completion plugin.

Changes

Rust generator (command-signatures/src/generators/npm.rs):

• Added PnpmWorkspacePackage struct for deserializing pnpm list -r --depth -1 --json output
• Added workspace_packages_generator() that dynamically suggests workspace package names with version info
• Registered the generator in pnpm_generators()
• Added unit tests for normal output, empty output, and invalid JSON

Completion spec (command-signatures/json/pnpm.json):

• Added -F as a short alias for --filter across all 21 subcommand occurrences
• Wired workspace_packages_generator into all --filter/-F args alongside the existing filepaths template

Generator Screenshots

pnpm run <Tab> — scripts completions (shows scripts from package.json with descriptions):

pnpm remove <Tab> — dependency completions (shows installed dependencies):

pnpm --filter <Tab> — filter completions (shows filepaths + workspace packages when pnpm is available):

Note: The workspace_packages_generator requires pnpm to be on PATH. In the sandbox test environment, the debug Warp build had restricted PATH that prevented the generator command from executing. The existing get_scripts_generator and dependencies_generator (which read local files via cat) work correctly as shown above.

Testing

• All presubmit checks pass (prettier format, cargo fmt, clippy, 45 tests including 3 new tests)
• Verified scripts and dependencies generators end-to-end in local Warp build
• Unit tests cover workspace packages generator parsing for valid JSON, empty output, and invalid JSON

---

Conversation: https://staging.warp.dev/conversation/4dc6c6b7-a480-4ec5-bfc3-a475248de4a6
Run: https://oz.staging.warp.dev/runs/019d689a-b684-7658-9363-ff95ac53972d
This PR was generated with Oz.

[linear]

APP-3496 [pnpm] Support pnpm shell plugin completions

pnpm project-specific completions from shell plugins (e.g. pnpm-shell-completion) are currently not picked up by Warp's completer.

See GitHub #3435

[lucieleblanc]

temp

[lucieleblanc]

Generator Screenshot Verification

All generators were verified end-to-end in a local Warp build against a test pnpm workspace with scoped packages (@myorg/pkg-a, @myorg/pkg-b, test-monorepo).

Fixes applied

1. Rebased onto main — resolved merge conflict with the new npm_registry_search_generator tests.

2. Switched workspace_packages_generator to filesystem-based approach — The original pnpm list -r --depth -1 --json command failed silently in the completion engine because pnpm is a corepack shim that can prompt for download confirmation in non-interactive generator subprocesses. The new approach reads pnpm-workspace.yaml and package.json files directly from the filesystem using standard POSIX tools (find, sed).

3. Removed template: "filepaths" from --filter args — Having both template and generatorName on the same args object prevented the generator from running in the Warp completion engine.

4. Added --filter/-F as a top-level option — pnpm's --filter is a global option (used before subcommand: pnpm --filter pkg run build), but was only defined on individual subcommands. The completion engine couldn't resolve which subcommand's --filter to use when no subcommand was typed yet.

Test results

• pnpm --filter <Tab> ✅ — Shows workspace package names: @myorg/pkg-a (v1.0.0), @myorg/pkg-b (v2.0.0), test-monorepo (workspace package)
• pnpm --filter @<Tab> ✅ — Filters to scoped packages only: @myorg/pkg-a, @myorg/pkg-b. Auto-completes common prefix @myorg/pkg-.
• pnpm -F <Tab> ✅ — Short alias works identically to --filter.
• pnpm run <Tab> ✅ — Shows scripts: build, dev, lint, test with descriptions.
• pnpm remove <Tab> ✅ — Shows dependencies: express, lodash, typescript with dependency types.

All 54 unit tests pass, including 3 updated tests for the workspace packages generator that verify @-scoped package names are correctly handled.