Skip to content

test(developer-experience): port eval cases T1 and T2 #9988

Open

Description

@kyle-sexton

Refs: #6649

Parent

#6649

Depends on

Problem

#6649 moves the developer-experience measurement onto claude plugin eval. Cases T1 and T2 exist only
as hand-rolled scenarios.

Fix

Port T1 and T2 from the committed scenario sources into plugins/developer-experience/evals/, one case
each, on the shared fixtures. Use deterministic graders where the scenario's D and T items allow; check
each llm grader against the committed labeled samples.

Also

  • Case layout: plugins/developer-experience/evals/<case>/ (prompt.md, case.yaml, graders/).
  • Include the rm and compound-shell checks where a case needs them.

Done when

  • Each case loads and passes /evals:validate (no paid run).
  • 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
    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
  2. added theissue type 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: Small
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: #9936, #9943

    Understood: port the hand-rolled developer-experience scenarios T1 and T2 into two claude plugin eval cases under plugins/developer-experience/evals/. They use the shared fixtures and deterministic graders where possible. Each llm grader is checked against the labeled samples. Done when each case passes /evals:validate and the changelog-fragment check exits 0.

    The scenario sources (#9936) and the shared fixtures (#9943) are both still open and are listed as dependencies, so this work waits on them. I found no likely duplicates.

    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. melodic-automation-lanes commented on Oct 25, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: blocker #9936 is not closed by a listed human or a merge; blocker #9943 is not closed by a listed human or a merge.

  7. removed
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    on Oct 25, 2026
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

    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