verification-workflowlisted

# Verification Workflow Automated verification to determine if a feature is complete and ready to ship. ## Workflow Overview ``` 1. Detect project type and locate dev server 2. Run static analysis (TypeScript, linting) 3. Check for requirements (requirements.md or requirements/) 4. If requirements exist → Generate unit tests from requirements 5. If no requirements → Run E2E to confirm behavior, then generate unit tests 6. Run all tests 7. Report: "Ready to ship" or "Issues found" ``` ## Step 1: Environment Detection Detect project type by checking for: - `package.json` with `next` → Next.js project - `package.json` with `expo` → Expo/React Native project - `pom.xml` or `build.gradle` → Spring Boot project Find running dev server by checking ports in order: 3000, 8080, 8081. ```bash for port in 3000 8080 8081; do if curl -s -o /dev/null -w "%{http_code}" "http://localhost:$port" | grep -q "200\|302\|304"; then echo "Dev server found on port $port" break fi done ``` ## Step 2: Static Analysis Run before any other verification: ```bash # TypeScript projects npx tsc --noEmit # Linting npm run lint 2>/dev/null || npx eslint . --ext .ts,.tsx,.js,.jsx ``` Fix any type errors or lint issues before proceeding. ## Step 3: Requirements Check Look for requirements in this order: 1. `requirements.md` in project root 2. `requirements/` folder in project root 3. Context provided in conversation If requirements found → Step 4a. Otherwise → Step 4b. ## Step 4a: Uni