Repository navigation
Retain optional JSON data with decisions and recent verdicts - #50
Merged
Merged
Conversation
A host-produced result must reach the sink unchanged after a failed attempt or runner restart, and remain available as recent context.
Keep a custom judge result with its decision and recent verdict so delivery retries and recovery do not need a host-side cache. Normalize incoming data, detach outgoing copies, and preserve absent fields for existing callers in both runtimes.
Keep the invariant suite pinned to the revision that retains decision data.
Carry the current main version and packaging checks into the decision data branch without changing the feature contract.
Keep the result contract alongside the custom judge API.
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.
Summary
A custom judge can now attach an optional JSON result to its decision in both runtimes.
The engine owns the prepared result through retries. Sinks and later judges receive detached copies. Omission keeps existing shapes; explicit null and empty values are retained. A skip keeps data in recent context; a wait keeps no final result. Reducer revision advances to 6; package versions are unchanged.
Evidence
Merge Danger
Door: Two-way before callers use data. Stores that contain it need compatible readers and writers; older versions do not retain the new field.
Blast Radius: Delivery and recent context. Data uses existing outbox/history storage, so callers should bound its size. Default notices and hosted judge prompts are unchanged. No package publication is included.