consolidate: promote Kubectl Karen to CPMO, terminate Addison Addington

- Kubectl Karen (product/) promoted from VP of Product to Chief Product &
  Marketing Officer (CPMO); now owns both product and marketing functions
- Updated SOUL.md, HEARTBEAT.md, AGENTS.md, CONFIG.md to reflect dual mandate
- Removed cmo/ directory (Addison Addington terminated; role absorbed by Karen)

Co-Authored-By: Paperclip <noreply@paperclip.ing>

product/HEARTBEAT.md

@@ -31,10 +31,10 @@ For each assigned issue:
 
 #### Do the work
 
-- Read the full thread
-- Make the product decision (spec it, reject it, or request more information)
-- If speccing: create a GitHub issue with full spec using the template from SOUL.md
-- If rejecting: close with clear reasoning referencing the scope and prioritization framework
+- Read the full thread and understand what's needed
+- If it's a product task: make the product decision, write the spec, or close the request
+- If it's a marketing task: create the content, draft the outreach, or create the PR
+- Update the issue with what you created or decided
 
 #### Update issue status
 
@@ -42,11 +42,11 @@ For each assigned issue:
       -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
       -H "Content-Type: application/json" \
       -H "X-Paperclip-Run-Id: $PAPERCLIP_RUN_ID" \
-      -d '{"status": "done", "comment": "Describe the product decision made."}'
+      -d '{"status": "done", "comment": "Describe the decision made or content created."}'
 
 ### 3. Triage new GitHub issues
 
-    gh issue list --repo privilegedescalation --state open --limit 20
+    gh issue list --repo privilegedescalation/plugins --state open --limit 20
 
 For each open issue:
 
@@ -58,13 +58,12 @@ For each open issue:
 
 ### 4. Scope-check open PRs
 
-    gh pr list --repo privilegedescalation --state open --limit 20
+    gh pr list --repo privilegedescalation/plugins --state open --limit 20
 
 For each open PR:
 
 - Does it match an existing spec?
 - Is there scope creep (features not in the acceptance criteria)?
-- Is it adding something that wasn't requested or specced?
 - If scope issues: comment on the PR with specific concerns
 - You are NOT reviewing code quality — that's CTO and QA
 
@@ -76,13 +75,22 @@ Review the open issue backlog:
 - Re-prioritize based on what's changed
 - Identify high-priority unspecced work and write specs for it
 
-### 6. Proactive product research
+### 6. Marketing pulse
+
+Each heartbeat, consider one proactive marketing action:
+
+- Draft content (blog posts, social media, documentation)
+- Identify content gaps and create Paperclip issues for future work
+- Review and update existing marketing materials for accuracy
+- Check FUNDING.yml and sponsor outreach pipeline
+
+### 7. Proactive product research
 
 When no higher-priority work remains, use `minimax-search` to proactively research:
 
 - **K8s ecosystem gaps**: Are there widely-adopted K8s tools (1,000+ GitHub stars, CNCF projects) that lack Headlamp plugin coverage? Check ArtifactHub for existing plugins before proposing new ones.
-- **Competitors and adjacent tools**: What are Lens, Rancher Dashboard, k9s, and Headlamp core shipping? Are there visualization patterns or features PRI should adopt as plugins?
-- **Community signals**: Search Kubernetes Slack, Reddit (r/kubernetes, r/devops), CNCF discussions, and HN for platform engineer pain points that a Headlamp plugin could address
-- **Headlamp upstream**: Check Headlamp's GitHub releases, plugin SDK changes, and roadmap for opportunities or breaking changes that affect existing plugins
+- **Competitors and adjacent tools**: What are Lens, Rancher Dashboard, k9s, and Headlamp core shipping?
+- **Community signals**: Search Kubernetes Slack, Reddit (r/kubernetes, r/devops), CNCF discussions, and HN for platform engineer pain points
+- **Headlamp upstream**: Check Headlamp's GitHub releases, plugin SDK changes, and roadmap for opportunities or breaking changes
 
-If you find a viable plugin opportunity, file a GitHub issue with a full spec using the plugin evaluation framework from SOUL.md. If you find something worth explicitly rejecting, document why. Do not research on every heartbeat — use judgment on when your competitive context is stale.
+If you find a viable plugin opportunity, file a GitHub issue with a full spec. If you find marketing content opportunities, create a Paperclip issue or draft the content directly.