Repository navigation
feat(contracts): defina fontes e explicação da simulação - #422
Merged
pedro-fs-garcia merged 2 commits intoNov 12, 2026
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.
Implementa os contratos das tarefas T-309 e T-316, permitindo identificar as bases utilizadas na simulação e representar a disponibilidade e o desfecho de sua explicação.
resultado-fontes, com exemplo baseado no manifesto atual, e adicionafontesopcional à consulta de auditoria.desfecho_explicacaoà conclusão da trilha e alinha as descrições deexplicacao_id,resultado_ide do nóexplicacao.explicacaona simulação retornada porGET /jobs/{id}, atualiza a descrição da flag de baixa rastreabilidade e define o evento SSEexplicacao.As alterações são aditivas: preservam os tipos, a obrigatoriedade dos campos existentes e os exemplos anteriores. O escopo se limita aos contratos e à documentação.
Validados os exemplos JSON, o OpenAPI, a compatibilidade dos contratos, a rejeição de hashes e competências inválidos e o
git diff --check. Arquivos revisados e conferidos localmente.