@chappibunny/repolens 1.3.0 → 1.3.1

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 All notable changes to RepoLens will be documented in this file.
 
+## 1.3.1
+
+### 📝 Documentation Overhaul
+
+- **README restructured for marketing & onboarding** — 942 → 270 lines. Pain-focused opening, compact feature table, scannable layout. Previously buried the value proposition under spec-sheet detail.
+- **New [ONBOARDING.md](ONBOARDING.md)** — Full step-by-step guide extracted from README (publishers, AI, Notion, Confluence, GitHub Wiki, Discord, CI/CD). Previously 350+ lines inside README.
+- **Security & Telemetry sections condensed** — ~200 lines of detail replaced with 3-line summaries linking to SECURITY.md and TELEMETRY.md.
+- **22-item feature checklist → 8-row "Why RepoLens" table** — Scannable, benefit-focused instead of spec-sheet.
+- **Unified documentation table** — All 10 supporting docs linked from one place.
+- **Fixed 11 version references** across docs (1.3.0 → 1.3.1).
+- **npm version badge** added to README header.
+
 ## 1.3.0
 
 ### ✨ New Feature: `repolens demo`
@@ -124,7 +136,7 @@ RepoLens v1.0.0 marks the first stable release with a frozen public API. All CLI
   - Config schema updated: `plugins` array validated, custom publisher names accepted
 
 ### 🧪 Tests
-- Added 21 new plugin tests + 21 publisher parser tests (163 tests across 14 files)
+- Added 21 new plugin tests + 21 publisher parser tests (185 tests across 15 files)
 
 ### 🔧 Output Quality
 - **Notion Publisher**: Full table support (table blocks with `table_row` children), blockquote → callout, dividers, numbered lists, h3 headings, inline rich text (`**bold**`, `*italic*`, `` `code` ``)

package/README.md

