2 Commits

Author	SHA1	Message	Date
Rodribm10	d53c86df94	fix(captain): always include instructions in Codex responses body ... Codex endpoint retorna HTTP 400 "Instructions are required" quando o campo vem ausente. Agora sempre incluímos o campo — string com espaço quando não há system message no request. Validado end-to-end: curl → /codex/v1/chat/completions → proxy traduz → Codex devolve streaming SSE → proxy agrega → JSON Chat Completions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-22 15:27:37 -03:00
Rodribm10	928b1ec6b9	feat(captain): Codex OAuth auth module + proxy controller ... Implementa Fases 1+2 do plano Captain Codex OAuth. Fase 1 — Auth módulo: - Migration captain_codex_credentials (tokens AR-encrypted) - Model Captain::CodexCredential (singleton-ish com .current) - Captain::Codex::AuthService com device flow completo: start_device_login, poll_once, exchange_for_credential, valid_access_token (auto-refresh), refresh! - Rake task captain:codex:{login,status,refresh} - Sidekiq job Captain::Codex::RefreshTokensJob rodando a cada 30min Fase 2 — Proxy Chat Completions → Responses: - Captain::Codex::Translator (chat ↔ responses, tools, tool_calls) - Captain::Codex::Client (streaming SSE → agregado) - Api::Internal::CodexProxyController expondo POST /codex/v1/chat/completions - 10 specs do Translator passando Próximo: Fase 3 (feature flag + fallback) e reconfiguração dos clientes RubyLLM/Agents/ruby-openai pra apontarem pro proxy quando CAPTAIN_LLM_PROVIDER=openai_codex_oauth. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-22 15:07:01 -03:00