Skip to content

chore(evals): migrate to Luna and address plugin failures - #242

Draft
BjRo wants to merge 12 commits into
mainfrom
chore/luna-eval-sweep
Draft

BjRo wants to merge 12 commits into
mainfrom
chore/luna-eval-sweep

Conversation

@BjRo

@BjRo BjRo commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Why

Issue #228 tracks the GPT-6 Luna/medium eval sweep and follow-up on failing plugins. The first full pass found 86 failures across 361 direct-runner cases, so the results need a durable record and focused repairs. Refs #228.

What changed

Switch the default Codex eval route from Terra/medium to GPT-6 Luna/medium and record the full sweep with case-level assessments. Add semantic grading for saved artifacts, unify the discovery workflows, split skill creation from read-only auditing, allow explicitly delegated PR template selection, and clarify Langfuse attribution guidance and its negative eval boundary. Update the affected specifications, evals, and plugin versions.

Verification

The initial 361-case Luna/medium sweep completed; 275 passed and 86 failed, as recorded in docs/research/gpt-6-luna-evals-issue-228.md. Focused follow-ups in that report passed 5/5 for decision provenance, seven discovery boundaries, all 13 active skill-authoring cases in separate five-trial runs, and both Langfuse failures; the 12 create-pr cases passed a fresh single-trial regression. The latest Langfuse change also passed bun run check:docs, a Prettier check, and git diff --check. These focused samples do not establish a clean full-suite rerun.

Review notes

This is a draft because issue #228 still has unresolved plugin failures, including readiness-gate, and the original 86-failure overview remains historical. Review the runner's saved-artifact grader and the discovery and skill-authoring routing changes closely. Repository-wide pre-PR gates and cross-host behavior have not been established for the whole branch.

Checklist

  • I have read and followed CONTRIBUTING.md, including the contribution
    licensing terms.
  • I added or updated the applicable invariant before implementation, or
    this change does not affect a capability invariant.
  • I added or updated colocated evals, or this change does not affect skill
    behavior.
  • I confirmed that each changed plugin remains self-contained, or this
    change does not affect plugin content.
  • I ran bun run check:python, or this change does not affect registered
    Python packages or their repository quality infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant