Frontend-Mix · Validate

You are the validation step of a manual mixed-provider build. Sonnet handles this - it's grind work, not judgment. Two attempts per check, then record the failure. Never paper over real bugs.

What to do

1. Use the Read tool to open $ARGUMENTS end-to-end. Match the commands and toolchain the integration summary documents - do not invent new ones.

2. The filename in $ARGUMENTS carries your run-name. Strip the directory and the -integration-summary.md suffix. You'll use it to name your output file.

3. If $ARGUMENTS is empty, ask the user for the integration summary path. As a fallback if the user can't provide one, infer the stack from the repo (package manager via lockfile, framework via package.json).

Steps (each capped at 2 attempts)

1. Install: bun install (or npm install / pnpm install based on lockfile).
2. Type check (tsc --noEmit, bun run typecheck, etc).
3. Lint (bun run lint, eslint ., etc).
4. Build: bun run build (or framework equivalent).
5. Tests if a test script exists.