dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 9 Wiki Activity

storkit: accept 375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects

Browse Source
This commit is contained in:
dave
2026-03-23 22:24:09 +00:00
parent 1cce46d3fa
commit 292f9cdfe2
1 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
.storkit/work/5_done/375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects.md
View File

@@ -1,43 +0,0 @@
---
name: "Default project.toml contains Rust-specific setup commands for non-Rust projects"
---
# Bug 375: Default project.toml contains Rust-specific setup commands for non-Rust projects
## Description
When scaffolding a new project where no tech stack is detected, the generated `project.toml` contains Rust-specific setup commands (`cargo check`) as example fallback components. This causes coder agents to try to satisfy Rust gates on non-Rust projects.
## Fix
1. In `detect_components_toml()` fallback (when no stack markers found): replace the Rust/pnpm example components with a single generic `app` component with empty `setup = []`
2. In the onboarding prompt Step 4: simplify to configure `[[component]]` entries based on what the user told the LLM in Step 2 (tech stack), rather than re-scanning the filesystem independently
## Acceptance Criteria
- [ ] Default project.toml does not contain language-specific setup commands when that language is not detected in the project
- [ ] If go.mod is present, setup commands use Go tooling
- [ ] If package.json is present, setup commands use npm/node tooling
- [ ] If no known stack is detected, setup commands are empty or just echo a placeholder
## How to Reproduce
1. Create a new Go + Next.js project directory with `go.mod` and `package.json`
2. Run `storkit .` to scaffold
3. Check `.storkit/project.toml` — the component setup commands reference cargo/Rust
4. Start a coder agent — it creates a `Cargo.toml` trying to satisfy the Rust setup commands
## Actual Result
The scaffolded `project.toml` has Rust-specific setup commands (`cargo check`) even for non-Rust projects. Agents try to satisfy these and create spurious files.
## Expected Result
The scaffolded `project.toml` should have generic or stack-appropriate setup commands. If no known stack is detected, setup commands should be empty or minimal (not Rust-specific).
## Acceptance Criteria
- [ ] Default project.toml does not contain language-specific setup commands when that language is not detected in the project
- [ ] If go.mod is present, setup commands use Go tooling
- [ ] If package.json is present, setup commands use npm/node tooling
- [ ] If no known stack is detected, setup commands are empty or just echo a placeholder