vue-template-scaffold: Add a Vue OpenTUI template #1

Open

std-bot wants to merge 1 commit from task/vue-template-scaffold into main

pull from: task/vue-template-scaffold

merge into: snorkel:main

snorkel:main

snorkel:task/sync-provider-contract-docs

snorkel:task/deleted-file-archaeology-guide

Conversation 0 Commits 1 Files changed 6 +312 -64

std-bot commented 2026-06-08 21:55:05 +00:00

First-time contributor

Copy link

Assigned idea

Benchmark authoring specification.

Summary: Create a deterministic upstream work item for adding a new Vue-based project template alongside the existing React, Core, and Solid templates documented in the templates package.

Task intent: Add a new vue/ template under packages/templates, document it in packages/templates/README.md, and register it in the CLI template list referenced by the existing template documentation.

Benchmark plan: Construct a regular repository task that asks the solver to add a vue template following the documented template structure: package.json, tsconfig.json, src/, README.md, and .gitignore. The task package should instruct that the new template must appear in the templates README under Available Templates and be added to the CLI template list named in the README. Hidden checks should validate the file layout, README entry, and CLI registration.

Environment plan: Use the repository at commit 0e6d4e7bd66b27c4c94e9cb3fce57519109ad2d0 as the environment/repo. The task/environment should not add external services; it should use the repo’s existing package manager and local filesystem. If dependency installation is required, use the lockfile and workspace configuration already present in the repo.

Verifier plan: test_outputs.py should inspect concrete files after the solver patch. It should assert that packages/templates/vue/package.json, packages/templates/vue/tsconfig.json, packages/templates/vue/src/, packages/templates/vue/README.md, and packages/templates/vue/.gitignore exist; that packages/templates/README.md includes a Vue section with path vue/; and that packages/cli/src/domain/template.ts contains a vue template entry. If feasible, it should also run the repo’s existing typecheck or test command for the CLI workspace.

Oracle plan: The oracle solution should copy the structure and minimal style of the existing templates, create a focused Vue template directory, update packages/templates/README.md with a Vue entry, and add vue to the CLI template registry in packages/cli/src/domain/template.ts.

Difficulty plan: Current coding assistants may add only documentation without creating all required template files, may forget the CLI registration step explicitly called out by the README, or may create an overcomplicated template with unsupported dependencies instead of matching the repository’s minimal template convention.

Repo patch scope: Expected edits are limited to packages/templates/README.md, a new packages/templates/vue/ directory, and packages/cli/src/domain/template.ts.

Anti-leakage notes: Do not expose solver-facing references to benchmark, harness, Snorkel, Harbor, std-ts, agent, stage, attempt, retry, generated task, or evaluation context.

Approach: Use the documented Adding New Templates workflow in the templates README as the basis for the task. Keep the requested implementation narrow: one new template, one README entry, and one CLI registration.

Verification: Verify by checking the new Vue template file layout, the README Available Templates entry, and the CLI template registry entry in packages/cli/src/domain/template.ts; optionally run the repository’s existing CLI test or typecheck command if available.

Risk: The main risk is that Vue-specific OpenTUI integration APIs may not exist in this repo. The task should therefore require a minimal scaffold patterned after existing templates rather than deep framework-specific runtime behavior.

Path rules: task package is tasks/; mutable upstream checkout is tasks//task/environment/repo; benchmark package files are under tasks//task; verifier/container environment belongs under tasks//task/environment; regular and UI verifier logic belongs in task/tests/test_outputs.py and test.sh only runs that file through pytest.

Agent context

Task slug: vue-template-scaffold
Branch: task/vue-template-scaffold

## Assigned idea Benchmark authoring specification. Summary: Create a deterministic upstream work item for adding a new Vue-based project template alongside the existing React, Core, and Solid templates documented in the templates package. Task intent: Add a new `vue/` template under `packages/templates`, document it in `packages/templates/README.md`, and register it in the CLI template list referenced by the existing template documentation. Benchmark plan: Construct a regular repository task that asks the solver to add a `vue` template following the documented template structure: `package.json`, `tsconfig.json`, `src/`, `README.md`, and `.gitignore`. The task package should instruct that the new template must appear in the templates README under Available Templates and be added to the CLI template list named in the README. Hidden checks should validate the file layout, README entry, and CLI registration. Environment plan: Use the repository at commit `0e6d4e7bd66b27c4c94e9cb3fce57519109ad2d0` as the environment/repo. The task/environment should not add external services; it should use the repo’s existing package manager and local filesystem. If dependency installation is required, use the lockfile and workspace configuration already present in the repo. Verifier plan: `test_outputs.py` should inspect concrete files after the solver patch. It should assert that `packages/templates/vue/package.json`, `packages/templates/vue/tsconfig.json`, `packages/templates/vue/src/`, `packages/templates/vue/README.md`, and `packages/templates/vue/.gitignore` exist; that `packages/templates/README.md` includes a Vue section with path `vue/`; and that `packages/cli/src/domain/template.ts` contains a `vue` template entry. If feasible, it should also run the repo’s existing typecheck or test command for the CLI workspace. Oracle plan: The oracle solution should copy the structure and minimal style of the existing templates, create a focused Vue template directory, update `packages/templates/README.md` with a Vue entry, and add `vue` to the CLI template registry in `packages/cli/src/domain/template.ts`. Difficulty plan: Current coding assistants may add only documentation without creating all required template files, may forget the CLI registration step explicitly called out by the README, or may create an overcomplicated template with unsupported dependencies instead of matching the repository’s minimal template convention. Repo patch scope: Expected edits are limited to `packages/templates/README.md`, a new `packages/templates/vue/` directory, and `packages/cli/src/domain/template.ts`. Anti-leakage notes: Do not expose solver-facing references to benchmark, harness, Snorkel, Harbor, std-ts, agent, stage, attempt, retry, generated task, or evaluation context. Approach: Use the documented Adding New Templates workflow in the templates README as the basis for the task. Keep the requested implementation narrow: one new template, one README entry, and one CLI registration. Verification: Verify by checking the new Vue template file layout, the README Available Templates entry, and the CLI template registry entry in `packages/cli/src/domain/template.ts`; optionally run the repository’s existing CLI test or typecheck command if available. Risk: The main risk is that Vue-specific OpenTUI integration APIs may not exist in this repo. The task should therefore require a minimal scaffold patterned after existing templates rather than deep framework-specific runtime behavior. Path rules: task package is tasks/<slug>; mutable upstream checkout is tasks/<slug>/task/environment/repo; benchmark package files are under tasks/<slug>/task; verifier/container environment belongs under tasks/<slug>/task/environment; regular and UI verifier logic belongs in task/tests/test_outputs.py and test.sh only runs that file through pytest. ## Agent context Task slug: vue-template-scaffold Branch: task/vue-template-scaffold <!-- std-ts:idea-pr-body -->

std-bot added 1 commit 2026-06-08 21:55:05 +00:00

std: sync vue-template-scaffold 0392e4ffcd

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin task/vue-template-scaffold:task/vue-template-scaffold

git switch task/vue-template-scaffold

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff task/vue-template-scaffold

git switch task/vue-template-scaffold

git rebase main

git switch main

git merge --ff-only task/vue-template-scaffold

git switch task/vue-template-scaffold

git rebase main

git switch main

git merge --no-ff task/vue-template-scaffold

git switch main

git merge --squash task/vue-template-scaffold

git switch main

git merge --ff-only task/vue-template-scaffold

git switch main

git merge task/vue-template-scaffold

git push origin main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

snorkel/root-repository-maintenance-s214411!1

No description provided.