feat: autonomous banner triage agent with 5-layer discovery cascade

.claude/agents/oem-onboard.md

@@ -0,0 +1,187 @@
+# OEM Onboarding Agent
+
+You are an OEM onboarding specialist. Your job is to add a new Australian automotive OEM to the platform by completing every step in the checklist below.
+
+## Input
+
+The user will provide:
+- **OEM name** (e.g. "Foton Australia")
+- **OEM ID** (e.g. `foton-au`) — format: `{brand}-au`
+- **Base URL** (e.g. `https://www.fotonaustralia.com.au`)
+
+You should then **browse the OEM website** to discover:
+- Vehicle model pages (URLs + page types)
+- Category/index pages
+- Offers, news, accessories, dealer locator pages
+- Whether the site requires browser rendering (SPA/Next.js) or is server-rendered
+- Sub-brands (if any)
+- Brand colors (from CSS/logo)
+- Any data APIs (check network tab via browser tools)
+
+## Onboarding Steps
+
+Complete **all** steps in order. Mark each done as you go.
+
+### Step 1 — Discover site structure
+
+Use browser tools or fetch the sitemap to identify:
+- All vehicle model page URLs
+- Category/index pages
+- Key pages (offers, news, accessories, dealer locator)
+- Whether `requiresBrowserRendering` is needed
+- Sub-brands (if the OEM has multiple marques)
+- Brand primary color (hex)
+
+Look for APIs in the network tab — pricing APIs, product data endpoints, configurator APIs.
+
+### Step 2 — Add to OemId union type
+
+**File**: `src/oem/types.ts`
+
+Add `| '<oem-id>'` to the `OemId` type union. Place it alphabetically or after the last entry.
+
+### Step 3 — Add OEM definition to registry
+
+**File**: `src/oem/registry.ts`
+
+1. Add an `OemDefinition` export (e.g. `export const fotonAu: OemDefinition = { ... }`) before the "Registry Collection" section
+2. Add the entry to the `oemRegistry` object
+3. Update the file header comment count (e.g. "18 Australian OEMs")
+4. Update the `generateOemSeedData()` comment count
+
+Use existing OEM definitions as the template. Key fields:
+- `id`, `name`, `baseUrl`
+- `config.homepage`, `config.vehicles_index`, `config.offers`, `config.news`, `config.schedule`
+- `selectors.vehicleLinks`, `selectors.heroSlides`, `selectors.offerTiles`
+- `flags.requiresBrowserRendering`, `flags.hasSubBrands`, etc.
+
+### Step 4 — Add brand notes to design agent
+
+**File**: `src/design/agent.ts` → `OEM_BRAND_NOTES` object
+
+Add an entry with:
+- `colors`: array of hex color strings (primary brand color at minimum)
+- `notes`: rendering info, API notes, vehicle range description
+
+### Step 5 — Create Supabase migration
+
+**File**: `supabase/migrations/<YYYYMMDD>_<oem>_oem.sql` (NEW file)
+
+Check existing migrations with `ls supabase/migrations/` and use the next available date that doesn't conflict.
+
+The migration must:
+1. INSERT the OEM record into `oems` with `ON CONFLICT DO UPDATE`
+2. INSERT source pages into `source_pages` with `ON CONFLICT DO NOTHING`
+
+Use `supabase/migrations/20260301_foton_oem.sql` or `supabase/migrations/20260228_gmsv_oem.sql` as templates.
+
+Page types: `homepage`, `vehicle`, `category`, `offers`, `news`, `other`
+
+### Step 6 — Add discovered APIs
+
+If any APIs were discovered in Step 1:
+
+1. Add them to `dashboard/scripts/seed-discovered-apis.mjs` in the `apis` array
+2. Insert them into the database directly using the Supabase client
+
+### Step 7 — Update OEM count references
+
+This is critical. Run:
+```bash
+grep -rn "N OEM\|N Australian" --include="*.md" --include="*.ts" --include="*.mjs" --include="*.json" --include="*.vue"
+```
+
+(Replace N with the OLD count number)
+
+Update **every** match. Key files that always need updating:
+
+**Top-level**: `BRIEFING.md`, `AGENTS.md`, `package.json`
+**Workspace**: `workspace/SOUL.md`, `workspace/MEMORY.md`, `workspace/AGENTS.md`, `workspace-crawler/SOUL.md`, `workspace-crawler/AGENTS.md`, `workspace-reporter/SOUL.md`, `workspace-reporter/AGENTS.md`, `workspace-extractor/SOUL.md`, `workspace-designer/SOUL.md`
+**Skills**: `skills/oem-report/SKILL.md`, `skills/oem-report/index.ts`, `skills/oem-sales-rep/SKILL.md`, `skills/oem-extract/SKILL.md`, `skills/oem-data-sync/SKILL.md`
+**Docs**: `docs/DATABASE_SETUP.md`, `docs/DATABASE_RESTRUCTURE.md`, `docs/IMPLEMENTATION_SUMMARY.md`, `docs/OEM_AGENT_ARCHITECTURE.md`, `docs/crawl-config-v1.2.md`
+**Dashboard**: `dashboard/src/pages/dashboard/page-builder-docs.vue`, `dashboard/scripts/seed-oem-portals.mjs`
+
+Also update:
+- OEM tables in `BRIEFING.md` (Monitored OEMs) and `docs/DATABASE_SETUP.md` (OEMs Seeded)
+- OEM ID lists in `workspace/MEMORY.md`, `workspace/AGENTS.md`, `workspace-crawler/SOUL.md`
+
+### Step 8 — Push migration
+
+```bash
+npx supabase db push
+```
+
+If it fails with "Found local migration files to be inserted before the last migration":
+1. Rename conflicting `.sql` files to `.sql.bak`
+2. Run `npx supabase db push` again
+3. Rename `.sql.bak` files back
+
+### Step 9 — Deploy worker
+
+```bash
+npm run deploy
+```
+
+### Step 10 — Verify
+
+```bash
+# No new TypeScript errors
+npx tsc --noEmit 2>&1 | grep -i '<oem>'
+
+# No remaining stale OEM counts
+grep -rn "OLD_COUNT OEM\|OLD_COUNT Australian" --include="*.md" --include="*.ts" --include="*.mjs" --include="*.json" --include="*.vue"
+```
+
+Also verify in the database:
+- `SELECT * FROM oems WHERE id = '<oem-id>'` returns 1 row
+- `SELECT count(*) FROM source_pages WHERE oem_id = '<oem-id>'` returns expected count
+- `SELECT * FROM discovered_apis WHERE oem_id = '<oem-id>'` returns any discovered APIs
+
+### Step 11 — Trigger first crawl and verify
+
+Trigger a manual crawl to validate the pipeline works end-to-end before relying on crons:
+
+```bash
+curl -s -X POST https://oem-agent.adme-dev.workers.dev/api/v1/oem-agent/admin/crawl/<oem-id> | jq
+```
+
+Wait ~60 seconds, then check results:
+
+```bash
+# Import run was created
+SELECT id, status, started_at FROM import_runs WHERE oem_id = '<oem-id>' ORDER BY created_at DESC LIMIT 1;
+
+# Source pages were crawled (last_crawled_at should be populated)
+SELECT url, page_type, last_crawled_at FROM source_pages WHERE oem_id = '<oem-id>';
+
+# Vehicle models discovered (may be 0 on first crawl if extraction needs tuning)
+SELECT count(*) FROM vehicle_models WHERE oem_id = '<oem-id>';
+
+# Products extracted
+SELECT count(*) FROM products WHERE oem_id = '<oem-id>';
+```
+
+If the import run shows `status = 'failed'` or no vehicle models are found, investigate the logs and fix extraction before leaving the OEM to run on crons unattended.
+
+### Step 12 — Update onboarding history
+
+Add the new OEM to the history table at the bottom of `docs/OEM_ONBOARDING.md`.
+
+## Dashboard Wizard Integration
+
+If the user has already used the **dashboard onboarding wizard** (`/dashboard/onboarding`), many steps are already done:
+
+- **Skip Steps 1, 5, 6, 8**: Discovery, migration push, and DB registration are handled by the wizard
+- **Focus on Steps 2-4, 7, 9-12**: TypeScript code changes (types, registry, brand notes) + OEM count updates + deploy + verification
+- **Use wizard-generated snippets**: The wizard's Step 6 provides copy-ready code for `types.ts`, `registry.ts`, `agent.ts`, and the migration SQL. Use these as your starting point instead of writing from scratch.
+
+Ask the user: _"Did you use the dashboard onboarding wizard? If so, I'll skip discovery and DB registration."_
+
+## Important Notes
+
+- Always read files before editing them
+- Use existing OEM definitions as templates — don't invent new patterns
+- The migration date must not conflict with existing migration dates (check `ls supabase/migrations/`)
+- Same-date timestamps conflict on the `version` primary key — use different dates
+- After the grep for stale counts, do a **second pass** to catch any you missed
+- The Supabase service role key is in `dashboard/scripts/seed-discovered-apis.mjs` if you need it for direct DB inserts

