From 0c85ecc85ca1092c6d0bd5cb63f566fc25050412 Mon Sep 17 00:00:00 2001 From: dave Date: Mon, 23 Mar 2026 16:43:27 +0000 Subject: [PATCH] storkit: accept 369_bug_cli_treats_help_and_version_as_project_paths --- ...ic_setup_commands_for_non_rust_projects.md | 31 ------------------- ...reats_help_and_version_as_project_paths.md | 0 2 files changed, 31 deletions(-) delete mode 100644 .storkit/work/1_backlog/375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects.md rename .storkit/work/{5_done => 6_archived}/369_bug_cli_treats_help_and_version_as_project_paths.md (100%) diff --git a/.storkit/work/1_backlog/375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects.md b/.storkit/work/1_backlog/375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects.md deleted file mode 100644 index 3b6ee60..0000000 --- a/.storkit/work/1_backlog/375_bug_default_project_toml_contains_rust_specific_setup_commands_for_non_rust_projects.md +++ /dev/null @@ -1,31 +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, the generated `project.toml` contains Rust-specific setup commands (`cargo check`, `cargo clippy`) regardless of the actual tech stack. This causes coder agents to try to satisfy Rust gates on non-Rust projects — e.g. creating a `Cargo.toml` in a Go project because the project.toml told them to run `cargo check`. - -## 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 diff --git a/.storkit/work/5_done/369_bug_cli_treats_help_and_version_as_project_paths.md b/.storkit/work/6_archived/369_bug_cli_treats_help_and_version_as_project_paths.md similarity index 100% rename from .storkit/work/5_done/369_bug_cli_treats_help_and_version_as_project_paths.md rename to .storkit/work/6_archived/369_bug_cli_treats_help_and_version_as_project_paths.md