Kompense Changelog — Seed Entries

5 seed entries to populate /changelog. KC plugs each into src/content/changelog/*.md for #61.


Entry 1 — 2026-06-30

v1.0 — Listing Day Release

The complete operator product is live.

After 6 weeks of focused engineering, Kompense's operator portal is production-ready and shipped. This is the launch of the "complete buyer-ready operator product" — the version we list on Acquire.com today.

Added

  • 20+ admin pages with full operator control (dashboard, users, support, chat, logs, billing, settings, integrations, campaigns, promo codes, knowledge base, testimonials)
  • 6 embedded AI agents (Gemini-powered, all approved-before-execute):
    • Admin Chat with 13 tools (7 read + 6 write w/ confirmation panel)
    • Support Triage (auto-categorize tickets + draft replies with voice scoring)
    • Email Campaign Writer (with A/B subject variants)
    • Lead Qualifier (ICP fit scoring 0-100)
    • Churn Risk Predictor (daily composite score + intervention prompts)
    • Knowledge Base Generator (resolved tickets → draft articles)
  • Self-sustaining loops:
    • 8-email automated trial lifecycle (D0, D1, D3, D7, D14, D25, D30, D35)
    • Referral program with KMP-{code} per user + Stripe credits ($79 to referrer)
    • Annual pricing option (17% off)
    • Usage-based upsell banner at 80% tier limit
  • Forge separation surface (/dashboard/admin/integrations):
    • API key management with revoke
    • Webhook destinations with HMAC + retry
    • 30-second clean disconnect at sale day
  • Public surfaces:
    • /help (knowledge base with 20 seed articles)
    • /refer (customer referral landing)
    • /redeem/[code] (promo code redemption)
    • /changelog (this page)
    • /roadmap
    • /vs/klue, /vs/crayon, /vs/kompyte (SEO comparison pages)
  • Production-grade compliance:
    • GDPR cookie consent banner with categorized opt-in + audit trail
    • Sentry error tracking with PII gating
    • A+ security headers
    • Disaster recovery runbook + monthly backup-verify cron

Fixed

  • arl_ → ksk_ API key prefix rename (legacy Aurel branding cleaned)
  • PII leak on users + tenants tables via RLS hardening
  • Admin chat read tool registry evolution (multi-session support via separate admin_conversations table)
  • vercel.json cron entry consolidation across 22 production cron schedules
  • admin-nav.tsx 9-tab navigation merge

Changed

  • Stale 3 intelligence modules (Social, Reviews, Content) now hidden behind feature flags labeled "Coming Q4 2026"
  • Stripe checkout supports monthly + annual options at all 5 tiers
  • Triage agent voice-coach gate now rejects banned phrases (leverage, synergy, etc.) and regenerates

Known issues (documented in /dashboard/admin/runbooks)

  • conversations.onConflict: 'user_id' collapses distinct chat context_types into one row (fix post-listing)
  • 2 stale n8n workflows from pre-rebrand Aurel era (to be disabled or rebuilt)

Migration

  • 24 production migrations applied to Supabase (all additive, all IF NOT EXISTS)
  • All RLS policies tightened
  • 22 Vercel cron schedules registered

Entry 2 — 2026-06-28

Wave E-3 + E-4 Polish Release

Production-grade polish for listing day.

Added

  • Status page at status.kompense.com (BetterStack)
  • Public /changelog with RSS feed
  • Public /roadmap (this page references it)
  • /dashboard/admin/health (5-minute cron health checks on 7 services)
  • /dashboard/admin/costs (cost monitoring dashboard with per-customer cost-to-serve)
  • /dashboard/admin/exports (bulk data export with signed URL email delivery)
  • /dashboard/admin/api-docs (auto-generated OpenAPI viewer)
  • /dashboard/admin/runbooks (10 operational runbooks)
  • 3 SEO comparison pages (vs Klue, Crayon, Kompyte)
  • A+ security headers via next.config.js

Changed

  • Onboarding tour rebuilt with driver.js
  • GDPR self-serve verified end-to-end

Fixed

  • Various minor UI polish issues

Entry 3 — 2026-06-20

Wave E-1 + E-2 Self-Sustaining Loops Release

The product now runs itself.

Added

  • Customer health score (composite: usage + sentiment + payment + login + features)
  • Referral program (KMP codes + Stripe coupons + $79 credit on conversion)
  • Annual pricing option at all 5 tiers (17% discount)
  • Usage-based upsell banner at 80% tier limit
  • Knowledge base + /help (20 seed articles)
  • NPS surveys at trial Day 14 + 60d pulse (detractor → ticket, promoter → testimonial)
  • Testimonials collection flow

Changed

  • Customer dashboard now includes upgrade banner for soft-limit users
  • Email Campaign Writer agent integrated with /admin/campaigns

Entry 4 — 2026-06-15

Wave D Forge Separation Release

Clean handover architecture.

Added

  • /dashboard/admin/integrations for API keys + webhook destinations
  • fireWebhook() helper with HMAC signing + retry queue
  • Auto-seed of legacy FORGE_WEBHOOK_URL env into webhook_destinations table
  • Set feature flag chat tool (set_feature_flag(key, value, rules))
  • Email campaigns CRUD + Resend send + A/B variant tracking
  • Trial lifecycle seeding + daily-trial-lifecycle cron
  • Promo codes with Stripe coupon sync

Changed

  • Existing single-Forge-env-URL system migrated to webhook destinations table
  • All admin write tools now use confirmation panel pattern

Entry 5 — 2026-06-10

Wave B + C Admin Core Release

The complete admin shell.

Added

  • /dashboard/admin/dashboard (P2 analytics)
  • /dashboard/admin/users (P3 list + dossier + 5 actions)
  • /dashboard/admin/support (P4 native ticketing)
  • /dashboard/admin/chat (P5 admin chat with 13 tools)
  • /dashboard/admin/logs (P6 logs + audit + Sentry errors)
  • /dashboard/admin/billing (revenue + refund history)
  • admin.kompense.com middleware rewrite to /dashboard/admin/*

Changed

  • admin-nav.tsx now 9 tabs (full Wave A-C feature set)

How to add a new changelog entry

When KC ships a new release:

  1. Create src/content/changelog/YYYY-MM-DD-release-name.md

  2. Use the template above (Title, Added, Changed, Fixed, Known issues, Migration)

  3. Tag with version number for SemVer (v1.0, v1.1, etc.)

  4. Push to main → /changelog page auto-renders

  5. (Optional) Tweet/LinkedIn post about the release

  6. (Optional) Email existing customers via Resend campaign