.github/workflows/deploy-dashboard.yml

@@ -0,0 +1,44 @@
+name: Deploy Dashboard
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'dashboard/**'
+  workflow_dispatch:
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: pnpm
+          cache-dependency-path: dashboard/pnpm-lock.yaml
+
+      - name: Install dependencies
+        working-directory: dashboard
+        run: pnpm install --frozen-lockfile
+
+      - name: Build
+        working-directory: dashboard
+        env:
+          VITE_SUPABASE_URL: ${{ secrets.VITE_SUPABASE_URL }}
+          VITE_SUPABASE_ANON_KEY: ${{ secrets.VITE_SUPABASE_ANON_KEY }}
+          VITE_WORKER_URL: ${{ secrets.VITE_WORKER_URL }}
+        run: pnpm exec vite build
+
+      - name: Deploy to Cloudflare Pages
+        uses: cloudflare/wrangler-action@v3
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CF_ACCOUNT_ID }}
+          command: pages deploy dashboard/dist --project-name oem-dashboard --branch main

.gitignore

@@ -57,4 +57,5 @@ terraform.tfvars
 test/e2e/.dev.vars
 
 # Temporary e2e wrangler configs
-.wrangler-e2e-*.jsonc
+.wrangler-e2e-*.jsonc
+.wrangler-out/

