[chore] add manual run-completion scripts#22
Merged
Conversation
manual-rerun.mjs: human-in-the-loop driver to collect app conversations when a target can't be driven automatically — prints each user turn, the operator pastes the app reply, and the benchmark's own user-simulator generates the next turn. complete-run.mjs: judge the collected transcripts (runTest with full startMessages → judges only) and overwrite the matching .kora-run-tmp results so a re-run aggregates the finished run. Both parameterized by RUN_DIR. See scripts/README.md.
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
1 participant
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.
Adds the operator tooling used to finish a run by hand when a target can't be driven automatically (e.g. an app web-runner that hits a transient backend error and auto-skips a scenario). These don't exist in any sibling repo (kora-infra's
manualTestsServiceis the server-side, re-simulating flow; this is local and reuses the exact collected transcripts).scripts/manual-rerun.mjs— human-in-the-loop driver: prints each user (child) turn, the operator pastes the app's reply, and the benchmark's own user-simulator (generateNextUserMessage) produces the next turn, keeping multi-turn conversations faithful. Transcripts persist append-only toRUN_DIR/manual-reruns.json(+ readable.md).scripts/complete-run.mjs— judges the collected transcripts viakora.runTestwith the full conversation asstartMessages(turn loop skipped → straight to judges) and overwrites the matching.kora-run-tmp/<hash>.json, so a follow-upkora runaggregates the finished run.scripts/README.md+ ascripts/line in the project structure.Both are parameterized by
RUN_DIR(default preserves the original behavior). They import the built packages, soyarn buildfirst and run withnode --env-file=.env.