From 4487862479a9aa822d5cc31cb4f31a8cae9b3185 Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 12:25:07 +0000 Subject: [PATCH] story-kit: create 65_story_standardised_script_test_entry_point_for_all_projects --- ...cript_test_entry_point_for_all_projects.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md diff --git a/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md b/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md new file mode 100644 index 0000000..c9f0a21 --- /dev/null +++ b/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md @@ -0,0 +1,22 @@ +--- +name: Standardised script/test Entry Point for All Projects +test_plan: pending +--- + +# Story 65: Standardised script/test Entry Point for All Projects + +## User Story + +As a Story Kit user, I want every project initialised by Story Kit to have a script/ directory with a test script, so that agents and the system always have a known location to run all tests (including e2e) without needing to know project-specific commands. + +## Acceptance Criteria + +- [ ] Story Kit project scaffolding creates a script/ directory in the project root +- [ ] A script/test executable is created during init with a sensible default (e.g. exit 0 or echo no tests configured) +- [ ] The Rust server can invoke script/test as the canonical way to run all tests for any project +- [ ] Agents use script/test instead of guessing test commands +- [ ] For this project (story-kit-app), script/test runs cargo test, pnpm test, and pnpm test:e2e + +## Out of Scope + +- TBD