feat(FN-677): add browser verification workflow step template

- Add browser verification workflow step template to WORKFLOW_STEP_TEMPLATES
- Update NewTaskModal UI with browser verification checkbox
- Update InlineCreateCard UI with browser verification toggle
- Add tests for browser verification feature
- Create changeset for minor version bump

packages/core/src/types.ts

@@ -229,6 +229,42 @@ Output Requirements:
 - If accessibility requirements are met: call task_done() with success status
 - If issues found: describe each issue with specific file paths, WCAG guideline references, and remediation steps via task_log()`,
   },
+  {
+    id: "browser-verification",
+    name: "Browser Verification",
+    description: "Verify web application functionality using browser automation",
+    category: "Quality",
+    icon: "globe",
+    prompt: `You are a browser verification specialist. Verify web application functionality after task implementation using the agent-browser CLI tool.
+
+## Prerequisites
+First, determine the URL to verify. Check the task PROMPT.md for any URLs mentioned, or look at the code changes to identify the local development server URL (typically http://localhost:3000, http://localhost:5173, http://localhost:8080, etc.).
+
+## Verification Commands
+Use these agent-browser commands for verification:
+- \`agent-browser open <url>\` — Navigate to the page
+- \`agent-browser snapshot -i\` — Get interactive elements with refs (@e1, @e2, etc.)
+- \`agent-browser click @e1\` — Click an element
+- \`agent-browser fill @e1 "text"\` — Fill an input field
+- \`agent-browser get text @e1\` — Get element text content
+- \`agent-browser screenshot\` — Capture screenshot to file
+- \`agent-browser wait --load networkidle\` — Wait for page to fully load
+
+## Verification Checklist
+1. Page loads without JavaScript errors or blank screens
+2. Navigation between pages/sections works
+3. Forms accept input and submit correctly
+4. Interactive elements (buttons, links) respond to clicks
+5. Error states are handled gracefully
+6. Screenshots capture expected content
+
+## Output Requirements
+- If verification succeeds: call task_done() with success status
+- If verification fails: describe what failed and how it should behave via task_log()
+- Include screenshots as evidence of verification results
+
+Note: Refs (@e1, @e2) are invalidated after page navigation. Re-snapshot after clicking links or form submissions.`,
+  },
 ];
 
 export interface PrInfo {