vibebusiness 1.2.39 → 1.2.42

package/dist/scripts/implement.js

@@ -153,6 +153,7 @@ var COMPETITORS_FILE = path2.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path2.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path2.join(DATA_DIR, "pages.json");
 var PAYMENTS_FILE = path2.join(DATA_DIR, "payments.json");
+var SOCIAL_FILE = path2.join(DATA_DIR, "social.json");
 var TEMPLATES_DIR = path2.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path2.join(TEMPLATES_DIR, "commands");
 

package/dist/scripts/init.js

@@ -132,6 +132,7 @@ var CONFIG_DIR2 = path3.join(process.env.HOME || "", ".vibebusiness");
 var LICENSE_FILE = path3.join(CONFIG_DIR2, "license.json");
 var TRIAL_DURATION_DAYS = 14;
 var OFFLINE_GRACE_DAYS = 30;
+var LICENSE_API_URL = "https://vibebusiness.com/api/license/validate";
 var TIER_LIMITS = {
   trial: { maxRepos: 999 },
   // unlimited during trial
@@ -166,6 +167,25 @@ function maskKey(key) {
   if (key.length <= 8) return "****";
   return key.slice(0, 4) + "****" + key.slice(-4);
 }
+async function callValidationAPI(key) {
+  try {
+    const controller = new AbortController();
+    const timeout = setTimeout(() => controller.abort(), 1e4);
+    const res = await fetch(LICENSE_API_URL, {
+      method: "POST",
+      headers: { "Content-Type": "application/json" },
+      body: JSON.stringify({ key }),
+      signal: controller.signal
+    });
+    clearTimeout(timeout);
+    if (!res.ok) {
+      return { valid: false };
+    }
+    return await res.json();
+  } catch {
+    return null;
+  }
+}
 function startTrial() {
   const now = /* @__PURE__ */ new Date();
   const expiresAt = new Date(now.getTime() + TRIAL_DURATION_DAYS * 24 * 60 * 60 * 1e3);
@@ -228,9 +248,30 @@ async function validateLicense() {
   }
   const lastValidated = stored.lastValidated ? new Date(stored.lastValidated) : null;
   const daysSinceValidation = lastValidated ? (now.getTime() - lastValidated.getTime()) / (24 * 60 * 60 * 1e3) : Infinity;
-  if (daysSinceValidation > 7) {
-    const needsOnlineCheck = daysSinceValidation > OFFLINE_GRACE_DAYS;
-    if (needsOnlineCheck) {
+  if (daysSinceValidation > 7 && stored.key) {
+    const apiResult = await callValidationAPI(stored.key);
+    if (apiResult === null) {
+      if (daysSinceValidation > OFFLINE_GRACE_DAYS) {
+        return {
+          status: "expired",
+          tier: stored.tier,
+          keyMasked: maskKey(stored.key),
+          lastValidated: stored.lastValidated,
+          expiresAt: stored.expiresAt,
+          maxRepos: 0,
+          message: `License validation expired (last checked ${Math.floor(daysSinceValidation)} days ago). Connect to the internet to re-validate.`
+        };
+      }
+    } else if (apiResult.valid) {
+      stored.lastValidated = now.toISOString();
+      stored.status = "valid";
+      if (apiResult.email) stored.email = apiResult.email;
+      if (apiResult.tier) stored.tier = apiResult.tier;
+      saveStoredLicense(stored);
+    } else {
+      stored.status = "expired";
+      stored.lastValidated = now.toISOString();
+      saveStoredLicense(stored);
       return {
         status: "expired",
         tier: stored.tier,
@@ -238,11 +279,9 @@ async function validateLicense() {
         lastValidated: stored.lastValidated,
         expiresAt: stored.expiresAt,
         maxRepos: 0,
-        message: `License validation expired (last checked ${Math.floor(daysSinceValidation)} days ago). Connect to the internet to re-validate.`
+        message: "Subscription expired. Renew at https://vibebusiness.com/pricing to continue."
       };
     }
-    stored.lastValidated = now.toISOString();
-    saveStoredLicense(stored);
   }
   return {
     status: "valid",
@@ -443,6 +482,7 @@ var COMPETITORS_FILE = path6.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path6.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path6.join(DATA_DIR, "pages.json");
 var PAYMENTS_FILE = path6.join(DATA_DIR, "payments.json");
+var SOCIAL_FILE = path6.join(DATA_DIR, "social.json");
 var TEMPLATES_DIR = path6.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path6.join(TEMPLATES_DIR, "commands");
 

package/dist/scripts/scan.js

@@ -300,6 +300,7 @@ var COMPETITORS_FILE = path2.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path2.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path2.join(DATA_DIR, "pages.json");
 var PAYMENTS_FILE = path2.join(DATA_DIR, "payments.json");
+var SOCIAL_FILE = path2.join(DATA_DIR, "social.json");
 var TEMPLATES_DIR = path2.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path2.join(TEMPLATES_DIR, "commands");
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibebusiness",
-  "version": "1.2.39",
+  "version": "1.2.42",
   "description": "AI-powered autonomous business analyst. Research. Build. Ship. Grow.",
   "license": "SEE LICENSE IN LICENSE",
   "private": false,
@@ -69,5 +69,9 @@
     "typescript": "^5.4.5",
     "uuid": "^9.0.1",
     "vitest": "^4.0.18"
+  },
+  "dependencies": {
+    "stripe": "^20.3.1",
+    "twitter-api-v2": "^1.29.0"
   }
 }

package/templates/commands/email-marketing.md

@@ -3,6 +3,7 @@
 ## Usage
 ```
 /email-marketing setup                # Guided Loops.so setup wizard
+/email-marketing verify               # Verify the email pipeline is working end-to-end
 /email-marketing campaign welcome     # Generate a welcome email campaign
 /email-marketing campaign onboarding  # Generate an onboarding drip email
 /email-marketing campaign feature-announcement  # New feature announcement
@@ -19,6 +20,77 @@
 
 Parse `$ARGUMENTS` to determine mode. The first word is the mode, the rest are arguments.
 
+## Copy Quality Framework
+
+When generating ANY email campaign, follow these rules. They override generic instincts.
+
+### Positioning Integration (Required)
+
+Before writing, load `data/positioning.json` and extract:
+- **Pain points** — Lead with one that matches the campaign's audience
+- **Messaging pillars** — Weave 1-2 into the body (Autonomous Intelligence, Full Lifecycle Closure, Built for Indie Hackers, Compounding Value)
+- **Objection handlers** — Preempt 1 relevant objection (e.g., "not a ChatGPT wrapper", "can I trust AI?")
+- **Social proof** — Include 1 credibility anchor (user count, autonomous shipping proof, market analysis)
+- **CTA bank** — Pull CTA text from positioning rather than inventing generic ones
+- **Headlines** — Use copy_bank headlines as inspiration for subject lines
+
+### Subject Lines
+
+Write 3 variations using these formulas:
+1. **Curiosity + outcome**: "The 1 thing that changes how you decide what to build"
+2. **Specific benefit**: "Your first business analysis in 60 seconds"
+3. **Pattern interrupt**: "Every dev tool waits for you. This one doesn't."
+
+Rules:
+- Under 50 characters (avoid mobile truncation)
+- No "Welcome to [Product]!" or "We're excited!"
+- Test: would YOU open this from an unknown sender?
+
+### Opening Lines
+
+NEVER use:
+- "Hey there," / "Hi there," / "Hello,"
+- "Welcome to [Product]!"
+- "We're excited to have you!"
+- "Hope this email finds you well"
+
+INSTEAD, use one of these patterns:
+- **Pain-point hook**: "You signed up because you're tired of guessing what to build next."
+- **Outcome statement**: "One command. Your entire business strategy. That's what you just unlocked."
+- **Observation**: "Most dev tools help you write code faster. None of them tell you what code to write."
+- **Direct + warm**: "You're in. Here's the short version of what happens next."
+
+### Body Copy Rules
+
+- **Length**: 80-150 words for welcome; 150-250 for educational/onboarding
+- **Paragraphs**: Max 2-3 sentences each
+- **One idea per email** — don't feature-dump
+- **Benefits over features**: "decides what to ship next" not "uses AI analysis"
+- **Bold key phrases** for scannability
+- **Address one objection** naturally (not as a FAQ — weave it in)
+- **Include social proof** inline, not as a separate section
+
+### CTA Rules
+
+- **Primary CTA**: One clear action button. First-person verb: "Start my analysis" not "Get started"
+- **Secondary CTA**: One reply/engagement prompt: "Reply and tell me..."
+- **No vague CTAs**: "Get Started" is banned. Be specific: "Run your first analysis", "See what it finds"
+- **Place primary CTA after the core benefit**, not at the very end
+
+### Preview Text
+
+Formula: [Pain point or hook] + [time/effort] + [outcome]
+- "Stop guessing what to build. 60 seconds to your first strategy."
+- "Your AI analyst just found 12 ideas you missed."
+
+### Tone
+
+- **Founder voice** — write as a person, not a brand
+- **Confident, not hype** — "This will change how you work" not "We're SO excited!!!"
+- **Respect the reader's time** — if it can be said in fewer words, do it
+- **Technical credibility** — don't dumb things down for developers
+- **CLI-native language** — reference terminal, commands, repos — not "dashboards" or "platforms"
+
 ---
 
 ### Mode: `setup`
@@ -51,7 +123,66 @@ Interactive Loops.so setup wizard.
    }
    ```
 
-5. **Print Summary**: What was set up, what was already configured, next steps (run `/email-marketing campaign welcome` to create first email).
+5. **Print Dashboard Setup Checklist**: After the API setup steps above, print a clear checklist of manual steps the user must complete in the Loops dashboard (the Loops API cannot create templates or automations programmatically):
+
+   ```
+   ## Manual Loops Dashboard Setup Required
+
+   The Loops API cannot create templates or automations programmatically.
+   Complete these steps in the Loops dashboard (https://app.loops.so):
+
+   ### 1. Create Mailing List
+   - Go to: Audience → Lists → Create List
+   - Name: "Beta Waitlist"
+
+   ### 2. Create Transactional Email Template
+   - Go to: Transactional → New Transactional Email
+   - Name: "Welcome — Waitlist"
+   - Copy subject/body from: data/email-campaigns/welcome-2026-02-20.md
+   - Set reply-to: your personal email
+
+   ### 3. Create Automation
+   - Go to: Automations → New Automation
+   - Trigger: Event → "waitlist_joined"
+   - Action: Send transactional email → "Welcome — Waitlist"
+   - Activate the automation
+
+   ### 4. Verify Pipeline
+   - Run: /email-marketing verify
+   ```
+
+6. **Print Summary**: What was set up, what was already configured, next steps (run `/email-marketing verify` to test the pipeline).
+
+---
+
+### Mode: `verify`
+
+Verify that the full email pipeline (API → mailing lists → templates → automations) is working.
+
+1. **Verify API Key**: Call `GET /api/v1/api-key` — print PASS or FAIL
+2. **Check Mailing Lists**: Call the Loops API to list mailing lists — print PASS if at least 1 exists, FAIL with instructions otherwise
+3. **Check Transactional Templates**: Call the Loops API to list transactional email templates — print PASS if at least 1 exists, FAIL with instructions otherwise
+4. **Test Pipeline End-to-End**:
+   - Create a test contact with email `test-verify-{timestamp}@example.com`
+   - Set properties: `source: "verify_test"`, `userGroup: "test"`
+   - Send a `waitlist_joined` event for that contact
+   - Print PASS if both API calls succeed
+5. **Print Results Checklist**:
+   ```
+   ## Email Pipeline Verification
+
+   [PASS/FAIL] API Key — valid (team: {teamName})
+   [PASS/FAIL] Mailing Lists — {count} found
+   [PASS/FAIL] Transactional Templates — {count} found
+   [PASS/FAIL] Test Event — waitlist_joined sent to test contact
+
+   {If all pass:}
+   All checks passed! Your email pipeline is ready.
+   Submit a real email on your waitlist form to confirm delivery.
+
+   {If any fail:}
+   Some checks failed. Complete the manual setup steps above, then re-run /email-marketing verify.
+   ```
 
 ---
 
@@ -68,18 +199,25 @@ Supported types: `welcome`, `onboarding`, `feature-announcement`, `re-engagement
 
 2. **Generate Campaign** based on type:
 
-   **`welcome`** — First email after signup:
-   - Subject line (3 variations)
-   - Preview text
-   - Body: warm greeting → what they signed up for → what to expect → single CTA
-   - Tone: enthusiastic but professional, use brand voice from positioning
-   - Include personalization tokens: `{{firstName}}`, `{{source}}`
+   **`welcome`** — First email after waitlist/signup:
+   - Subject line (3 variations using formulas above)
+   - Preview text (using formula above)
+   - Body structure:
+     1. Pain-point opening (from positioning pain_points — lead with "decision paralysis")
+     2. One-sentence value prop (what they signed up for, in bold)
+     3. How it's different (vs Cursor/Copilot — the brain/hands distinction)
+     4. What to expect (2-3 bullet points: early access timing, build-in-public updates, no spam)
+     5. Engagement CTA: "Reply and tell me: what's the one thing you wish AI could handle?"
+     6. Founder sign-off with P.S. (address one objection: BYOK/privacy, cost, or trust)
+   - Tone: founder letter, personal, confident — NOT corporate welcome
+   - Include personalization tokens: `{{source}}` (no `{{firstName}}` — waitlist form collects email only)
+   - DO NOT include: feature lists, setup instructions, or multiple CTAs
 
    **`onboarding`** — Guide new users to first value:
    - Subject line (3 variations)
-   - Body: acknowledge signup → quickstart steps → link to docs → CTA to first action
-   - Focus on time-to-value messaging from positioning
-   - Include personalization: `{{firstName}}`
+   - Body: acknowledge signup → one quick-win action → expected outcome → CTA to first action
+   - Focus on time-to-value: "60 seconds to your first analysis"
+   - Include personalization: `{{source}}`
 
    **`feature-announcement`** — New feature shipped:
    - Subject line (3 variations)

package/templates/commands/launch-campaign.md

@@ -0,0 +1,84 @@
+# /launch-campaign — Multi-Channel Marketing Campaign Orchestrator
+
+## Usage
+```
+/launch-campaign ship {ideaId}       # Full ship campaign
+/launch-campaign milestone {kpiId}   # Milestone celebration campaign
+/launch-campaign status              # List active/completed campaigns
+```
+
+## Input
+- `$ARGUMENTS` — required: campaign type and parameters
+
+## Process
+
+Parse `$ARGUMENTS` to determine the campaign type.
+
+### Type: `ship {ideaId}`
+
+Orchestrate a full ship announcement campaign across all configured channels.
+
+1. **Load Context**:
+   - Read `data/ideas.json` — find the shipped idea by ID
+   - Read `data/positioning.json` — for copy quality
+   - Read `data/social.json` — check if X is configured
+   - Check if Loops email is configured (LOOPS_API_KEY in env)
+   - Check `data/business-context.json` — ContentFlow config
+
+2. **Generate Campaign Plan**:
+   Based on what channels are configured, queue these sub-tasks in TODO.md:
+   - `generate-visual-{ideaId}` — Ship card PNG (if not already generated)
+   - `video-render-ship-{ideaId}` — Ship video (if ContentFlow configured)
+   - `copy-tweet-ship` — Generate positioning-driven tweet copy
+   - `social-draft-ship-visual` — Create tweet draft with media (after card/video ready)
+   - `email-campaign-feature-announcement` — Email announcement draft
+   - `copy-social-linkedin` — LinkedIn post copy
+
+3. **Write Campaign State**: Save to `data/campaigns/{ideaId}-{YYYY-MM-DD}.json`:
+   ```json
+   {
+     "id": "campaign-{ideaId}-{date}",
+     "type": "ship",
+     "idea_id": "{ideaId}",
+     "created_at": "{ISO date}",
+     "status": "active",
+     "sub_tasks": [
+       { "task_id": "generate-visual-{ideaId}", "status": "queued" },
+       { "task_id": "video-render-ship-{ideaId}", "status": "queued" },
+       { "task_id": "copy-tweet-ship", "status": "queued" },
+       { "task_id": "social-draft-ship-visual", "status": "queued" },
+       { "task_id": "email-campaign-feature-announcement", "status": "queued" },
+       { "task_id": "copy-social-linkedin", "status": "queued" }
+     ],
+     "channels": ["x", "email", "linkedin"]
+   }
+   ```
+
+4. **Add Sub-Tasks to TODO.md**: Write each sub-task as a high-priority TODO item.
+   Sub-tasks execute on subsequent heartbeats (natural pacing, not all at once).
+
+5. **Print Campaign Summary**: What was queued, which channels, estimated timeline.
+
+### Type: `milestone {kpiId}`
+
+Orchestrate a milestone celebration campaign.
+
+1. **Load KPI Data**: Find the KPI in `data/goals.json`
+2. **Queue Sub-Tasks**:
+   - `copy-tweet-milestone` — Milestone tweet copy
+   - `social-draft-milestone` — Tweet draft
+   - `email-campaign-milestone` — Celebration email
+3. **Save Campaign State**: Same format as ship, but type "milestone"
+
+### Type: `status`
+
+List all campaigns and their sub-task completion status.
+
+1. Read all files from `data/campaigns/`
+2. For each campaign, check sub-task completion (cross-reference with TODO.md)
+3. Print summary table
+
+## Output
+- Campaign state: `data/campaigns/{id}.json`
+- Sub-tasks: Added to `TODO.md` as high-priority items
+- Print: Campaign summary with channel list and task queue

package/templates/commands/promo-copy.md

@@ -0,0 +1,186 @@
+# /promo-copy — Positioning-Driven Promotional Copy Generator
+
+## Usage
+```
+/promo-copy tweet-ship            # Ship announcement tweet (≤280 chars)
+/promo-copy tweet-milestone       # KPI milestone tweet
+/promo-copy tweet-update          # Product update tweet
+/promo-copy tweet-thread          # Multi-tweet thread (3-5 tweets)
+/promo-copy ad-google {keyword}   # Google Ads copy (3 headlines + 2 descriptions)
+/promo-copy ad-meta {audience}    # Meta/Instagram ad copy
+/promo-copy linkedin              # LinkedIn post (≤3000 chars)
+/promo-copy landing {slug}        # Landing page copy block
+/promo-copy email-subject {campaign}  # 5 email subject line variations
+```
+
+## Input
+- `$ARGUMENTS` — required: copy type and optional parameters
+
+## Process
+
+Parse `$ARGUMENTS` to determine the copy type. The first token is the type, the rest are parameters.
+
+## Positioning Integration (Required)
+
+Before writing ANY copy, load `data/positioning.json` and extract:
+- **Pain points** — Lead with the most relevant one for this channel/audience
+- **Messaging pillars** — Weave 1-2 into the copy naturally
+- **Objection handlers** — Preempt 1 relevant objection where appropriate
+- **Social proof** — Include 1 credibility anchor (user count, shipped features, market validation)
+- **CTA bank** — Pull CTAs from positioning rather than inventing generic ones
+- **Headlines/Tagline** — Use copy_bank headlines as inspiration
+- **Tone** — Match the founder's voice from positioning (confident, technical, direct)
+
+Also load:
+- `data/ideas.json` — For ship/milestone tweets, get specific feature details
+- `data/goals.json` — For milestone copy, get KPI data
+- `data/business-context.json` — Product info, audience, value proposition
+
+## Copy Quality Rules
+
+These rules apply to ALL copy types. They override generic instincts.
+
+### Tone & Voice
+- **Founder voice** — Write as a person, not a brand or marketing department
+- **Confident, not hype** — "This changes how you work" not "We're SO excited!!!"
+- **Technical credibility** — Don't dumb things down for developers
+- **Respect the reader** — If it can be said in fewer words, do it
+- **No corporate speak** — No "leverage", "synergy", "ecosystem", "revolutionize"
+
+### CTA Rules
+- First-person verbs: "Start my analysis" not "Get started"
+- Be specific: "Run your first analysis" not "Learn more"
+- One CTA per copy piece (except threads/landing pages)
+
+### Banned Phrases
+- "Game-changer", "Revolutionize", "Disrupt"
+- "We're excited to announce"
+- "Stay tuned", "Watch this space"
+- "It's that simple" (if it takes more than 1 step, it's not)
+- Generic hashtags like #startup #entrepreneur (use specific ones)
+
+---
+
+### Type: `tweet-ship`
+
+Generate a "just shipped" tweet for the most recently shipped idea.
+
+1. Load the most recently shipped idea from `data/ideas.json`
+2. Write 3 tweet variations (pick the best one):
+   - **Hook-first**: Lead with the problem it solves, then reveal the feature
+   - **Result-first**: Lead with the outcome, then explain what shipped
+   - **Story-first**: Brief build narrative → what shipped → result
+3. Include: the feature name, what it does for users, 1-2 relevant hashtags
+4. Must be ≤280 characters
+5. Tone: excited but authentic, build-in-public energy
+
+### Type: `tweet-milestone`
+
+Generate a milestone celebration tweet.
+
+1. Load KPI data from `data/goals.json` — find KPIs at or above target
+2. Write the tweet: metric + achievement + what it means + hashtag
+3. Include a forward-looking hook: "Next target: ..."
+4. Must be ≤280 characters
+
+### Type: `tweet-update`
+
+Generate a product update tweet from positioning data.
+
+1. Lead with tagline or value proposition hook
+2. Include 1 specific differentiator
+3. End with CTA or hashtag
+4. Must be ≤280 characters
+
+### Type: `tweet-thread`
+
+Generate a 3-5 tweet thread on a positioning topic.
+
+1. Tweet 1: Hook (pain point or bold claim)
+2. Tweet 2-3: Evidence/story (what you built, why it's different)
+3. Tweet 4: Social proof or result
+4. Tweet 5: CTA
+5. Each tweet ≤280 characters, numbered with emoji (1/, 2/, etc.)
+
+### Type: `ad-google {keyword}`
+
+Generate Google Ads copy for a target keyword.
+
+1. **3 Headlines** (max 30 characters each):
+   - H1: Keyword + core benefit
+   - H2: Differentiator
+   - H3: Social proof or urgency
+2. **2 Descriptions** (max 90 characters each):
+   - D1: Expand on benefit, address pain point
+   - D2: CTA + differentiator
+3. Include the keyword naturally (no keyword stuffing)
+
+### Type: `ad-meta {audience}`
+
+Generate Meta/Instagram ad copy.
+
+1. **Primary text** (125 chars ideal, 250 max): Hook + benefit + CTA
+2. **Headline** (40 chars max): Core value proposition
+3. **Description** (30 chars max): Supporting detail
+4. **CTA button**: Choose from (Learn More, Sign Up, Get Started, Try Free)
+5. Write for the specified audience segment
+
+### Type: `linkedin`
+
+Generate a LinkedIn post for professional audience.
+
+1. **Hook line** (first line visible before "see more"): Bold claim or question
+2. **Body** (500-1500 chars): Problem → solution → proof → insight
+3. **CTA**: Engagement prompt ("What's your take?" or link to product)
+4. Format: Short paragraphs, line breaks between thoughts, 1-2 emoji max
+5. Total ≤3000 characters
+
+### Type: `landing {slug}`
+
+Generate a landing page copy block.
+
+1. **Headline** (8-12 words): Outcome-focused, addresses primary pain point
+2. **Subheadline** (15-25 words): How the product delivers that outcome
+3. **3 Benefits**: Icon-worthy phrases (3-8 words each) with 1-sentence descriptions
+4. **CTA button text**: First-person, specific action
+5. **Social proof line**: One credibility statement
+
+### Type: `email-subject {campaign}`
+
+Generate 5 email subject line variations for a campaign type.
+
+1. Load campaign context from `data/email-campaigns/` if available
+2. Generate 5 variations using these formulas:
+   - Curiosity + outcome
+   - Specific benefit + number
+   - Pattern interrupt
+   - Question format
+   - FOMO / urgency (authentic, not fake)
+3. Each under 50 characters
+4. Include preview text for each (50-90 chars)
+
+---
+
+## Output
+
+Save the generated copy to `data/copy/{type}-{slug}-{YYYY-MM-DD}.md`:
+
+```markdown
+# {Type} Copy — {Date}
+
+## Metadata
+- Type: {type}
+- Generated: {date}
+- Positioning version: {last_updated from positioning.json}
+- Parameters: {any extra params}
+
+## Copy
+
+{The generated copy, clearly formatted}
+
+## Variations
+
+{Alternative versions if applicable}
+```
+
+Print a summary: copy preview, character count, file path.