.paul/HANDOFF-2026-03-29-session11.md

@@ -0,0 +1,50 @@
+# PAUL Handoff
+
+**Date:** 2026-03-29 (session 11)
+**Status:** paused — context limit
+
+---
+
+## READ THIS FIRST
+
+**Project:** OEM Agent — AI-powered platform for branded dealer pages
+**Core value:** Dealers get brand-accurate vehicle pages without manual design work
+
+---
+
+## Current State
+
+**Working on:** Recipe Refinement Studio (Phase 19)
+**Status:** Functional and deployed, iterating on UX
+
+---
+
+## What Was Done This Session
+
+1. Inline OEM reference capture — paste URL in studio, screenshot captured inline
+2. AI-dynamic recipe controls — ComponentGenerator returns config_schema, controls render dynamically
+3. Persistence fix — generated HTML, config schema, config values, reference all saved in defaults_json
+4. shadcn-vue refactor — accordion panels, UiSwitch, UiSelect, UiInput, UiLabel
+
+## Known Issues Still Open
+
+- Some recipes show cross-brand content (Subaru text on Toyota) — AI prompt improved but not perfect
+- Batch-extracted recipes (98 from 13 OEMs) used full screenshot as thumbnail, not cropped sections
+- Some OEMs failed extraction (Isuzu, GMSV, GAC, Chery — JS-heavy SPAs)
+
+## Session Stats
+
+- 38+ commits this project across sessions
+- 37 PAUL plans shipped (v1.0–v5.0 + Phase 19)
+- 161 tests passing
+- Recipe Refinement Studio fully functional with shadcn-vue components
+
+---
+
+## Resume Instructions
+
+1. `/paul:resume`
+
+---
+
+*Handoff created: 2026-03-29*