Conversation
0xcadams
force-pushed
the
0xcadams/type-runtime-network
branch
from
October 1, 2026 06:02
ee39620 to
5bfe6d4
Compare
0xcadams
changed the base branch from
main
to
0xcadams/type-client-certificate-phase
October 1, 2026 06:03
0xcadams
added this pull request to stack #43
October 1, 2026 06:03
0xcadams
force-pushed
the
0xcadams/type-runtime-network
branch
from
October 1, 2026 06:30
5bfe6d4 to
e0145fd
Compare
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.
What
Parse the runtime-load scenario and network impairment path into finite TypeScript choices before fault orchestration.
Why
Runtime fault scenarios already had a Zod enum, but setup used raw SCENARIO and NETWORK_PATH environment strings and passed a loose path into the fault runtime. That left typing behind at the entry point.
Changes