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
As of this issue being written, the Starter Suite does not include a TypeScript monorepo/tooling task. Vite issue #22237 reports a regression where Vite does not recognize Deno workspace roots when computing server.fs.allow, so nested package roots can exclude repository-level node_modules/.deno paths. No Agent Eval Lab task bundle, reference artifact, reference verification artifact, or Codex smoke trial exists for this candidate yet.
Focused upstream test command from the PR: pnpm exec vitest run packages/vite/src/node/server/__tests__/search-root.spec.ts
Why change
The Starter Suite needs more varied realistic tasks before broader capability reporting. This candidate adds TypeScript tooling and monorepo-root detection coverage, which is meaningfully different from the current Python, CLI, UI, setup, and formatter tasks.
What to build
Promote this candidate into a publishable Starter Suite task bundle. The task should ask the agent to make Vite recognize Deno workspace roots declared by a workspace field in deno.json or valid-JSON deno.jsonc, so searchForWorkspaceRoot returns the repository/workspace root instead of a nested package directory.
Keep the task narrow. The grader should exercise searchForWorkspaceRoot behavior directly or through the focused upstream search-root.spec.ts test path; do not require the full Vite test suite, browser tests, or broad end-to-end setup. The expected behavior is that nested and root Deno workspace fixtures resolve to the workspace root when a Deno workspace config is present, while existing package-manager workspace behavior remains intact.
If the task cannot be made fair without full monorepo installation, broad Vite test execution, browser/e2e tests, or unusually slow setup, stop and comment on this issue instead of committing a brittle or resource-heavy task.
Acceptance criteria
A task bundle exists under the Starter Suite with a stable task id, pinned Vite repository URL, and start commit dfc8aa5057dd8ec2b1223980d1e2eeb946ac3384.
The prompt describes the Deno workspace-root bug and expected conservative fix without naming the reference commit as the solution.
Deterministic graders fail on the start commit and pass for the intended fix. They must focus on searchForWorkspaceRoot behavior for deno.json and valid-JSON deno.jsonc workspace configs, preferably through the focused search-root.spec.ts path or an equivalently narrow direct test.
Graders avoid full Vite test-suite, browser/e2e, or broad monorepo validation.
Existing workspace-root behavior for non-Deno markers is not broken by the task/reference artifact.
A reviewed reference artifact is committed and recorded in task.yaml.
Reference verification passes and writes the standard reference report/result/diff artifacts.
The generated task-card.md is committed and task-card drift checks pass.
Run one Codex smoke trial with --trials 1 --jobs 1; if it is fair, comment with the trial/report/result paths. If it is invalid, suspicious, or resource-heavy, comment with the reason and do not scale the trial batch.
Keep the branch scoped to the task bundle, generated task card, reference artifacts, and task-specific tests if needed; do not add suite README indexes or local task-candidate backlog files.
Parent
Related to #10.
Current behavior / design
As of this issue being written, the Starter Suite does not include a TypeScript monorepo/tooling task. Vite issue #22237 reports a regression where Vite does not recognize Deno workspace roots when computing
server.fs.allow, so nested package roots can exclude repository-levelnode_modules/.denopaths. No Agent Eval Lab task bundle, reference artifact, reference verification artifact, or Codex smoke trial exists for this candidate yet.Candidate anchors:
regression in 8.0.4:consumer === "server"` bypass removed, breaks Deno + nitro vitejs/vite#22237dfc8aa5057dd8ec2b1223980d1e2eeb946ac33842ea005e5ec4bf2e5c0f4ed5030d84d713f747facpnpm exec vitest run packages/vite/src/node/server/__tests__/search-root.spec.tsWhy change
The Starter Suite needs more varied realistic tasks before broader capability reporting. This candidate adds TypeScript tooling and monorepo-root detection coverage, which is meaningfully different from the current Python, CLI, UI, setup, and formatter tasks.
What to build
Promote this candidate into a publishable Starter Suite task bundle. The task should ask the agent to make Vite recognize Deno workspace roots declared by a
workspacefield indeno.jsonor valid-JSONdeno.jsonc, sosearchForWorkspaceRootreturns the repository/workspace root instead of a nested package directory.Keep the task narrow. The grader should exercise
searchForWorkspaceRootbehavior directly or through the focused upstreamsearch-root.spec.tstest path; do not require the full Vite test suite, browser tests, or broad end-to-end setup. The expected behavior is that nested and root Deno workspace fixtures resolve to the workspace root when a Deno workspace config is present, while existing package-manager workspace behavior remains intact.If the task cannot be made fair without full monorepo installation, broad Vite test execution, browser/e2e tests, or unusually slow setup, stop and comment on this issue instead of committing a brittle or resource-heavy task.
Acceptance criteria
dfc8aa5057dd8ec2b1223980d1e2eeb946ac3384.searchForWorkspaceRootbehavior fordeno.jsonand valid-JSONdeno.jsoncworkspace configs, preferably through the focusedsearch-root.spec.tspath or an equivalently narrow direct test.task.yaml.task-card.mdis committed and task-card drift checks pass.--trials 1 --jobs 1; if it is fair, comment with the trial/report/result paths. If it is invalid, suspicious, or resource-heavy, comment with the reason and do not scale the trial batch.Blocked by
None - can start immediately.