You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test(developer-experience): port eval cases T1 and T2 #10007
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.
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.
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
Activity
github-actions commentedon Oct 25, 2026
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.
melodic-automation-lanes commentedon Oct 25, 2026
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:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40209631918
To retry, answer the question here, remove
needs-humanand addagent-readyagain.kyle-sexton commentedon Oct 25, 2026
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.