This repository was archived by the owner on Jul 10, 2026. It is now read-only.
Cleanup: remove rotas mortas do api + corrige roadmap (orchestrator rejeitado, Swagger/usage já reais) - #116
Merged
Merged
Conversation
- P-01 vLLM vs Ollama: RESOLVIDO — runtime Ollama externo, ADR-001 atualizado; vLLM = profile GPU (depende de P-06). - P-07 Redis: RESOLVIDO (parcial) — redis no compose + throttle de login usa Redis; falta so confirmar recursos da VPS de producao. - P-09: remove referencia ao SHA antigo de main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AcsaeS7c9zJ4vkNtxqBcnc
…rator rejeitado) Investigacao revelou que varios apontamentos da auditoria estavam desatualizados e que ha codigo morto confundindo o crate `api`: - removidos 5 arquivos de rota ORFAOS no api (nao declarados em routes/mod.rs, zero refs): usage.rs, webhooks.rs, search.rs (duplicatas mortas das rotas reais que vivem no crate api-public) + chat.rs, feedback.rs (stubs que importavam `ai_orchestrator`, um nao-dependency — nem compilariam). Correcoes de entendimento (roadmap): - TKT-018/019 (linkar ai-orchestrator): REJEITADO. O crate e dead code para outra arquitetura (vLLM, RAG rag-searcher, tabela training_interactions, SSE proprio, sem basic-auth nem OLLAMA_MOCK). Linka-lo quebraria o chat atual + 11 testes. - TKT-020 (rag-searcher): REJEITADO (RAG do orchestrator); api::rag ja faz 4 estagios com rerank. - TKT-041 (Swagger): JA real (ApiDoc utoipa 40+ paths + SwaggerUi em /docs). - TKT-042 (usage tokens): o caminho VIVO (admin_service.get_usage_metrics, usado pelo dashboard via /api/admin/metrics) JA soma tokens de usage_events. O "0 // TODO" estava no api/routes/usage.rs MORTO (deletado). PR #113 editou esse arquivo morto — superado por esta remocao. Verificacao local: cargo build -p api -p api-public OK apos as remocoes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AcsaeS7c9zJ4vkNtxqBcnc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Limpeza de código morto + correção do roadmap
Investigação (para as "mudanças arquiteturais de IA") revelou que vários apontamentos da auditoria estavam desatualizados e que há código morto confundindo o crate
api.Removidos (5 arquivos órfãos no
api, não declarados emroutes/mod.rs, zero refs)usage.rs,webhooks.rs,search.rs— duplicatas mortas das rotas reais que vivem no crateapi-publicchat.rs,feedback.rs— stubs que importavamai_orchestrator(um não-dependency — nem compilariam)Correções de entendimento (roadmap)
ai-orchestrator): ❌ rejeitado. O crate é dead code para outra arquitetura (vLLM, RAGrag-searcher, tabelatraining_interactions, SSE próprio, sem basic-auth nemOLLAMA_MOCK). Linká-lo quebraria o chat atual + 11 testes. Oapijá tem caminho LLM/RAG próprio (Ollama-compat + rerank).rag-searcher): ❌ rejeitado (é o RAG do orchestrator);api::ragjá faz 4 estágios com rerank.ApiDocutoipa 40+ paths +SwaggerUiem/docs).admin_service.get_usage_metrics, usado pelo dashboard via/api/admin/metrics) já soma tokens deusage_events. O0 // TODOestava noapi/routes/usage.rsmorto (deletado) — o Sprint 5: /usage retorna tokens reais (TKT-042) #113 editou esse arquivo morto e é superado por esta remoção.Verificação local
cargo build -p api -p api-public✓ após as remoções.🤖 Generated with Claude Code
Generated by Claude Code