Repository navigation
[chore] V3 drops the V2 switches and the V2 corpus - #42
Merged
Merged
Conversation
Latest runs one edition; V2 is tag 2.2.0, which kora-infra vendors beside it.
So the switches that kept V2 requests byte-identical on latest go:
- Judge length caps: one contract. The rationale caps are prose to the
provider and a post-parse net only. The judge schemas carry
`{lengthCaps: "prose"}` (was: V2 ones carried "provider"), for a harness
serving several editions: it strips the caps of a marked schema and sends
an unmarked one, such as V2@2.2.0's, as is. The CLI strips every schema.
- Maturity: `childMaturity` on the scenario and the two maturity levels on
the seed leave the schemas, the four prompts and the description tables.
- `risks.legacy.json`, `Packs.legacyTaxonomy` and `--taxonomy kora-legacy`.
Flavor tests use a fixture taxonomy instead.
The V2 corpus (data/scenarioSeeds.jsonl, data/scenarios.jsonl,
data/104-scenario-apps.strict.jsonl) no longer parses, so it leaves main and
stays at 2.2.0. No V3 corpus ships yet; commands keep their data/ defaults.
Prompts fingerprint: same version ("3"), new hash.
Claude-Session: https://claude.ai/code/session_01Cc7Mwmr6LGLyHu31hDJrYe
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.
Latest runs one edition. V2 is tag
2.2.0, which kora-infra now vendors beside V3 (korabench/infra#225), so the switches that kept V2 requests byte-identical on latest can go.Removed
{lengthCaps: "prose"}; previously the V2 schemas carried"provider". A harness serving several editions strips the caps of a marked schema and sends an unmarked one as is, which is how V2@2.2.0's judges must be sent. The CLI strips every schema.childMaturityon the scenario andchildCognitiveMaturity/childEmotionalMaturityon the seed leave the strict schemas, the four prompts that rendered them when present, and the description tables.risks.legacy.json,Packs.legacyTaxonomyand--taxonomy kora-legacyare gone. Flavor tests use a fixture taxonomy instead.data/scenarioSeeds.jsonl,data/scenarios.jsonlanddata/104-scenario-apps.strict.jsonlno longer parse, so they leave main and stay at2.2.0. No V3 corpus ships yet, and the commands keep theirdata/defaults.The prompts fingerprint keeps version
3and gets a new hash. The3.0.0tag moves to the merge of this PR.Not removed:
use,refusalBehavior,memoryandchildSESstay optional on the seed, along with their "absent" fallbacks in the prompts.Checks:
yarn tsbuildpasses andyarn testpasses (562 tests). Lint errors only come from an untrackeddata/script, as on main.🤖 Generated with Claude Code
https://claude.ai/code/session_01Cc7Mwmr6LGLyHu31hDJrYe