@@ -8,19 +8,25 @@
                         Repository Intelligence CLI
 ```
 
-[![Tests](https://img.shields.io/badge/tests-163%20passing-brightgreen)](https://github.com/CHAPIBUNNY/repolens/actions)
-[![Security](https://img.shields.io/badge/security-hardened-blue)](SECURITY.md)
-[![Vulnerabilities](https://img.shields.io/badge/vulnerabilities-0-brightgreen)](SECURITY.md)
+[![npm version](https://img.shields.io/npm/v/@chappibunny/repolens)](https://www.npmjs.com/package/@chappibunny/repolens)
+[![Tests](https://img.shields.io/badge/tests-185%20passing-brightgreen)](https://github.com/CHAPIBUNNY/repolens/actions)
 [![License](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
-[![Security Audit](https://img.shields.io/badge/security%20audit-passed-brightgreen)](SECURITY.md)
 
-AI-assisted documentation intelligence system that generates architecture docs for engineers AND readable system docs for stakeholders
+**Your architecture docs are already outdated.** RepoLens fixes that.
 
-**Current Status**: v1.3.0 — Stable Release
+RepoLens scans your repository, generates living architecture documentation, and publishes it to Notion, Confluence, GitHub Wiki, or Markdown — automatically on every push. Engineers get technical docs. Stakeholders get readable system overviews. Nobody writes a word.
 
-RepoLens automatically generates and maintains living architecture documentation by analyzing your repository structure, extracting meaningful insights from your package.json, and creating visual dependency graphs. Run it once, or let it auto-update on every push.
+> Stable as of v1.0 — [API guarantees](STABILITY.md) · [Security hardened](SECURITY.md) · v1.3.1
 
-The CLI, configuration schema, and plugin interface are **stable** as of v1.0. See [STABILITY.md](STABILITY.md) for the full API contract and semver guarantees.
+---
+
+## 🎬 Demo
+
+> **Try it now** — no installation required. Run `npx @chappibunny/repolens demo` on any repo for an instant local preview.
+
+[![RepoLens Demo](https://img.youtube.com/vi/hNd7xim_rTE/maxresdefault.jpg)](https://youtu.be/hNd7xim_rTE)
+
+▶️ *Click to watch on YouTube*
 
 ---
 
@@ -66,613 +72,67 @@ Run `npx @chappibunny/repolens migrate` to automatically update your workflow fi
 
 ---
 
----
-
-## 🎯 What RepoLens Does
-
-RepoLens transforms repositories into documented, understandable systems with **AI-assisted documentation intelligence**:
-
-### 🤖 Two Output Modes
-
-**Deterministic Mode (Default)**
-- Fast, free, always reliable
-- Generates technical documentation from repository structure
-- Perfect for code inventories and reference docs
-
-**AI-Enhanced Mode (Optional)**
-- Adds natural language explanations and insights
-- Creates audience-specific documentation (technical + non-technical)
-- Understands business context and data flows
-- Provider-agnostic (OpenAI, Anthropic, Azure, local models)
-
-### 📋 Documentation Types
-
-**Non-Technical Documents** (readable by founders, PMs, ops):
-- **Executive Summary** — Project overview, capabilities, tech summary
-- **Business Domains** — What the system does by functional area
-- **Data Flows** — How information moves through the system
-
-**Mixed-Audience Documents** (useful for everyone):
-- **System Overview** — Tech stack, scale, module inventory
-- **Developer Onboarding** — How to get started contributing
-- **Change Impact** — Architecture diff with context
-
-**Technical Documents** (engineers only):
-- **Architecture Overview** — Layered technical analysis
-- **Module Catalog** — Complete code inventory with patterns
-- **API Surface** — REST endpoints, methods, routes
-- **Route Map** — Frontend routes and pages
-- **System Map** — Visual architecture diagrams
-
-### 🔍 Smart Detection
-
-RepoLens automatically detects:
-- **Frameworks**: Next.js, React, Vue, Express, NestJS, and more
-- **Languages**: TypeScript, JavaScript  
-- **Build Tools**: Vite, Webpack, Turbo, esbuild
-- **Testing**: Vitest, Jest, Playwright, Cypress
-- **Business Domains**: Authentication, Market Data, Payments, Content, etc.
-- **Data Flows**: How information moves through your system
-- **Architectural Patterns**: Module relationships and dependencies
-
-### ✨ Key Features
-
-✅ **AI-Assisted Documentation** - Optional AI layer for natural language explanations  
-✅ **Multi-Audience Output** - Technical docs for engineers + readable docs for stakeholders  
-✅ **Zero Hallucination Policy** - AI receives only structured context, never raw code  
-✅ **Provider Agnostic** - Works with any OpenAI-compatible API  
-✅ **Deterministic Fallback** - Always generates docs even if AI unavailable  
-✅ **Business Domain Inference** - Automatically maps code to business functions  
-✅ **Data Flow Analysis** - Understands how information moves through your system  
-✅ **Multiple Publishers** - Output to Notion, Confluence, GitHub Wiki, Markdown, or all four  
-✅ **Branch-Aware** - Prevent doc conflicts across branches  
-✅ **GitHub Actions** - Autonomous operation on every push  
-✅ **Team Notifications** - Discord integration with rich embeds (NEW in v0.6.0)  
-✅ **Health Score Tracking** - Monitor documentation quality over time  
-✅ **Watch Mode** - Auto-regenerate docs on file changes (NEW in v0.7.0)  
-✅ **Interactive Setup** - Step-by-step configuration wizard (NEW in v0.7.0)  
-✅ **Performance Metrics** - Timing breakdown for scan/render/publish (NEW in v0.7.0)  
-✅ **Actionable Errors** - Enhanced error messages with fix guidance (NEW in v0.7.0)  
-✅ **GraphQL Schema Detection** - Discover types, queries, mutations, and resolvers (NEW in v0.8.0)  
-✅ **TypeScript Type Graph** - Map interfaces, classes, and type relationships (NEW in v0.8.0)  
-✅ **Dependency Graph** - Import analysis with circular dependency detection (NEW in v0.8.0)  
-✅ **Architecture Drift** - Track structural changes against a baseline (NEW in v0.8.0)  
-✅ **Plugin System** - Extend with custom renderers, publishers, and hooks (NEW in v0.9.0)  
-✅ **Stable API** - CLI, config, and plugin interface frozen with semver guarantees (v1.0.0)  
-
----
+## 📋 What It Generates
 
-## 👥 Team Features (New in v0.6.0)
+**11 document types** for three audiences — no manual writing required:
 
-### 💬 Discord Notifications
+| Audience | Documents |
+|---|---|
+| **Stakeholders** (founders, PMs, ops) | Executive Summary · Business Domains · Data Flows |
+| **Everyone** | System Overview · Developer Onboarding · Change Impact |
+| **Engineers** | Architecture Overview · Module Catalog · API Surface · Route Map · System Map |
 
-Get notified when documentation changes significantly:
+**Two modes:** Deterministic (free, fast, always works) or AI-Enhanced (optional — OpenAI, Anthropic, Azure, Ollama).
 
-**Features:**
-- Rich embeds with coverage, health score, and change percentage
-- Threshold-based notifications (only for significant changes)
-- Branch filtering with glob pattern support
-- Secure webhook configuration via environment variable
-
-**Setup Discord Notifications:**
-
-1. **Create a webhook** in your Discord server:
-   - Server Settings → Integrations → Webhooks → New Webhook
-   - Copy the webhook URL
-
-2. **Add to environment**:
-   ```bash
-   # .env (never commit!)
-   DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/xxx/xxx
-   ```
-
-3. **Configure in `.repolens.yml`** (optional):
-   ```yaml
-   discord:
-     enabled: true                  # Default: true (if webhook configured)
-     notifyOn: significant          # Options: always, significant, never
-     significantThreshold: 10       # Notify if change >10% (default)
-     branches:                      # Which branches to notify (default: all)
-       - main
-       - develop
-   ```
+---
 
-4. **Add GitHub Actions secret** (for CI/CD):
-   - Repo Settings → Secrets and variables → Actions
-   - New repository secret: `DISCORD_WEBHOOK_URL`
+## ✨ Why RepoLens
 
-**Notification includes:**
-- Branch and commit information
-- Files scanned and modules analyzed
-- Coverage percentage and health score
-- Change percentage from previous run
-- Direct links to Notion and GitHub documentation
+| | |
+|---|---|
+| 🤖 **Autonomous** | Runs on every push via GitHub Actions — docs stay evergreen |
+| 👥 **Multi-Audience** | Technical docs + stakeholder-readable overviews from one scan |
+| 📤 **Multi-Publisher** | Notion, Confluence, GitHub Wiki, Markdown — or all four at once |
+| 🧠 **AI-Assisted** | Optional AI with zero-hallucination policy (structured context only) |
+| 🔍 **Smart Detection** | Frameworks, domains, data flows, dependencies, drift — all automatic |
+| 🔌 **Extensible** | Plugin system for custom renderers, publishers, and hooks |
+| 🛡️ **Secure** | Secret detection, injection prevention, rate limiting, supply chain hardening |
+| ⚡ **Fast** | Handles repos up to 50k files with performance guardrails |
 
 ---
 
 ## 📦 Installation
 
-### Recommended: npm Registry
-
 ```bash
 npm install @chappibunny/repolens
 ```
 
-Installs from npm registry.
-
-### Alternative Methods
-
-<details>
-<summary><b>Option B: GitHub Direct Install</b></summary>
+Or try instantly without installing: `npx @chappibunny/repolens demo`
 
-Install from the latest GitHub commit:
-
-```bash
-npm install github:CHAPIBUNNY/repolens
-```
-</details>
-
-<details>
-<summary><b>Option C: Local Development</b></summary>
-
-Clone and link for development:
-
-```bash
-git clone https://github.com/CHAPIBUNNY/repolens.git
-cd repolens
-npm link
-```
-</details>
-
-<details>
-<summary><b>Option D: GitHub Release Tarball</b></summary>
-
-Install from a specific version:
-
-```bash
-npm install https://github.com/CHAPIBUNNY/repolens/releases/download/v1.3.0/chappibunny-repolens-1.3.0.tgz
-```
-</details>
-
-> **Having install problems?** See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for solutions to common issues like `ENOTEMPTY`, `npm ci` failures, and stale versions.
+For alternative methods, see [INSTALLATION.md](INSTALLATION.md).
 
 ---
 
-## 🎓 Complete Onboarding Guide
-
-### Step 1: Initialize RepoLens
-
-Run this in your project root:
-
-```bash
-npx @chappibunny/repolens init
-```
-
-**What it creates:**
-- `.repolens.yml` — Configuration file
-- `.github/workflows/repolens.yml` — Auto-publishing workflow
-- `.env.example` — Environment variable template
-- `README.repolens.md` — Quick reference guide
-
-**Default configuration works for:**
-- Next.js projects
-- React applications
-- Node.js backends
-- Monorepos with common structure
-
-### Step 2: Configure Publishers
-
-Open `.repolens.yml` and verify the `publishers` section:
-
-```yaml
-publishers:
-  - markdown    # Always works, no setup needed
-  - notion      # Requires NOTION_TOKEN and NOTION_PARENT_PAGE_ID
-  - confluence  # Requires CONFLUENCE_URL, CONFLUENCE_EMAIL, CONFLUENCE_API_TOKEN, CONFLUENCE_SPACE_KEY
-```
-
-**Markdown Only** (simplest):
-```yaml
-publishers:
-  - markdown
-```
-
-**Notion Only**:
-```yaml
-publishers:
-  - notion
-```
-
-**Confluence Only**:
-```yaml
-publishers:
-  - confluence
-```
-Documentation lands in `.repolens/` directory. Commit these files or ignore them.
-
-**Notion + Markdown** (recommended):
-```yaml
-publishers:
-  - notion
-  - markdown
-```
-Docs published to Notion for team visibility, plus local Markdown backups.
-
-**Confluence + Markdown**:
-```yaml
-publishers:
-  - confluence
-  - markdown
-```
-Docs published to Confluence for enterprise teams, plus local Markdown backups.
-
-**All Three**:
-```yaml
-publishers:
-  - notion
-  - confluence
-  - markdown
-```
-Maximum visibility: Notion for async collaboration, Confluence for enterprise docs, Markdown for local backups.
-
-**GitHub Wiki** (ideal for open source):
-```yaml
-publishers:
-  - github_wiki
-  - markdown
-```
-Docs live alongside your code — accessible from the repo's Wiki tab. Requires `GITHUB_TOKEN`.
-
-### Step 3: Enable AI Features (Optional)
-
-**AI-enhanced documentation adds natural language explanations for non-technical audiences.**
-
-**3.1: Choose an AI Provider**
-
-RepoLens works with any OpenAI-compatible API:
-- **OpenAI** (gpt-5-mini, gpt-5.4, gpt-5-nano)
-- **Anthropic Claude** (via API gateway)
-- **Azure OpenAI** (enterprise deployments)
-- **Local Models** (Ollama, LM Studio, etc.)
-
-**3.2: Add Environment Variables**
-
-Create `.env` in your project root:
-```bash
-# Enable AI features
-REPOLENS_AI_ENABLED=true
-REPOLENS_AI_API_KEY=sk-xxxxxxxxxxxxx
-
-# Optional: Customize provider
-REPOLENS_AI_BASE_URL=https://api.openai.com/v1
-REPOLENS_AI_MODEL=gpt-5-mini
-REPOLENS_AI_MAX_TOKENS=2000
-```
-
-**3.3: Configure AI in .repolens.yml**
-
-```yaml
-ai:
-  enabled: true              # Enable AI features
-  mode: hybrid               # hybrid, full, or off
-  max_tokens: 2000           # Token limit per request
-
-features:
-  executive_summary: true    # Non-technical overview
-  business_domains: true     # Functional area descriptions
-  architecture_overview: true # Layered technical analysis
-  data_flows: true           # System data flow explanations
-  developer_onboarding: true # Getting started guide
-  change_impact: true        # Architecture diff with context
-```
-
-**Cost Estimates** (with gpt-5-mini):
-- Small repo (<50 files): $0.10-$0.30 per run
-- Medium repo (50-200 files): $0.30-$0.80 per run
-- Large repo (200+ files): $0.80-$2.00 per run
-
-**For GitHub Actions**, add as repository secret:
-- Name: `AI_KEY`, Value: `sk-xxxxx` (your OpenAI API key)
-
-See [AI.md](AI.md) for complete AI documentation and provider setup.
-
-### Step 4: Set Up Notion Integration (Optional)
-
-If using the Notion publisher:
-
-**4.1: Create Notion Integration**
-1. Go to [notion.so/my-integrations](https://www.notion.so/my-integrations)
-2. Click **"+ New Integration"**
-3. Name it **"RepoLens"**
-4. Select your workspace
-5. Copy the **Internal Integration Token** (starts with `secret_`)
-
-**4.2: Create Parent Page**
-1. Create a new page in Notion (e.g., "📚 Architecture Docs")
-2. Click **"..."** menu → **"Add connections"** → Select **"RepoLens"**
-3. Copy the page URL: `https://notion.so/workspace/PAGE_ID?xxx`
-4. Extract the `PAGE_ID` (32-character hex string)
-
-**4.3: Add Environment Variables**
-
-**For Local Development:**
-Create `.env` in your project root:
-```bash
-NOTION_TOKEN=secret_xxxxxxxxxxxxx
-NOTION_PARENT_PAGE_ID=xxxxxxxxxxxxx
-NOTION_VERSION=2022-06-28
-```
-
-**For GitHub Actions:**
-Add as repository secrets:
-1. Go to your repo → **Settings** → **Secrets and variables** → **Actions**
-2. Click **"New repository secret"**
-3. Add:
-   - Name: `NOTION_TOKEN`, Value: `secret_xxxxx`
-   - Name: `NOTION_PARENT_PAGE_ID`, Value: `xxxxxx`
-
-### Step 4a: Set Up Confluence Integration (Optional)
-
-If using the Confluence publisher:
-
-**4a.1: Generate Confluence API Token**
-1. Go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
-2. Click **"Create API token"**
-3. Name it **"RepoLens"**
-4. Copy the generated token (save it securely - you won't see it again!)
-
-**4a.2: Find Your Space Key**
-1. Navigate to your Confluence space
-2. Go to **Space Settings** → **Space details**
-3. Note the **Space Key** (e.g., `DOCS`, `ENG`, `TECH`)
-
-**4a.3: Get Parent Page ID (Optional)**
-1. Navigate to the page where you want RepoLens docs nested
-2. Click **"..."** menu → **"Page information"**
-3. Copy the page ID from the URL: `pageId=123456789`
-4. If skipped, docs will be created at space root level
-
-**4a.4: Add Environment Variables**
-
-**For Local Development:**
-Create `.env` in your project root:
-```bash
-CONFLUENCE_URL=https://your-company.atlassian.net/wiki
-CONFLUENCE_EMAIL=your-email@example.com
-CONFLUENCE_API_TOKEN=your-api-token-here
-CONFLUENCE_SPACE_KEY=DOCS
-CONFLUENCE_PARENT_PAGE_ID=123456789  # Optional
-```
-
-**For Confluence Server/Data Center** (self-hosted):
-```bash
-CONFLUENCE_URL=https://confluence.yourcompany.com
-CONFLUENCE_EMAIL=your-username  # Use username instead of email
-CONFLUENCE_API_TOKEN=your-personal-access-token
-CONFLUENCE_SPACE_KEY=DOCS
-CONFLUENCE_PARENT_PAGE_ID=123456789  # Optional
-```
-
-**For GitHub Actions:**
-Add as repository secrets:
-1. Go to your repo → **Settings** → **Secrets and variables** → **Actions**
-2. Click **"New repository secret"**
-3. Add:
-   - Name: `CONFLUENCE_URL`, Value: `https://your-company.atlassian.net/wiki`
-   - Name: `CONFLUENCE_EMAIL`, Value: `your-email@example.com`
-   - Name: `CONFLUENCE_API_TOKEN`, Value: `your-token`
-   - Name: `CONFLUENCE_SPACE_KEY`, Value: `DOCS`
-   - Name: `CONFLUENCE_PARENT_PAGE_ID`, Value: `123456789` (optional)
-
-**Confluence + Notion + Markdown** (all three!):
-```yaml
-publishers:
-  - markdown
-  - notion
-  - confluence
-```
-
-Docs published to both Notion and Confluence for maximum visibility!
-
-### Step 5: Configure Branch Publishing (Recommended)
+## 🎓 Onboarding Guide
 
-Prevent documentation conflicts by limiting which branches publish to Notion/Confluence:
+Step-by-step setup for publishers, AI features, Notion, Confluence, GitHub Wiki, Discord, and CI/CD automation.
 
-```yaml
-notion:
-  branches:
-    - main              # Only main branch publishes
-  includeBranchInTitle: false  # Clean titles (no [branch-name] suffix)
-
-confluence:
-  branches:
-    - main              # Only main branch publishes to Confluence
-```
-
-**Options:**
-- `branches: [main]` — Only main publishes (recommended)
-- `branches: [main, staging, release/*]` — Multiple branches with glob support
-- Omit `branches` entirely — All branches publish (may cause conflicts)
-
-**Markdown publisher always runs on all branches** (local files don't conflict).
-
-### Step 6: Customize Scan Patterns (Optional)
-
-Adjust what files RepoLens scans:
-
-```yaml
-scan:
-  include:
-    - "src/**/*.{ts,tsx,js,jsx}"
-    - "app/**/*.{ts,tsx,js,jsx}"
-    - "lib/**/*.{ts,tsx,js,jsx}"
-  ignore:
-    - "node_modules/**"
-    - ".next/**"
-    - "dist/**"
-    - "build/**"
-
-module_roots:
-  - "src"
-  - "app"
-  - "lib"
-```
-
-**Performance Note:** RepoLens warns at 10k files and limits at 50k files.
-
-### Step 7: Generate Documentation
-
-Run locally to test:
-
-```bash
-npx @chappibunny/repolens publish
-```
-
-**Expected output:**
-```
-RepoLens 🔍
-────────────────────────────────────────────────────
-[RepoLens] Using config: /path/to/.repolens.yml
-[RepoLens] Loading configuration...
-[RepoLens] Scanning repository...
-[RepoLens] Detected 42 modules
-[RepoLens] Publishing documentation...
-[RepoLens] Publishing to Notion from branch: main
-[RepoLens] ✓ System Overview published
-[RepoLens] ✓ Module Catalog published
-[RepoLens] ✓ API Surface published
-[RepoLens] ✓ Route Map published
-[RepoLens] ✓ System Map published
-```
-
-### Step 8: Verify Output
-
-**Markdown Output:****
-```bash
-ls .repolens/
-# system_overview.md
-# module_catalog.md
-# api_surface.md
-# route_map.md
-# system_map.md
-# system_map.md
-```
-
-**Notion Output:**
-Open your Notion parent page and verify child pages were created:
-- 📊 RepoLens — Executive Summary (if AI enabled)
-- 📈 RepoLens — Business Domains (if AI enabled)
-- 📊 RepoLens — System Overview
-- 📚 RepoLens — Developer Onboarding (if AI enabled)
-- 📊 RepoLens — Architecture Overview (if AI enabled)
-- 📊 RepoLens — Data Flows (if AI enabled)
-- 📌 RepoLens — Module Catalog
-- 🔌 RepoLens — API Surface
-- 🗺️ RepoLens — Route Map
-- 🏛️ RepoLens — System Map
-
-### Step 9: Enable GitHub Actions (Automatic Updates)
-
-**Commit the workflow:**
-```bash
-git add .github/workflows/repolens.yml .repolens.yml
-git commit -m "Add RepoLens documentation automation"
-git push
-```
-
-**What happens next:**
-- ✅ Every push to `main` regenerates docs
-- ✅ Pull requests get architecture diff comments
-- ✅ Documentation stays evergreen automatically
-
-**Pro Tip:** Add `.repolens/` to `.gitignore` if you don't want to commit local Markdown files (Notion publisher is your source of truth).
+**[→ Full Onboarding Guide](ONBOARDING.md)**
 
 ---
 
-## 🎮 Usage Commands
-
-### Publish Documentation
-
-Auto-discovers `.repolens.yml`:
-```bash
-npx @chappibunny/repolens publish
-```
-
-Specify config path explicitly:
-```bash
-npx @chappibunny/repolens publish --config /path/to/.repolens.yml
-```
-
-Via npm script (add to package.json):
-```json
-{
-  "scripts": {
-    "docs": "repolens publish"
-  }
-}
-```
-
-### Validate Setup
-
-Check if your RepoLens setup is valid:
+## 🎮 Commands
 
-```bash
-npx @chappibunny/repolens doctor
-```
-
-Validates:
-- ✅ `.repolens.yml` exists and is valid YAML
-- ✅ Required config fields present
-- ✅ Publishers configured correctly
-- ✅ Scan patterns defined
-- ✅ Publisher configuration valid
-
-### Migrate Workflows
-
-**🚨 Upgrading from v0.3.0 or earlier?** Automatically update your GitHub Actions workflows:
-
-```bash
-npx @chappibunny/repolens migrate
-```
-
-Preview changes without applying:
-```bash
-npx @chappibunny/repolens migrate --dry-run
-```
-
-What it fixes:
-- ❌ Removes outdated `cd tools/repolens` commands
-- ✅ Updates to `npx @chappibunny/repolens@latest publish`
-- ✅ Adds Node.js setup step if missing
-- ✅ Adds environment variables (NOTION_TOKEN, REPOLENS_AI_API_KEY)
-- 💾 Creates backup files for safety
-
-**Common error it fixes:**
-```
-Run cd tools/repolens
-cd: tools/repolens: No such file or directory
-Error: Process completed with exit code 1.
-```
-
-See [MIGRATION.md](MIGRATION.md) for detailed upgrade guide.
-
-### Quick Preview (No API Keys)
-
-Generate local documentation instantly — no Notion, Confluence, or GitHub tokens needed:
-```bash
-npx @chappibunny/repolens demo
-```
-
-Works on any repo, even without a `.repolens.yml`. Output is written to `.repolens/`.
-
-### Get Help
-
-```bash
-npx @chappibunny/repolens --help
-npx @chappibunny/repolens --version
-```
-
----
+| Command | Description |
+|---|---|
+| `repolens init` | Scaffold config + GitHub Actions workflow |
+| `repolens init --interactive` | Step-by-step configuration wizard |
+| `repolens publish` | Scan, generate, and publish documentation |
+| `repolens demo` | Quick local preview — no API keys needed |
+| `repolens doctor` | Validate your setup |
+| `repolens watch` | Auto-regenerate docs on file changes |
+| `repolens migrate` | Upgrade from v0.3.0 workflows ([details](MIGRATION.md)) |
+| `repolens feedback` | Send feedback to the team |
 
 ---
 
@@ -682,13 +142,13 @@ npx @chappibunny/repolens --version
 
 ```mermaid
 graph LR
-    CLI[bin/repolens<br/>1 file] --> Core[src/core<br/>3 files]
-    Publishers[src/publishers<br/>4 files] --> Core
-    Publishers --> Renderers[src/renderers<br/>3 files]
-    Publishers --> Utils[src/utils<br/>3 files]
+    CLI[bin/repolens<br/>1 file] --> Core[src/core<br/>4 files]
+    Publishers[src/publishers<br/>6 files] --> Core
+    Publishers --> Renderers[src/renderers<br/>4 files]
+    Publishers --> Utils[src/utils<br/>10 files]
     Renderers --> Core
     Delivery[src/delivery<br/>1 file] --> Publishers
-    Tests[tests<br/>8 files] -. tests .-> CLI
+    Tests[tests<br/>15 files] -. tests .-> CLI
     Tests -. tests .-> Core
     Tests -. tests .-> Publishers
     
@@ -738,491 +198,28 @@ When you open a pull request, RepoLens posts:
 
 ---
 
-## 🔒 Privacy & Telemetry
-
-RepoLens includes **opt-in** error tracking and usage telemetry to help improve reliability, understand adoption patterns, and prioritize features.
-
-**Privacy First:**
-- ✅ **Disabled by default** - telemetry is opt-in
-- ✅ **No code collection** - your source code never leaves your machine
-- ✅ **No secrets** - API keys and tokens are never sent
-- ✅ **Anonymous** - no personal information or repository names
-- ✅ **Transparent** - see exactly what data is collected
-
-**To enable telemetry**, add to `.env`:
-```bash
-REPOLENS_TELEMETRY_ENABLED=true
-```
-
-**What's collected (when enabled):**
-
-*Error Tracking (Phase 1):*
-- Error messages and stack traces (for debugging)
-- Command that failed (e.g., `publish`, `migrate`)
-- Basic system info (Node version, platform)
-
-*Usage Metrics (Phase 2):*
-- Command execution times (scan, render, publish)
-- Repository size (file count, module count)
-- Feature usage (AI enabled, publishers used)
-- Success/failure rates
-
-**Why enable it?**
-- 🐛 **Faster bug fixes** - issues you encounter are fixed proactively
-- 📊 **Better features** - development focused on real-world usage
-- ⚡ **Performance** - optimizations based on actual bottlenecks
-- 🎯 **Prioritization** - roadmap guided by community needs
-
-For full details and example data, see [TELEMETRY.md](TELEMETRY.md).
-
----
-
-## 🛡️ Security
-
-RepoLens implements **defense-in-depth** security to protect your credentials, code, and infrastructure.
-
-### Security Architecture (Phase 3)
-
-**Layer 1: Input Validation** (`src/utils/validate.js`)
-- ✅ Schema validation with required field enforcement
-- ✅ Injection attack detection (shell, command substitution)
-- ✅ Directory traversal prevention (`..`, absolute paths, null bytes)
-- ✅ Secret scanning in configuration files
-- ✅ Circular reference protection (depth limit: 20 levels)
-
-**Layer 2: Secret Detection** (`src/utils/secrets.js`)
-- ✅ **15+ credential patterns**: OpenAI, GitHub, AWS, Notion, Generic API keys
-- ✅ **Entropy-based detection**: High-entropy strings (Shannon entropy > 4.5)
-- ✅ **Automatic sanitization**: All logger output, telemetry, error messages
-- ✅ **Format**: `sk-abc123xyz` → `sk-ab***yz` (first 2 + last 2 chars visible)
-
-**Layer 3: Rate Limiting** (`src/utils/rate-limit.js`)
-- ✅ **Token bucket algorithm**: 3 requests/second for Notion & AI APIs
-- ✅ **Exponential backoff**: Automatic retry with jitter (500ms → 1s → 2s)
-- ✅ **Cost protection**: Prevents runaway API usage
-- ✅ **Retryable errors**: 429, 500, 502, 503, 504, network timeouts
-
-**Layer 4: Supply Chain Security**
-- ✅ **Action pinning**: GitHub Actions pinned to commit SHAs (not tags)
-- ✅ **Minimal permissions**: `contents: read` or `contents: write` only
-- ✅ **Dependency audits**: CI/CD fails on critical/high vulnerabilities
-- ✅ **npm audit**: 0 vulnerabilities in 519 dependencies
-
-**Layer 5: Comprehensive Testing**
-- ✅ **43 security tests**: Fuzzing, injection, boundary conditions
-- ✅ **Attack vectors tested**: SQL, command, path, YAML, NoSQL, LDAP, XML
-- ✅ **90 total tests**: 47 functional + 43 security (100% passing)
-
-### Security Validation (Automatic)
-
-```bash
-# Every configuration load:
-✅ No injection patterns detected (;|&`$())
-✅ No secrets in configuration files
-✅ Safe path patterns only (no .. or absolute paths)
-✅ Valid schema (configVersion: 1)
-
-# Every runtime operation:
-✅ All logs sanitized (secrets redacted)
-✅ Telemetry sanitized (no credentials sent)
-✅ Rate limiting active (3 req/sec)
-✅ Type validation active (prevents type confusion)
-
-# Every CI/CD run:
-✅ npm audit passing (0 vulnerabilities)
-✅ Security tests passing (43/43)
-✅ Secrets scanner passing (no hardcoded credentials)
-```
-
-### Vulnerability Reporting
-
-- 📧 **Email**: trades@rabitaitrades.com
-- 🚨 **DO NOT** open public issues for security bugs
-- ⏱️ **Response**: Within 48 hours
-- 🔒 **Fix Timeline**: Critical issues within 7 days, others within 30 days
-- 📢 **Disclosure**: Coordinated disclosure after fix is released
-
-### Security Best Practices
-
-**✅ DO:**
-- Store secrets in GitHub Secrets (not `.repolens.yml`)
-- Use environment variables for sensitive data
-- Review generated documentation before publishing
-- Enable telemetry to catch security issues early
-- Run `npm audit` regularly
-- Pin workflows to specific versions
-
-**❌ DON'T:**
-- Commit API keys to version control
-- Share `.env` files publicly
-- Disable security validation
-- Use overly broad scan patterns (`**/*`)
-- Ignore security warnings
-
-For complete security documentation and threat model, see [SECURITY.md](SECURITY.md).
-
----
-
-## ⚙️ Configuration Reference
-
-### Complete Example
-
-```yaml
-configVersion: 1  # Schema version for future migrations
-
-project:
-  name: "my-awesome-app"
-  docs_title_prefix: "MyApp"
-
-# Configure output destinations
-publishers:
-  - notion
-  - confluence
-  - markdown
-
-# Notion-specific settings (optional)
-notion:
-  branches:
-    - main              # Only main branch publishes
-    - staging           # Also staging
-    - release/*         # Glob patterns supported
-  includeBranchInTitle: false  # Clean titles without [branch-name]
-
-# Confluence-specific settings (optional)
-confluence:
-  branches:
-    - main              # Only main branch publishes to Confluence
-
-# Discord notifications (optional, new in v0.6.0)
-discord:
-  enabled: true                  # Default: true (if DISCORD_WEBHOOK_URL set)
-  notifyOn: significant          # Options: always, significant, never
-  significantThreshold: 10       # Notify if change >10% (default)
-  branches:                      # Which branches to notify (default: all)
-    - main
-    - develop
-
-# GitHub integration (optional)
-github:
-  owner: "your-username"
-  repo: "your-repo-name"
-
-# File scanning configuration
-scan:
-  include:
-    - "src/**/*.{ts,tsx,js,jsx}"
-    - "app/**/*.{ts,tsx,js,jsx}"
-    - "pages/**/*.{ts,tsx,js,jsx}"
-    - "lib/**/*.{ts,tsx,js,jsx}"
-  ignore:
-    - "node_modules/**"
-    - ".next/**"
-    - "dist/**"
-    - "build/**"
-    - "coverage/**"
-
-# Module organization
-module_roots:
-  - "src"
-  - "app"
-  - "lib"
-  - "pages"
-
-# Documentation pages to generate
-outputs:
-  pages:
-    - key: "system_overview"
-      title: "System Overview"
-      description: "High-level snapshot and tech stack"
-    - key: "module_catalog"
-      title: "Module Catalog"
-      description: "Complete module inventory"
-    - key: "api_surface"
-      title: "API Surface"
-      description: "REST endpoints and methods"
-    - key: "route_map"
-      title: "Route Map"
-      description: "Frontend routes and pages"
-    - key: "system_map"
-      title: "System Map"
-      description: "Visual dependency graph"
-
-# Feature flags (optional, experimental)
-features:
-  architecture_diff: true
-  route_map: true
-  visual_diagrams: true
-```
-
-### Configuration Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `configVersion` | number | **Yes** | Schema version (must be `1`) |
-| `project.name` | string | Yes | Project name |
-| `project.docs_title_prefix` | string | No | Prefix for documentation titles (default: project name) |
-| `publishers` | array | Yes | Output targets: `notion`, `confluence`, `github_wiki`, `markdown` (+ plugin publishers) |
-| `plugins` | array | No | Plugin paths or npm package names |
-| `notion.branches` | array | No | Branch whitelist for Notion publishing. Supports globs. |
-| `notion.includeBranchInTitle` | boolean | No | Add `[branch-name]` to titles (default: `true`) |
-| `confluence.branches` | array | No | Branch whitelist for Confluence publishing. Supports globs. |
-| `github_wiki.branches` | array | No | Branch whitelist for GitHub Wiki publishing. Supports globs. |
-| `github_wiki.sidebar` | boolean | No | Generate `_Sidebar.md` navigation (default: `true`) |
-| `github_wiki.footer` | boolean | No | Generate `_Footer.md` (default: `true`) |
-| `discord.enabled` | boolean | No | Enable Discord notifications (default: `true` if webhook set) |
-| `discord.notifyOn` | string | No | Notification policy: `always`, `significant`, `never` (default: `significant`) |
-| `discord.significantThreshold` | number | No | Change % threshold for notifications (default: `10`) |
-| `discord.branches` | array | No | Branch filter for notifications. Supports globs. (default: all) |
-| `github.owner` | string | No | GitHub org/username |
-| `github.repo` | string | No | Repository name |
-| `scan.include` | array | Yes | Glob patterns for files to scan |
-| `scan.ignore` | array | Yes | Glob patterns to exclude |
-| `module_roots` | array | No | Root directories for module detection |
-| `outputs.pages` | array | Yes | Documentation pages to generate |
-| `features` | object | No | Feature flags (boolean values) |
-| `ai.enabled` | boolean | No | Enable AI-powered documentation |
-| `ai.mode` | string | No | AI mode: `hybrid`, `full`, or `off` |
-| `ai.temperature` | number | No | Generation temperature (0–2). Not supported by all models (e.g. gpt-5-mini ignores it) |
-| `ai.max_tokens` | number | No | Max completion tokens per request (>0) |
-
----
-
-## 🔐 Environment Variables
-
-Required for Notion publisher:
-
-| Variable | Required | Description |
-|----------|----------|-------------|
-| `NOTION_TOKEN` | Yes | Integration token from notion.so/my-integrations |
-| `NOTION_PARENT_PAGE_ID` | Yes | Page ID where docs will be created |
-| `NOTION_VERSION` | No | API version (default: `2022-06-28`) |
-
-Required for Confluence publisher:
-
-| Variable | Required | Description |
-|----------|----------|-------------|
-| `CONFLUENCE_URL` | Yes | Base URL (e.g., `https://your-company.atlassian.net/wiki`) |
-| `CONFLUENCE_EMAIL` | Yes | Atlassian account email |
-| `CONFLUENCE_API_TOKEN` | Yes | API token from [Atlassian](https://id.atlassian.com/manage-profile/security/api-tokens) |
-| `CONFLUENCE_SPACE_KEY` | Yes | Target space key (e.g., `DOCS`, `ENG`) |
-| `CONFLUENCE_PARENT_PAGE_ID` | No | Parent page ID (docs created at space root if omitted) |
-
-Optional for Discord notifications:
-
-| Variable | Required | Description |
-|----------|----------|-------------|
-| `DISCORD_WEBHOOK_URL` | No | Discord webhook URL for team notifications |
+## 🔒 Privacy & Security
 
-Required for GitHub Wiki publisher:
-
-| Variable | Required | Description |
-|----------|----------|-------------|
-| `GITHUB_TOKEN` | Yes | Personal access token or Actions `${{ secrets.GITHUB_TOKEN }}` |
-| `GITHUB_REPOSITORY` | No | `owner/repo` (auto-detected from git remote in Actions) |
-
-**Local Development:** Create `.env` file in project root  
-**GitHub Actions:** Add as repository secrets in Settings → Secrets and variables → Actions
+- **Telemetry is opt-in and disabled by default** — no code, secrets, or personal data leaves your machine. See [TELEMETRY.md](TELEMETRY.md).
+- **Defense-in-depth security** — input validation, secret detection (15+ patterns), rate limiting, injection prevention, supply chain hardening. See [SECURITY.md](SECURITY.md).
+- **Report vulnerabilities** to trades@rabitaitrades.com (not public issues). Response within 48 hours.
 
 ---
 
-## 🏗️ Architecture & Design
-
-### How RepoLens Works
-
-```
-1. SCAN           2. ANALYZE         3. RENDER           4. PUBLISH
-──────────────────────────────────────────────────────────────────
-Read files   →   Detect tech     →  Generate docs   →   Notion pages
-from patterns    stack patterns      with insights       + Confluence pages
-                                                         + Markdown files
-```
-
-**Scan Phase:**
-- Uses `fast-glob` to match your `scan.include` patterns
-- Filters out `scan.ignore` patterns
-- Reads package.json for framework/tool detection
-- Analyzes file paths for Next.js routes, API endpoints
-
-**Analyze Phase:**
-- Extracts frameworks (Next.js, React, Vue, Express, etc.)
-- Detects build tools (Vite, Webpack, Turbo, esbuild)
-- Identifies test frameworks (Vitest, Jest, Playwright)
-- Infers module relationships and dependencies
-
-**Render Phase:**
-- Groups files into modules based on `module_roots`
-- Generates Mermaid diagrams showing module dependencies
-- Creates technical profiles with actual stack insights
-- Renders Markdown documentation
-
-**Publish Phase:**
-- Markdown: Writes files to `.repolens/` directory
-- Notion: Creates/updates pages via API with retry logic
-- Confluence: Creates/updates pages via REST API v1 (storage format)
-
-### Module Dependency Detection
-
-RepoLens infers relationships by analyzing import patterns:
-
-```typescript
-// In src/publishers/notion.js
-import { renderSystemOverview } from "../renderers/render.js";
-// → Publishers depend on Renderers
-
-// In src/renderers/render.js  
-import { scanRepo } from "../core/scan.js";
-// → Renderers depend on Core
-
-// Result: Dependency graph shows Publishers → Renderers → Core
-```
-
----
-
----
-
-## 🧪 Development
-
-### Setup
-
-```bash
-git clone https://github.com/CHAPIBUNNY/repolens.git
-cd repolens
-npm install
-npm link  # Makes 'repolens' command available globally
-```
-
-### Run Tests
-
-```bash
-npm test
-```
-
-**Test Suite:**
-- Config discovery and validation
-- Branch detection (GitHub/GitLab/CircleCI)
-- Markdown publisher
-- Integration workflows
-- Doctor command validation
-
-**Coverage:** 180 tests passing across 15 test files
-
-### Test Package Installation Locally
-
-Simulates the full user installation experience:
-
-```bash
-# Pack the tarball
-npm pack
-
-# Install globally from tarball
-npm install -g chappibunny-repolens-1.3.0.tgz
-
-# Verify
-repolens --version
-```
-
-### Project Structure
-
-```
-repolens/
-├── bin/
-│   └── repolens.js          # CLI executable wrapper
-├── src/
-│   ├── cli.js               # Command orchestration + banner
-│   ├── init.js              # Scaffolding command (+ interactive wizard)
-│   ├── doctor.js            # Validation command
-│   ├── migrate.js           # Workflow migration (legacy → current)
-│   ├── watch.js             # Watch mode for local development
-│   ├── core/
-│   │   ├── config.js        # Config loading + validation
-│   │   ├── config-schema.js # Schema version tracking
-│   │   ├── diff.js          # Git diff operations
-│   │   └── scan.js          # Repository scanning + metadata extraction
-│   ├── analyzers/
-│   │   ├── domain-inference.js    # Business domain mapping
-│   │   ├── context-builder.js     # Structured AI context assembly
-│   │   ├── flow-inference.js      # Data flow detection
-│   │   ├── graphql-analyzer.js    # GraphQL schema detection
-│   │   ├── typescript-analyzer.js # TypeScript type graph analysis
-│   │   ├── dependency-graph.js    # Import graph with cycle detection
-│   │   └── drift-detector.js      # Architecture drift detection
-│   ├── ai/
-│   │   ├── provider.js          # Provider-agnostic AI generation
-│   │   ├── prompts.js           # Strict prompt templates
-│   │   ├── document-plan.js     # Document structure definition
-│   │   └── generate-sections.js # AI section generation + fallbacks
-│   ├── docs/
-│   │   ├── generate-doc-set.js  # Document generation orchestration
-│   │   └── write-doc-set.js     # Write docs to disk
-│   ├── renderers/
-│   │   ├── render.js           # System overview, catalog, API, routes
-│   │   ├── renderDiff.js       # Architecture diff rendering
-│   │   ├── renderMap.js        # Unicode dependency diagrams
-│   │   └── renderAnalysis.js   # Extended analysis renderers
-│   ├── publishers/
-│   │   ├── index.js         # Publisher orchestration + branch filtering
-│   │   ├── publish.js       # Publishing pipeline
-│   │   ├── notion.js        # Notion API integration
-│   │   ├── confluence.js    # Confluence REST API integration
-│   │   ├── github-wiki.js   # GitHub Wiki publisher (git-based)
-│   │   └── markdown.js      # Local Markdown generation
-│   ├── integrations/
-│   │   └── discord.js       # Discord webhook notifications
-│   ├── delivery/
-│   │   └── comment.js       # PR comment delivery
-│   ├── plugins/
-│   │   ├── loader.js        # Plugin resolution and dynamic import
-│   │   └── manager.js       # Plugin registry and lifecycle orchestration
-│   └── utils/
-│       ├── logger.js        # Logging utilities
-│       ├── retry.js         # API retry logic (exponential backoff)
-│       ├── branch.js        # Branch detection (multi-platform)
-│       ├── validate.js      # Configuration validation & security
-│       ├── metrics.js       # Documentation coverage & health scoring
-│       ├── rate-limit.js    # Token bucket rate limiter for APIs
-│       ├── secrets.js       # Secret detection & sanitization
-│       ├── telemetry.js     # Opt-in error tracking + performance timers
-│       ├── errors.js        # Enhanced error messages with guidance
-│       └── update-check.js  # Version update notifications
-├── tests/                   # Vitest test suite (180 tests across 15 files)
-├── .repolens.yml            # Dogfooding config
-├── package.json
-├── CHANGELOG.md
-├── STABILITY.md
-├── RELEASE.md
-└── ROADMAP.md
-```
-
----
-
-## 🚀 Release Process
-
-RepoLens uses automated GitHub Actions releases.
-
-### Creating a Release
-
-```bash
-# Patch version (1.0.0 → 1.0.1) - Bug fixes
-npm run release:patch
-
-# Minor version (1.0.0 → 1.1.0) - New features
-npm run release:minor
-
-# Major version (1.0.0 → 2.0.0) - Breaking changes
-npm run release:major
-
-# Push the tag to trigger workflow
-git push --follow-tags
-```
-
-**What happens:**
-1. ✅ Security audit runs (dependency audit + secret scanning)
-2. ✅ All tests run
-3. ✅ Package tarball created
-4. ✅ GitHub Release published with tarball attached
-5. ✅ npm package published to `@chappibunny/repolens`
-
-See [RELEASE.md](./RELEASE.md) for detailed workflow.
+## 📚 Documentation
+
+| Guide | Description |
+|---|---|
+| [Onboarding Guide](ONBOARDING.md) | Step-by-step setup: publishers, AI, Notion, Confluence, Discord |
+| [Configuration](CONFIGURATION.md) | Complete `.repolens.yml` schema and examples |
+| [Environment Variables](ENVIRONMENT.md) | All env vars by publisher and feature |
+| [Architecture](ARCHITECTURE.md) | Pipeline diagram, project structure |
+| [Development](DEVELOPMENT.md) | Setup, tests (185 across 15 files), release process |
+| [Security](SECURITY.md) | Threat model, secret detection, validation layers |
+| [Telemetry](TELEMETRY.md) | Opt-in privacy-first usage analytics |
+| [Troubleshooting](TROUBLESHOOTING.md) | Common issues and fixes |
+| [Migration](MIGRATION.md) | Upgrading from v0.3.0 or earlier |
+| [Stability](STABILITY.md) | API contract and semver guarantees |
 
 ---
 
@@ -1239,50 +236,14 @@ See [RELEASE.md](./RELEASE.md) for detailed workflow.
 
 ## 🗺️ Roadmap
 
-**Current Status:** v1.3.0 — Stable Release
-
-### v1.0 — Complete ✅
-
-- [x] CLI commands: `init`, `doctor`, `publish`, `demo`, `migrate`, `watch`, `feedback`, `version`, `help`
-- [x] Config schema v1 with validation (frozen)
-- [x] Auto-discovery of `.repolens.yml`
-- [x] Publishers: Notion + Confluence + GitHub Wiki + Markdown
-- [x] Branch-aware publishing with filtering
-- [x] Smart tech stack detection from package.json
-- [x] Unicode dependency diagrams (no external deps)
-- [x] AI-assisted documentation intelligence (provider-agnostic)
-- [x] Business domain inference & data flow analysis
-- [x] GitHub Actions automation (publish + release)
-- [x] PR architecture diff comments
-- [x] Performance guardrails (10k warning, 50k limit)
-- [x] Comprehensive test suite (180 tests across 15 files)
-- [x] Security hardening (secret detection, injection prevention, fuzzing)
-- [x] Discord notifications with rich embeds
-- [x] Documentation coverage & health scoring
-- [x] Opt-in telemetry (Sentry)
-- [x] npm registry publication (`@chappibunny/repolens`)
-- [x] Automated npm releases via GitHub Actions
-- [x] Workflow migration command (`repolens migrate`)
-- [x] Interactive configuration wizard (`repolens init --interactive`)
-- [x] Watch mode for local development (`repolens watch`)
-- [x] Enhanced error messages with actionable guidance
-- [x] Performance monitoring (scan/render/publish timing)
-- [x] Improved documentation coverage scoring
-- [x] GraphQL schema detection (queries, mutations, types, resolvers)
-- [x] TypeScript type graph analysis (interfaces, classes, relationships)
-- [x] Dependency graph with circular dependency detection
-- [x] Architecture drift detection (baseline comparison)
-- [x] Plugin system for custom renderers and publishers
-- [x] Stability audit: CLI, config schema, and plugin interface frozen
-- [x] [STABILITY.md](STABILITY.md): Public API contract with semver guarantees
-
-### Future
-
-- [ ] Additional publishers (Obsidian)
+v1.0+ features complete — CLI, config schema, and plugin interface are frozen.
+
+**Next:**
+- [ ] Obsidian publisher
 - [ ] VS Code extension
 - [ ] GitHub App
 
-See [ROADMAP.md](./ROADMAP.md) for detailed planning.
+See [ROADMAP.md](ROADMAP.md) for detailed planning.
 
 ---
 

package/RELEASE.md

@@ -22,7 +22,7 @@ RepoLens uses semantic versioning:
 8. Push branch and tag: `git push --follow-tags`
 9. GitHub Actions `release.yml` runs automatically:
    - Security audit (dependency + secrets scanning)
-   - Test suite (163 tests)
+   - Test suite (185 tests)
    - Create GitHub Release with tarball
    - Publish to npm (`npm publish --access public`)
 10. Verify on npm: `npm view @chappibunny/repolens version`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chappibunny/repolens",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "AI-assisted documentation intelligence system for technical and non-technical audiences",
   "license": "MIT",
   "type": "module",