Add scenario runner seam for runtime summaries#44
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.



Purpose
Add a reproducible scenario-runner seam for local runtime experiment evidence generation.
Type
Changes
This PR adds a no-dependency Node scenario runner that accepts one deployment scenario and one k6 workload, coordinates Kubernetes/k6 adapters, and writes sanitized runtime-summary artifacts for collector ingestion.
The runner preserves backend business behavior. It does not add runtime-aware scoring, SLO classification, Cosmos writes, cluster creation, image loading, secrets handling, or production monitoring.
Files changed
load-tests/runtime-scenarios/*.mjsdocs/runtime-scenario-summaries.mddocs/README.mddocs/runtime-fitness-extension.md.beads/issues.jsonllined-51sscenario-runner seam work as in progress.Expected result
This is experiment tooling only. Structural fitness may move slightly because new test/tooling code and docs are added, but backend business logic is unchanged.
Verification
Additional checks run:
node --test load-tests/runtime-scenarios/*.test.mjsnode --check load-tests/runtime-scenarios/*.mjsgit diff --checkkubectl kustomize k8s/kind/scenarios/fixed-smallkubectl kustomize k8s/kind/scenarios/fixed-mediumkubectl kustomize k8s/kind/scenarios/replicas-2kubectl kustomize k8s/kind/scenarios/hpa-cpu