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

story-kit: accept 216_story_merge_quality_gates_should_use_project_toml_components_and_script_test_instead_of_hardcoded_frontend_pnpm

Browse Source
This commit is contained in:
Dave
2026-02-26 21:32:04 +00:00
parent a66ac697c0
commit 799562a4e2
1 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
.story_kit/work/5_done/216_story_merge_quality_gates_should_use_project_toml_components_and_script_test_instead_of_hardcoded_frontend_pnpm.md
View File

@@ -1,20 +0,0 @@
---
name: "Merge quality gates should use project.toml components and script/test instead of hardcoded frontend/pnpm"
---
# Story 216: Merge quality gates should use project.toml components and script/test instead of hardcoded frontend/pnpm
## User Story
As a project maintainer, I want the merge pipeline quality gates to use the dynamic component setup from project.toml and script/test, so that the pipeline works with any tech stack rather than assuming a frontend/ directory and pnpm.
## Acceptance Criteria
- [ ] run_squash_merge uses project.toml component setup commands (same as worktree creation) to prepare the merge workspace instead of hardcoded pnpm install in frontend/
- [ ] run_merge_quality_gates delegates to script/test for the full test suite instead of separately invoking cargo clippy, cargo test, pnpm build, and pnpm test
- [ ] No hardcoded references to pnpm or frontend/ in the merge pipeline code path (run_squash_merge, run_merge_quality_gates)
- [ ] Existing script/test entrypoint continues to work as the single source of truth for quality gates
## Out of Scope
- TBD