story-kit: create 220_story_acceptance_gates_in_current_stage_should_use_script_test_instead_of_hardcoded_cargo_clippy

.story_kit/work/1_upcoming/220_story_acceptance_gates_in_current_stage_should_use_script_test_instead_of_hardcoded_cargo_clippy.md

@@ -0,0 +1,20 @@
+---
+name: "Acceptance gates in Current stage should use script/test instead of hardcoded cargo clippy"
+---
+
+# Story 220: Acceptance gates in Current stage should use script/test instead of hardcoded cargo clippy
+
+## User Story
+
+As a developer using Story Kit with a non-Rust project, I want the acceptance gates that run after a coder agent completes to use script/test and project.toml components instead of hardcoded cargo clippy, so that my Go/Python/Node project doesn't fail gates for missing Rust tooling.
+
+## Acceptance Criteria
+
+- [ ] run_acceptance_gates uses script/test as the primary quality gate instead of hardcoded cargo clippy
+- [ ] run_acceptance_gates does not invoke cargo clippy unless the project has a Cargo.toml
+- [ ] Default coder prompt in config.rs no longer mentions cargo clippy (uses generic 'quality gates' language)
+- [ ] MCP merge_agent_work tool description no longer hardcodes cargo clippy/pnpm references
+
+## Out of Scope
+
+- TBD