[feat] export the prompt builders from the package index - #35
Merged
Merged
Conversation
The system prompts (conversationToNextMessagePrompt) and the two user-simulator prompts were reachable only from inside the package. kora-infra's run export ships the full text of every prompt a run used, so it needs to call them. Additive: no behaviour change, no signature change.
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
Three added lines in
packages/benchmark/src/index.ts:Why
kora-infra's new run export produces a self-contained package for a run, which
includes a
prompts/folder with the full text of every prompt the run used:the four target system prompts (adult + one per age band) and the two
user-simulator prompts, alongside the two judge prompts.
It renders those by calling the builders against a placeholder scenario. The
two judge builders were already exported from the index; these three were not,
so they are unreachable through the package's export map and the consumer does
not compile.
Purely additive — no signature change, no behaviour change, nothing else in the
file moves. The alternative was reaching past the export map into
build/,which would break the next time the build layout changes.
Note
kora-infra's submodule pointer needs to move to the merged commit once this
lands; its export branch is blocked until then.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NExrgZ5EyiE2Ww9wP9RWMC