fix(codex): default custom provider wire_api to 'responses'

[CZH-THU]

Summary

Default codexCustomWireAPI from "chat" to "responses" to align with modern codex behavior and support custom providers that only implement the Responses API.

Problem

When using a custom provider (e.g., tokenswitch, idealab) with a non-default base_url, skill-up generates codex command-line flags like:

\-c model\_providers.skill-up-openai.wire\_api="chat"

This overrides the provider's configured wire_api setting, forcing codex to use /chat/completions. If the upstream endpoint only supports /responses, the request fails or hangs.

Solution

Change codexCustomWireAPI from "chat" to "responses":

// Before
codexCustomWireAPI  = "chat"

// After
codexCustomWireAPI  = "responses"

This aligns with modern codex defaults (which already use "responses") and ensures compatibility with custom providers that implement the Responses API.

Impact

Scenario	Before	After
Default OpenAI (no base_url)	No change	No change
Custom provider with Responses API	❌ Fails	✅ Works
Custom provider with Chat API only	✅ Works	❌ Fails

Note: Modern codex defaults to "responses" anyway, so custom providers that only support Chat API are already incompatible with current codex versions.

Testing

Verified with tokenswitch provider (Responses API only):

✅ [1/1] pause-campaign-confirmation: PASS (100.0%)
📋 Results: 1 passed, 0 failed, 0 errors

Related

• Fixes issue where skill-up eval runs hang or fail with custom providers
• Aligns with codex's default behavior since v0.80+

[CLAassistant]

All committers have signed the CLA.