Repository navigation
chore(developer-experience): commit the hand-rolled eval scenario sources #9936
Description
Refs: #6649
Parent
Depends on
- none: on the frontier now
Problem
Every porting child of #6649 needs the S1-S7, T1-T4, N1 and stays-quiet prompts, the two fixture
repositories, the checklists and the labeled judge samples, and none of them is in this repository.
The hand-rolled harness from PR #6668 survives on melo-desk-001 in the PR's worktree, under the
gitignored .work/devx/evals/ of branch feat/devx-skills-plugins: harness/ (13 files: scenarios.sh maps
each scenario id to fixture, arm state, prompts and tool allowlist; build-fixtures.py generates the fixtures;
score-deterministic.py scores the D and T items), fixtures/ (200 generated files: tarnquill .NET,
brackenfold Python, brackenfold-agentic), labels/ (484 files), lists/, held-out/, and judge/
(1174 files of judge output). The spec is .work/devx/eval-scenarios-draft.md in the same worktree.
Only that host has them, so this item runs there (through /fleet:reach from another machine).
Fix
Commit the scenario sources the ports read: the scenario definitions, the fixture generator (not the
200 generated files, if the generator reproduces them), the checklists and the labeled samples. Leave
results and judge run output out.
- 11 files in that set contain a home path or an email address: scrub them.
- Labeled and judge samples are model output: they follow
.claude/rules/eval-case-transcripts.md
(no raw transcript; an identifying-details review before commit).
Also
- Commit location:
plugins/developer-experience/evals/sources/.
Done when
- The sources are on main, with the identifying-details review recorded in the PR.
-
scripts/check-changelog-fragments.sh --check-required origin/mainexits 0.
Filed by AI from the owner-approved split of #6649 (2026-10-18), after the scenario sources were found on melo-desk-001 (2026-10-25).
Activity
github-actions commentedon Oct 25, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: commit the hand-rolled eval scenario sources (scenario definitions, fixture generator, checklists, labeled samples) from the PR #6668 harness into main. That means scrubbing the 11 files that hold a home path or email, leaving out results and judge output, and recording an identifying-details review in the PR.
The sources currently live only on one host, so the copy step needs a run there. That is a constraint on the run, not a gap in the request. No likely duplicates found in the open issues.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 25, 2026
The work-resolve-issue lane stopped partway through this issue and needs a person.
Why, in the run's own words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40208853249
To retry, remove
needs-humanand addagent-readyagain.