Repository navigation
fix: show one Jev routing header per completion (0.15.33) - #63
Merged
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uma completion com thinking e texto mostrava duas vezes
jev-router → modelo, inclusive deixando um cabeçalho acima de raciocínio oculto. Agora o primeiro bloco visível de texto/tool possui o único cabeçalho daquela completion; novos pedidos continuam exibindo suas próprias escolhas.A identidade usa request + completion, antes de recortar o viewport, e preserva os metadados do histórico. Inclui regressões para múltiplos blocos, tools agrupadas, retomada, transcript, IDs de provider repetidos em requisições independentes e pacote instalado em PTY normal/fullscreen. Prepara a versão 0.15.33 para distribuição assinada.
Validação local: 342/342 arquivos de testes isolados com Bun 1.3.13 no ambiente CI; build e self-test de protocolo; regressões JSON/SSE com reasoning + selected_model; testes do pacote instalado em terminais reais. Nomes dos dois secrets Minisign confirmados no environment
release, e job de assinatura habilitado.