Skip to content

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

Closed as not planned
Closed as not planned

Description

@kyle-sexton

Refs: #6649

What to do

Port scenarios T1 and T2 from the committed sources into plugins/developer-experience/evals/<case>/ (prompt.md, case.yaml, graders/), deterministic graders where possible and llm graders calibrated against labeled samples. Include the rm and compound-shell checks where a case needs them.

Done when

  • python3 plugins/evals/skills/validate/scripts/validate-cases.py plugins/developer-experience/evals exits 0.
  • git ls-files plugins/developer-experience/evals lists a case.yaml for both T1 and T2.
  • ci-status is green on the PR.

Split by the owner's HITL session (2026-10-24, owner decisions C12 and Q93-Q95). Intake triage sets its fields.

Activity

  1. added theissue type on Oct 25, 2026
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  3. 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: port eval scenarios T1 and T2 from the committed sources into plugins/developer-experience/evals/ as cases, each with prompt.md, case.yaml and graders. Graders should be deterministic where possible, with llm graders calibrated on labeled samples. The rm and compound-shell checks are included where a case needs them. The done-when items are checkable. The main thing to confirm is where the committed T1/T2 sources live. No duplicates found among the listed open issues.

    Automated triage, applied by the lanes App.

  4. 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
  5. added
    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.
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    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 did not start this issue: it needs a person to make it clearer first.

    Why, in the run's own words:

    This run can't port T1 and T2 because their scenario text isn't anywhere it can read. The issue says to port them 'from the committed sources', but nothing is committed. plugins/developer-experience/evals/ (and evals/sources/) does not exist on main. No file in the repository defines a developer-experience T1 or T2. The issue that was supposed to commit the sources, #9936, is still open with no PR; its lane comment says the sources exist only in the gitignored .work/devx/evals/ folder of PR #6668's worktree on melo-desk-001. Neither #6649 nor duplicate #9988 contains the scenario text either. The question for a person: will you land #9936 (commit the hand-rolled sources to plugins/developer-experience/evals/sources/) or paste the T1 and T2 prompts, expected behavior and labeled samples into this issue? Also consider recording #9936 as a blocker of this issue, as #9988 does, so the lane does not admit it again before the sources land.

    What the run says it did not do:

    • No eval cases written: the T1 and T2 sources are not in the repository (blocked on #9936)
    • validate-cases.py was not run: no plugins/developer-experience/evals directory exists to validate
    • ci-status on the PR is left to CI; no PR is opened for a pushback

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

    To retry, answer the question here, remove needs-human and add agent-ready again.

  8. kyle-sexton commented on Oct 25, 2026

    @kyle-sexton
    MemberAuthor

    Duplicate split of #6649 by a second Backlog HITL writer. To reopen: reopen this issue and say what the kept child misses.

    Kept child: #9988.

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