---
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
