Skip to content

test(developer-experience): add shared eval fixtures for the .NET and Python repositories #9984

Closed as not planned

Description

@kyle-sexton

Refs: #6649

What to do

Build the shared .NET and Python fixture repositories under plugins/developer-experience/evals/fixtures/ from the committed sources, each named by a scaffold or seed script (/playbooks:skill-authoring runbook, "Checks eval files trip").

Done when

  • python3 plugins/evals/skills/validate/scripts/validate-cases.py plugins/developer-experience/evals exits 0.
  • Every file under the fixtures directory is named by a scaffold or seed script, and the orphaned-fixtures check passes in ci-status.
  • 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: Known
    Flags: none
    Blocked by: none

    Understood: build the shared .NET and Python fixture repositories under plugins/developer-experience/evals/fixtures/ from committed sources, with every fixture file named by a scaffold or seed script. The done-when items are validate-cases.py exiting 0, the orphaned-fixtures check passing, and ci-status green. The scope looks clear from the issue and no duplicates turned up among the open issues. Refs #6649.

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

    The issue says to build the .NET and Python fixture repositories 'from the committed sources', but those sources are not in the repository. plugins/developer-experience/evals/ does not exist, and nothing in the checkout names a developer-experience .NET or Python fixture. The issue that commits them, #9936 ('commit the hand-rolled eval scenario sources' under plugins/developer-experience/evals/sources/), is still open, has no linked PR, and says the sources live only on the host that ran the PR #6668 eval. Its duplicate, #9977, was closed as not planned. There is a second blocker: check-orphaned-fixtures.sh counts a fixture as consumed only when some evals/*/scaffold.sh (or a seed script a scaffold runs) names it, and no developer-experience case exists yet, because the porting children #9992, #9997, #10004, #10006, #10007, #9993 and #9998 are still to land. So the 'orphaned-fixtures passes' criterion cannot be met by fixtures alone. A person needs to decide: (a) block #9984 on #9936 (add 'Depends on: #9936') and requeue it once the sources are committed, or (b) say what the .NET and Python fixture repositories should contain without those sources (files, project layout, the states each case needs), and which case scaffolds should name them in this PR so the orphaned-fixtures check passes.

    What the run says it did not do:

    • No fixtures built: the committed sources the issue names do not exist yet (#9936 is open)
    • validate-cases.py and the orphaned-fixtures check were not run on a developer-experience evals tree, because none exists
    • ci-status green on the PR: left to the PR's CI; no PR results from this run

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

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

  9. 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: #9943.

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