Skip to content

chore(developer-experience): commit the hand-rolled eval scenario sources #9936

Open

Description

@kyle-sexton

Refs: #6649

Parent

#6649

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/main exits 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

  1. added theissue type on Oct 25, 2026
  2. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    on Oct 25, 2026
  3. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  4. github-actions commented on Oct 25, 2026

    @github-actions
    Contributor

    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.

  5. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  6. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 25, 2026
  7. melodic-automation-lanes commented on Oct 25, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane stopped partway through this issue and needs a person.

    Why, in the run's own words:

    The files this issue asks to commit are not on this runner. The issue says the hand-rolled harness (harness/, fixtures/, labels/, lists/, held-out/, judge/) and the spec .work/devx/eval-scenarios-draft.md exist only on melo-desk-001, in the gitignored .work/devx/evals/ of PR #6668's worktree, and that the item has to run on that host through /fleet:reach. A search of this checkout found none of it: no scenarios.sh, build-fixtures.py, eval-scenarios-draft.md, or any tarnquill/brackenfold reference, and plugins/developer-experience/evals/ does not exist. Writing these files from scratch would be inventing the source content, and the scrub and identifying-details review need the real files. Run this item on melo-desk-001, or copy the sources somewhere this lane can reach, then re-run.

    What the run says it did not do:

    • Commit the scenario sources under plugins/developer-experience/evals/sources/: the source files are only on melo-desk-001 and this runner can't get to them
    • Scrub home paths and email addresses from the 11 affected files, and do the identifying-details review under .claude/rules/eval-case-transcripts.md: both need the real files
    • Changelog fragment for developer-experience: not written because nothing changed in the plugin
    • PR prep (review, verify, lint, class audits): skipped because there is no diff

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40208853249

    To retry, remove needs-human and add agent-ready again.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions