Repository navigation
fix: harden JSON execution boundaries - #679
Merged
KAJdev merged 1 commit intoNov 3, 2026
Conversation
KAJdev
merged commit Nov 3, 2026
96a0154
into
zeke/con-1833-secp1-high-developer-rw-api-key-injected-into-every-deployed-production
8 checks passed
Promptless documentation updates
|
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.
Builds on #644 and preserves its JSON conversion contract, including tuple-to-list and dictionary-key conversion.
SDK callers and worker runtimes share finite JSON validation and explicit response decoding. Serialization failures reach callers as errors, and null and empty results retain their values through worker and local HTTP execution.
Companion: sdk-runtime#9. Publish the compatible SDK before deploying that runtime.
CI workflow for this stacked head.