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): add shared eval fixtures for the .NET and Python repositories #9943
The ported cases of #6649 share two invented fixture repositories (tarnquill, .NET; brackenfold,
Python) in several states (bare, conventions-only, converged, legacy).
Fix
Add them under plugins/developer-experience/evals/ in the layout claude plugin eval reads, built
from the committed sources.
Also
Location: plugins/developer-experience/evals/fixtures/, each fixture built by a scaffold or seed script (/playbooks:skill-authoring runbook, "Checks eval files trip").
Done when
A case that names each fixture state loads under /evals:validate.
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: #9936
Understood: add two invented fixture repositories (tarnquill, .NET; brackenfold, Python) in four states each (bare, conventions-only, converged, legacy). They go under plugins/developer-experience/evals/fixtures/, each built by a scaffold or seed script. Done when a case naming each state loads under /evals:validate and the changelog-fragment check passes.
The scope and approach are clear. The issue depends on #9936 (committing the eval scenario sources), which is still open, so it waits on that. I found no likely duplicates.
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
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: Known
Flags: none
Blocked by: #9936
Understood: add two invented fixture repositories (
tarnquill, .NET;brackenfold, Python) in four states each (bare, conventions-only, converged, legacy). They go underplugins/developer-experience/evals/fixtures/, each built by a scaffold or seed script. Done when a case naming each state loads under/evals:validateand the changelog-fragment check passes.The scope and approach are clear. The issue depends on #9936 (committing the eval scenario sources), which is still open, so it waits on that. I found no likely duplicates.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 25, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.kyle-sexton commentedon Oct 25, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 25, 2026
Not admitted to the issue lane yet: blocker #9936 is not closed by a listed human or a merge.