[Completions] Bump command-signatures to 15debaeb (kubectl --context/--cluster/--user forwarding)

[warp-agent-staging]

Description

Updates warp-command-signatures to 15debaeb, the squash commit on command-signatures:main for warpdotdev/command-signatures#331.

That PR fixes the last remaining symptom of #5186: a --context (or --cluster, or --user) written on the command line was never forwarded into the commands the kubectl completion generators run, so later completions enumerated from the shell's active context instead of the one on the line. With kubectl --context staging-cluster --namespace <TAB>, the generator ran kubectl … get namespace -o custom-columns=:.metadata.name with no --context. It now forwards --context, --cluster and --user, mirroring the existing --kubeconfig and --namespace handling. It also adds value completion for kubectl --user, and wires --context/--cluster/--user up for kubecolor and oc, which declared those options with no generator.

Merged PRs

• Fix nx run completions: use nx graph --file=stdout (Fix nx run completions: use nx graph --file=stdout command-signatures#335)
• Add completion specs for yay and paru (AUR helpers) (Add completion specs for yay and paru (AUR helpers) command-signatures#334)
• Fix yay/paru completion specs: -Pc field separators and -B/--build option placement (Fix yay/paru completion specs: -Pc field separators and -B/--build option placement command-signatures#336)
• Forward --context/--cluster/--user in kubectl generators (Forward --context/--cluster/--user in kubectl generators command-signatures#331)

Linked Issue

Addresses #5186 (labeled ready-to-implement). Also addresses #3929, which asks for this same context-forwarding behavior. Deliberately no closing keyword — #5186 covers several symptoms and should be closed manually with a note that the earlier parts landed in the June 2026 stable builds.

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

The kubectl behavior is covered by unit tests in warpdotdev/command-signatures#331, which assert the generated command string rather than merely that completion happens — including an assert_eq on the entire command for the reported case, and a tightened test_context_and_namespace_flags_before_subcommand (it previously passed a --context but only checked namespace forwarding, which is why the earlier #247 fix missed this). That repo's ./script/presubmit and CI were green on merge: 174 tests, 33 of them kubectl-specific.

For this dependency bump:

• cargo fmt --all --check passes.

• cargo clippy -p warp_completer --all-targets --tests -- -D warnings passes against the new rev.

• cargo metadata --locked accepts the lockfile, so Cargo.lock is in sync; the lockfile diff is limited to the two command-signatures source lines.

• cargo tree -p warp_completer -i warp-command-signatures confirms 15debaeb is what resolves.

• cargo test -p warp_completer reports 138 passed / 25 failed, identical to origin/master with this change stashed. Those 25 failures are pre-existing in this environment and unrelated to the bump. There are no kubectl-specific tests in warp_completer.

• I have manually tested my changes locally with ./script/run

Screenshots / Videos

No capture taken. Exercising this path in a running client requires a full client build against the bumped rev, which is expensive relative to the value: warpdotdev/command-signatures#247 already carries screenshots of the --context/--cluster value completion working, #331 carries end-to-end evidence from real kubectl runs against a synthetic offline kubeconfig, and the generated command is asserted precisely by unit tests.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-IMPROVEMENT: Added completions for yay and paru, and kubectl --user value completions.
CHANGELOG-BUG-FIX: Fixed kubectl completions ignoring a --context, --cluster or --user written on the command line, so namespaces, pods and other resources are now suggested from that cluster instead of the shell's active context. kubecolor and oc now complete those flags too, and nx run completions were fixed.

[warp-agent-staging]

This PR was generated with Warp.