Supergentic Docs Transfer Plan

Install the make-docs skill from ~/dev/stitchwand/docs/make-docs.skill

Use the make-docs skill in MAKE mode on this repo.

## Context
This is **supergentic** — an AI-powered marketing operations platform for Salesforce Marketing Cloud. It's a React 19 SPA (Vite + Tailwind + React Router) with no backend. The app has 15+ pages, 30+ components, 5 AI agents, a Console with command palette, and a multi-step wizard system. Heavy Salesforce integration planned but currently simulated.

## Brand / Design System
- **Accent color**: `#FE9339` (orange), dark variant `#E57C00`
- **Background**: `#0A0A0A`
- **Font**: Inter (sans), SF Mono / Fira Code (mono)
- **Auth**: sessionStorage with `sg-auth` key, URL param `?auth=next`, password "next"
- **Company**: Dilshaus Ventures / The Fieldhaus
- **Copyright**: 2026
- **Secondary colors**: green `#45C65A`, purple `#9050E9`, blue `#1B96FF`, cyan `#00BDD6`

## Existing Docs
There is already a `/docs` directory with 10+ self-contained HTML files:
- `index.html` (portal with auth gate)
- `pitch.html`, `demo.html`, `demo-script.html`
- `launch-plan.html`, `technical-architecture.html`
- `ai-strategy.html`, `go-to-market.html`
- `design-system.html`, `research-sfmc-flows.html`
- `paid-ads.html`

Plus markdown planning docs:
- `solidify.md` — feature audit and solidify sprint results
- `console-feature-spec.md` — Console feature specification
- `salesforce-cloud-integration.md` — Salesforce multi-cloud integration roadmap

## What I Want
1. **Analyze the full codebase** — read every source file, component, page, data model, config. Understand what's real vs. simulated.
2. **Analyze existing docs** — read each HTML doc, understand its structure, assess if it's current or stale.
3. **Identify gaps** — what docs are missing? I expect at minimum: Onboarding guide, Strategy consolidation (merge ai-strategy + go-to-market + paid-ads into tabbed strategy.html), Stealth marketing + organic social proof tab, Updated architecture doc.
4. **Present a doc plan** — show me what you'll generate and what you'll update before doing it.

Do NOT generate anything yet. Just analyze and present the plan.

Proceed with the doc plan. Generate and rebuild all docs using the orange `#FE9339` design system.

Every doc must:
- Use the standardized two-level sticky nav with glass-morphism (global nav + section nav)
- Include the global nav with brand badge (use orange instead of purple for supergentic)
- Standard nav links: Pitch, Demo, Architecture, Strategy, Vision, Launch Plan, Open App
- Use `sg-auth` password gate (password: "next", sessionStorage key: `sg-auth`, URL bypass: `?auth=next`)
- Use `#FE9339` accent throughout
- Be accurate to the actual codebase
- Include screenshots if the app is running (check localhost:5173)

For strategy.html — consolidate into tabs: AI Strategy, GTM, Growth, Paid Ads, Stealth Marketing. Include the stealth marketing warning modal gated by sessionStorage.

For launch-plan.html — use the task checkbox system with sidebar, expandable sections, auto-collapse, export/import, and sidebar detail panel with Claude Code prompts.

Run validation on all docs in /docs:

1. HTML validity — well-formed tags
2. Link integrity — all internal href targets exist
3. Image references — all img src files exist
4. No placeholder text — no {{MARKERS}}, TODO, FIXME, SCREENSHOT NEEDED
5. Design system compliance — Google Fonts loaded, dark theme, viewport meta
6. Portal consistency — all docs linked from index.html
7. Nav consistency — every doc has the same global nav links
8. Auth gate — portal and sensitive docs use sg-auth sessionStorage

Fix any errors found. Report warnings.

Commit all docs changes:

1. Create branch: docs/make-docs-rebuild-$(date +%Y%m%d)
2. Stage all changes in docs/
3. Commit: "docs: rebuild all documentation with make-docs skill — orange design system, consolidated strategy, stealth marketing, standardized nav"
4. Push and create PR with summary of what changed

Set up a nightly 3am scheduled task for supergentic docs:

- Task ID: supergentic-docs-update
- Schedule: 0 3 * * * (daily at 3am)
- Use make-docs skill in UPDATE mode
- Repo: ~/dev/supergentic
- Brand: orange #FE9339, auth sg-auth/next
- If changes detected: update affected docs, recapture screenshots, validate, commit + PR
- If no changes: log "supergentic docs are current" and exit

I'm Brian from Dilshaus Ventures. I need to rebuild the documentation for my project **supergentic** using the make-docs skill.

## What is supergentic
AI-powered marketing operations platform for Salesforce Marketing Cloud. React 19 SPA (Vite + Tailwind + React Router), no backend. 15+ pages, 30+ components, 5 AI agents, Console with command palette, multi-step wizard. Repo at ~/dev/supergentic.

## What I need
1. Select folder ~/dev/supergentic
2. Install the make-docs skill from ~/dev/stitchwand/docs/make-docs.skill (or it may already be installed)
3. Run make-docs in MAKE mode — analyze the codebase, detect gaps, present a plan
4. After I approve, generate all docs with orange #FE9339 branding
5. Consolidate strategy docs into tabbed strategy.html (AI Strategy, GTM, Growth, Paid Ads, Stealth Marketing)
6. Add stealth marketing with warning modal
7. Validate everything
8. Commit + PR
9. Set up nightly 3am update schedule

## Brand details
- Accent: #FE9339 (orange), dark variant #E57C00
- Background: #0A0A0A
- Fonts: Inter + SF Mono/Fira Code
- Auth: sessionStorage sg-auth, password "next", URL bypass ?auth=next
- Company: Dilshaus Ventures / The Fieldhaus
- Secondary: green #45C65A, purple #9050E9, blue #1B96FF, cyan #00BDD6

## Reference
The stitchwand docs at ~/dev/stitchwand/docs/ are the gold standard. Match that quality and design system but with orange branding. Key files to reference: strategy.html (8-tab consolidated), launch-plan.html (task system with sidebar), demo.html (5-tab with filter pills).

Start by selecting the supergentic folder and running the analysis.