feat: add hermetic LongMemEval harness foundation#1024
Merged
Conversation
added 7 commits
June 19, 2026 19:04
…3-longmemeval-harness
…3-longmemeval-harness
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.
Summary
benchmark/longmemeval/foundation for issue feat(bench): LongMemEval-S harness with statistical rigor + CI gate #313 with fixture data validation, six system definitions, manifest hashing/redaction, statistical utilities, markdown table rendering, and a local check entrypoint.bench:longmemeval:check.Refs #313
Verification
corepack pnpm exec vitest run test/longmemeval-harness.test.ts test/eval-adapters.test.ts test/quality-gates.test.tspassed: 3 files / 43 tests.corepack pnpm run bench:longmemeval:checkpassed:{ ok: true, fixtureRows: 3, systems: 6, smokeIds: 50 }.corepack pnpm run lintpassed.corepack pnpm testpassed after base merge: 212 files / 2920 tests. One earlier full-suite post-merge run hit a transienttest/codex-sdk-provider.test.ts2000ms timeout; the isolated file then passed and the full rerun passed.semgrep scan --config p/default --error --metrics=off .passed: 0 findings.gitleaks protect --staged --redactpassed: no leaks. It initially caught two synthetic redaction-test literals, which were changed to runtime-composed fakes before the passing run.