[codex] Add bounded diagnostic evidence metadata#14
Merged
Conversation
Add diagnostic budget limits, partial response metadata, ranked Event evidence, CLI and HTTP budget options, viewer Diagnostic Signals, and updated agent documentation so downstream users can reason about bounded in-memory graph results safely.
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
1 participant
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.
Summary: add maxNodes/maxEdges diagnostic budgets, partial response metadata, budget warnings, ranked Event evidence, CLI/HTTP/viewer support, and updated AI-agent docs/skill guidance. Validation: go test ./... with KUBECONFIG=/private/tmp/kubernetes-ontology-kind-kubeconfig; make visualize-check; kind live diagnostic against ontology-demo using only /private/tmp/kubernetes-ontology-kind-kubeconfig; headless Chrome viewer screenshot. Notes: kind demo namespace was deleted after verification.