Skip to content

test(developer-experience): port eval cases S3 and S6 #10004

Closed as not planned
Closed as not planned

Description

@kyle-sexton

Refs: #6649

What to do

Port scenarios S3 and S6 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 S3 and S6.
  • 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 S3 and S6 into plugins/developer-experience/evals// (prompt.md, case.yaml, graders/), using deterministic graders where possible and calibrated llm graders, including the rm and compound-shell checks where needed. Done-when is clear and checkable. The "committed sources" for S3 and S6 are not linked in the issue, so the implementer will need to locate them (see #6649). No duplicates found among the 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
    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
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 25, 2026
  6. 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 source material for S3 and S6 is not in the repository. The issue says to port them 'from the committed sources', but those sources were never committed. Child issue #9936 ('commit the hand-rolled eval scenario sources', meant for plugins/developer-experience/evals/sources/) is still open with needs-human and no PR. Per #6649 and #9936, the only copy is in PR #6668's gitignored .work/devx/evals/ tree on the maintainer's host (melo-desk-001): harness/scenarios.sh, the fixture generator, checklists, labeled judge samples, and the spec .work/devx/eval-scenarios-draft.md. Writing S3 and S6 prompts, checklists, and calibrated llm graders from scratch would mean inventing the scenarios and labeled samples. The issue's timeline also shows it blocked by #9984 (shared .NET and Python eval fixtures), which may be the fixtures these cases need. Unblock by landing #9936, and #9984 if these cases need its fixtures, then re-add agent-ready.

    What the run says it did not do:

    • Port S3 and S6 into plugins/developer-experience/evals/<case>/ (prompt.md, case.yaml, graders/): blocked because the scenario sources are not committed (#9936)
    • validate-cases.py on plugins/developer-experience/evals: not run because there are no cases to validate
    • Local fresh-context review of the diff: skipped because the diff is empty (review-venue.txt absent)
    • ci-status green on the PR: left to the PR's CI; no PR is warranted with no changes

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

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

  7. 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: #9966.

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