fix(providers/command-code): send required stream payload

[ddarkr]

Summary

• Force Command Code upstream wrapper payloads to include skills: "" and params.stream: true.
• Align Command Code validation probe payload with the upstream-required shape and default it to deepseek/deepseek-v4-flash.
• Update focused Command Code tests for runtime payloads, validation payloads, and default validation model selection.

Verification

• node --import tsx/esm --test tests/unit/command-code-executor.test.ts
• node --import tsx/esm --test --test-name-pattern="validateCommandCodeProvider" tests/unit/provider-validation-specialty.test.ts
• node --import tsx/esm --test --test-name-pattern="Command Code" tests/unit/responses-handler.test.ts
• npm run typecheck:core

[gemini-code-assist]

Code Review

This pull request introduces a skills field (defaulting to an empty array) and hardcodes the stream parameter to true within the CommandCodeExecutor and its validation logic. Corresponding unit tests have been updated to align with these changes. Feedback suggests making the skills field configurable via the input body to increase flexibility. Additionally, it is recommended to refactor the validation logic to utilize the CommandCodeExecutor directly, which would eliminate code duplication and prevent potential desynchronization as the API evolves.

[gemini-code-assist]

Instead of hardcoding skills to an empty array, consider allowing it to be passed from the input body if present. This would make the executor more flexible for clients that might want to leverage specific Command Code skills while still defaulting to an empty array as required by the upstream wrapper.

Suggested change

	skills: [],
	skills: Array.isArray(input.skills) ? input.skills : [],

[gemini-code-assist]

The Command Code request wrapper structure and headers are now duplicated between this validator and the CommandCodeExecutor. This duplication (including the hardcoded version 0.24.1 and the new skills field) increases the risk of desync as the provider API evolves.

Consider refactoring validateCommandCodeProvider to use the CommandCodeExecutor directly to centralize the payload transformation and header logic. This pattern is already established in this file for other providers (e.g., validateClaudeOAuthInline at line 658).

[diegosouzapw]

✅ Merged into release/v3.8.0 — thank you @ddarkr!

All 5 commits cherry-picked and integrated. The Command Code executor now properly includes skills: "" and forces params.stream: true, and the validation probe defaults to deepseek/deepseek-v4-flash. Credit added to the CHANGELOG. 🎯