Repository navigation
Explain graph changes and recorded run outcomes - #547
Merged
harrisonoconnorhover merged 2 commits intoOct 1, 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.
Authors currently have an infrastructure deployment preview but no read-only explanation of how an unsaved graph edit affects outputs. Run status also exposes default zero counters before measurements have been collected.
Add a static change-preview endpoint against the exact saved ETag, with downstream impact and before/after writer effects, plus a deterministic run-explanation endpoint that distinguishes unknown measurements, skipped work, and recorded results. Both reuse the existing authorization, graph limits, and lifecycle; generated contracts and documentation are included.
Validation: 87 focused comparison, explanation, HTTP, OIDC, and contract tests; canonical strict typing (513 files); Ruff lint/format; Control contract drift; diff checks. No live cloud mutation.
This is the first part of the guided workflow. Date-scoped output repair and the paired Druff interface remain active follow-on work. Published RC19 artifacts remain unchanged; the new source contract requires a newly generated client from a verified immutable artifact.