Add git worktree name autocomplete suggestions

[warp-agent-staging]

Summary

Adds git-worktree-aware autocomplete so Warp suggests a repo's known linked working trees while typing git worktree lock, move, remove, and unlock.

• New worktrees generator in command-signatures/src/generators/git.rs, sourced from git --no-optional-locks worktree list --porcelain. It parses the porcelain records and emits one suggestion per linked working tree, mirroring the neighbouring git generators (--no-optional-locks, filter_messages/fatal: short-circuit, IconType, descriptions).
• Wires "generatorName": "worktrees" into the worktree arg of git worktree lock, move, remove, and unlock in command-signatures/json/git.json (the previously empty arg slots).

Design decision: insert the path, not the name

Each suggestion inserts the worktree's path, not a derived short name. Git identifies a working tree by its path — the worktree arg in git.json documents "Working trees can be identified by path, either relative or absolute", and git worktree lock/move/remove/unlock all operate on a path. git worktree list --porcelain reports absolute paths, so the inserted value always resolves. The checked-out branch (stripped of refs/heads/), or the bare/detached HEAD state, is surfaced as the suggestion description so the user can tell worktrees apart.

Design decision: exclude the main working tree, single generator

The main working tree is an invalid target for all four consuming subcommands — git worktree lock/unlock reject it outright and remove/move refuse it — so suggesting it would only ever produce a command that fails. git worktree list --porcelain always lists the main worktree first, so it is skipped. Because the four git worktree subcommands are the only consumers and all reject the main worktree, a single worktrees generator that excludes it is sufficient; a second "all worktrees" generator would be unreferenced dead code, so it was not added.

Verification

This is a spec/generator change validated by deterministic unit tests; there is no runnable UI in this repo, so no computer-use visual proof is applicable (the client that renders these suggestions lives elsewhere).

• Regression tests in git.rs over real git worktree list --porcelain output: test_post_process_worktrees (branch + detached linked worktrees, and an explicit assertion that the main worktree is absent), test_post_process_worktrees_bare (bare main excluded, linked kept), test_post_process_worktrees_only_main (main-only repo → no suggestions), test_post_process_worktrees_fatal_error (fatal short-circuit), test_worktrees_generator_command (asserts the porcelain command).
• The repo invariant test all_referenced_generators_exist confirms the new generatorName: "worktrees" references in git.json resolve to a defined generator, and all_command_specs_succeed_deserialization confirms the JSON still parses.
• ./script/presubmit passes end to end: npm run format:check, cargo fmt --check, cargo clippy … -D warnings, and cargo test (87 tests, 0 failures).

Context

• Implements Add autocomplete suggestions for git worktree names warp#11542 (Add autocomplete suggestions for git worktree names).
• Supersedes the earlier client-side attempt in Add worktree-aware autocomplete suggestions warp#14758 — this feature belongs in command-signatures (dynamic git values are supplied by named generators here), so that PR is being reverted to draft.

Rework changes

• Dropped the cd scope (requester objected): reverted command-signatures/json/cd.json, deleted command-signatures/src/generators/cd.rs, and removed its registration from generators/mod.rs. Attaching worktrees to the universal cd builtin would have shelled out to git worktree list on every cd completion anywhere, well beyond the issue's scope.
• Excluded the main working tree (fixes the oz-for-oss review finding): the generator no longer suggests the main worktree, which the four git worktree subcommands all reject. Added test_post_process_worktrees_only_main and an in-test assertion that the main worktree is absent.

Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1785969286177199

Conversation: https://staging.warp.dev/conversation/b894be3e-b473-41a9-b2c9-b972048c4fa9
Run: https://oz.staging.warp.dev/runs/019fd491-856f-7b3b-bc44-504490833074

This PR was generated with Oz.

[oz-for-oss]

@warp-agent-staging[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

Adds dynamic git worktree completions for git worktree subcommands and cd, backed by git worktree list --porcelain, with unit coverage for parsing and command construction.

Concerns

• The shared worktree generator emits the main worktree, but the newly wired git worktree lock, move, remove, and unlock arguments cannot operate on the main worktree path, so the first suggested completion is invalid for those commands.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz