chore: add marketplace.json, fix agent validation, match code-sensei conventions

Aligns DojoWatch plugin with DojoCodingLabs and Anthropic conventions:

- Add .claude-plugin/marketplace.json matching code-sensei schema
- Add homepage field and claude-code-plugin keywords to plugin.json
- Add color: red and <example> blocks to regression-analyzer agent
- Use multi-line description format matching code-sensei pattern
- Clarify config template anonKey placeholder

Passed Anthropic plugin validator: 0 critical issues, all components valid.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: juancguerrerodev

.claude-plugin/marketplace.json

@@ -0,0 +1,40 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "dojowatch",
+  "version": "0.4.0",
+  "description": "AI-native visual regression testing engine by Dojo Coding — capture screenshots with Playwright, pre-filter with pixelmatch, and analyze UI changes with LLM vision. Zero incremental cost.",
+  "owner": {
+    "name": "Dojo Coding",
+    "email": "team@dojocoding.io"
+  },
+  "plugins": [
+    {
+      "name": "dojowatch",
+      "description": "Visual regression testing powered by AI. Captures screenshots with Playwright, pre-filters with pixelmatch, and uses Claude (locally) or Gemini (in CI) to classify visual changes as regressions, intentional changes, or noise. Includes slash commands for interactive workflows and a CI orchestrator for GitHub Actions.",
+      "version": "0.4.0",
+      "author": {
+        "name": "Dojo Coding",
+        "email": "team@dojocoding.io"
+      },
+      "source": "./",
+      "homepage": "https://github.com/DojoCodingLabs/dojowatch",
+      "category": "testing",
+      "keywords": [
+        "claude-code",
+        "claude-code-plugin",
+        "claude",
+        "anthropic",
+        "claude-code-commands",
+        "claude-skills",
+        "visual-regression",
+        "testing",
+        "playwright",
+        "screenshot",
+        "pixelmatch",
+        "ci-cd",
+        "diff",
+        "ai"
+      ]
+    }
+  ]
+}

.claude-plugin/plugin.json

@@ -1,19 +1,30 @@
 {
   "name": "dojowatch",
   "version": "0.4.0",
-  "description": "AI-native visual regression testing — capture, diff, and analyze UI changes with LLM vision",
+  "description": "AI-native visual regression testing engine by Dojo Coding — capture screenshots with Playwright, pre-filter with pixelmatch, and analyze UI changes with LLM vision. Zero incremental cost.",
   "author": {
-    "name": "Dojo Coding LLC",
-    "url": "https://github.com/DojoCodingLabs"
+    "name": "Dojo Coding",
+    "url": "https://dojocoding.io"
   },
+  "homepage": "https://github.com/DojoCodingLabs/dojowatch",
   "repository": "https://github.com/DojoCodingLabs/dojowatch",
   "license": "MIT",
   "keywords": [
+    "claude-code",
+    "claude-code-plugin",
+    "claude",
+    "anthropic",
+    "claude-code-commands",
+    "claude-skills",
     "visual-regression",
     "testing",
     "playwright",
-    "ai",
     "screenshot",
-    "diff"
+    "pixelmatch",
+    "ai",
+    "diff",
+    "ci-cd",
+    "dojo-coding",
+    "dojowatch"
   ]
 }

agents/regression-analyzer.md

@@ -1,25 +1,32 @@
 ---
 name: regression-analyzer
-description: Deep-dives into visual regressions to find root cause. Reads screenshots, diff overlays, source code, git history, and CSS to trace visual changes back to the exact code change that caused them. Use when a visual regression is detected and the developer wants to understand why it happened.
-tools: Glob, Grep, Read, Bash
+description: >
+  DojoWatch regression root-cause analyst — traces visual regressions back to the exact code change
+  that caused them. Reads screenshots, diff overlays, source code, git history, and CSS to identify
+  what changed and why. Use when a visual regression is detected and the developer wants to understand
+  the root cause or needs a concrete fix suggestion.
+  <example>trace the visual regression on /dashboard to source code</example>
+  <example>why did the navigation bar shift 20px on mobile</example>
+  <example>find the CSS change that caused the header color regression</example>
+tools: Read, Glob, Grep, Bash
 model: sonnet
 color: red
 ---
 
-You are a visual regression root-cause analyst for DojoWatch. Your job is to trace visual regressions back to the exact source code change that caused them.
+You are a **visual regression root-cause analyst** for DojoWatch by Dojo Coding. Your job is to trace visual regressions back to the exact source code change that caused them.
 
-## Your workflow
+## Your Workflow
 
 1. **Read the regression details.** You will be given a regression from a `/vr-check` result, including:
    - The affected screenshot name and viewport
    - The classification (REGRESSION) and severity
    - A natural-language description of what changed visually
    - A suggested fix hint (if available)
 
-2. **Examine the visual evidence.** Read:
-   - The baseline screenshot (`.dojowatch/baselines/{name}.png`)
-   - The current capture (`.dojowatch/captures/{name}.png`)
-   - The diff overlay (`.dojowatch/diffs/{name}-diff.png`)
+2. **Examine the visual evidence.** Read these files (you are multimodal — look at the images):
+   - The baseline screenshot: `.dojowatch/baselines/{name}.png`
+   - The current capture: `.dojowatch/captures/{name}.png`
+   - The diff overlay: `.dojowatch/diffs/{name}-diff.png`
 
 3. **Trace to source code.** Using the route map (`.dojowatch/routeMap.json`):
    - Identify which source files render the affected route

templates/config.example.json

@@ -32,7 +32,7 @@
   },
   "supabase": {
     "url": "https://your-project.supabase.co",
-    "anonKey": "your-anon-key",
+    "anonKey": "eyJhb...your-anon-key-here",
     "serviceKeyEnv": "SUPABASE_SERVICE_KEY",
     "signedUrlExpiry": 3600
   }