@chappibunny/repolens 0.6.0 → 0.6.3

package/CHANGELOG.md

@@ -2,84 +2,72 @@
 
 All notable changes to RepoLens will be documented in this file.
 
-## 0.6.0 (Phase 4: Team Features & Observability Dashboard)
+## 0.6.3
 
 ### ✨ New Features
+- **User Feedback**: Added `repolens feedback` CLI command for sending feedback directly to the RepoLens team via Sentry
+  - Interactive prompts for name, email, and message
+  - Works even when telemetry is disabled — feedback is always accepted
+  - Uses `Sentry.captureFeedback()` from `@sentry/node`
 
-**Discord Integration** (`src/integrations/discord.js` - 268 lines):
+### 🔧 Maintenance
+- Updated version references across all documentation
+- Added `feedback` to CLI help and command listings
+
+## 0.6.2
+
+### 🐛 Bug Fixes
+- **CI/CD**: Fixed release workflow failing with `Cannot find module @rollup/rollup-linux-x64-gnu`
+  - Root cause: macOS-generated `package-lock.json` doesn't resolve Linux platform-specific optional dependencies
+  - Fix: Changed all CI install steps to `rm -rf node_modules package-lock.json && npm install`
+  - Applied to both `publish-docs.yml` and `release.yml` workflows
+
+### 🔧 Maintenance
+- Updated version references across codebase
+- Updated test assertions for version 0.6.2
+
+## 0.6.1
+
+### 🐛 Bug Fixes
+- **Confluence Publisher**: Fixed `version` showing as `[object Object]1`
+  - Root cause: `existingPage.version` was the full version object, not just the number
+  - Fix: Normalize version to use cached structure with extracted version number
+- **Confluence Publisher**: Fixed code block formatting in storage format
+  - Implemented 3-step extract→convert→restore pipeline
+  - Properly handles fenced code blocks in Markdown→Confluence conversion
+
+### 📦 Package
+- Renamed npm package from `@rabitai/repolens` to `@chappibunny/repolens`
+- Updated all references across codebase, workflows, and documentation
+- Published to npm registry under new scope
+
+## 0.6.0 (Team Features & Observability)
+
+### ✨ New Features
+
+**Discord Integration** (`src/integrations/discord.js`):
 - Rich embed notifications with coverage, health score, and change metrics
 - Threshold-based notifications (default: >10% change)
 - Branch filtering with glob pattern support
 - Secure webhook configuration via `DISCORD_WEBHOOK_URL` environment variable
-- Functions: `sendDiscordNotification()`, `buildDocUpdateNotification()`, `buildErrorNotification()`, `shouldNotify()`
 - Color-coded embeds: success (green), warning (yellow), error (red), info (blue)
 
-**Metrics Collection System** (`src/utils/metrics.js` - 412 lines):
-- **Coverage Calculation**: Weighted average (modules 50%, APIs 30%, pages 20%)
-- **Health Score Algorithm**: 0-100 rating (40% coverage + 30% freshness + 30% quality)
-- **Staleness Detection**: Flags documentation >90 days old
-- **Quality Analysis**: Identifies undocumented modules/APIs/pages with severity levels
-- **Historical Tracking**: Persists metrics to `.repolens/metrics-history.json`
-- **Trend Indicators**: Up/down/stable trend detection (>1% threshold)
-- Functions: `calculateCoverage()`, `calculateHealthScore()`, `detectStaleness()`, `analyzeQuality()`, `trackMetrics()`, `calculateTrends()`, `collectMetrics()`
-
-**Interactive Dashboard** (`src/renderers/renderDashboard.js` - 1,020 lines):
-- Beautiful HTML dashboard with inline CSS (zero dependencies)
-- **Health Score Card**: Color-coded 0-100 score (excellent/good/fair/poor)
-- **Coverage Breakdown**: Module/API/page coverage with progress bars
-- **Freshness Tracking**: Stale file detection with last updated timestamps
-- **Quality Issues List**: Severity badges (high/medium/low) with actionable items
-- **Trend Charts**: SVG visualization of coverage and health score over time
-- **Quick Links**: Direct links to Notion, GitHub, and Markdown documentation
-- Responsive design with animations and smooth transitions
-- Generated at `.repolens/dashboard/index.html`
-
-**GitHub Pages Deployment** (`.github/workflows/deploy-dashboard.yml` - 73 lines):
-- Automated deployment to `https://OWNER.github.io/REPO/`
-- Deploys on every push to main branch
-- Uses local code during development (`npm link`)
-- Graceful fallback for missing dashboard files
-- Security-conscious environment variable handling
+**Metrics Collection System** (`src/utils/metrics.js`):
+- Coverage calculation: weighted average (modules 50%, APIs 30%, pages 20%)
+- Health score algorithm: 0-100 rating (40% coverage + 30% freshness + 30% quality)
+- Staleness detection: flags documentation >90 days old
+- Quality analysis: identifies undocumented modules/APIs/pages with severity levels
+- Historical tracking: persists metrics to `.repolens/metrics-history.json`
+- Trend indicators: up/down/stable trend detection (>1% threshold)
 
 **Configuration Extensions** (`src/core/config-schema.js`):
-- **Discord Configuration**:
-  * `discord.notifyOn`: "always", "significant", or "never"
-  * `discord.significantThreshold`: 0-100 (default: 10%)
-  * `discord.branches`: Array with glob pattern support
-  * `discord.enabled`: Boolean
-- **Dashboard Configuration**:
-  * `dashboard.enabled`: Boolean (default: true)
-  * `dashboard.githubPages`: Boolean
-  * `dashboard.staleThreshold`: Number (default: 90 days)
+- Discord configuration: `discord.notifyOn`, `discord.significantThreshold`, `discord.branches`, `discord.enabled`
 
 **Publishing Integration** (`src/publishers/index.js`):
 - Automatic metrics collection after publishing
-- Dashboard generation integrated into publish flow
 - Discord notifications sent after successful publish (if configured)
 - Branch-aware notification filtering
-- Graceful error handling (doesn't fail publish if dashboard/notifications fail)
-
-### 🔧 Configuration
-
-**Environment Variables** (`.env.example`):
-- Added `DISCORD_WEBHOOK_URL` for team notifications
-- Security warnings and setup instructions
-- GitHub Actions secret configuration guidance
-
-**GitHub Actions** (`.github/workflows/publish-docs.yml`):
-- Added `DISCORD_WEBHOOK_URL` to workflow environment
-
-### 📊 Testing
-- All 90 tests passing (47 main + 43 security)
-- No regressions from Phase 4 integration
-- Metrics algorithms validated
-- Dashboard generation tested
-
-### 🐛 Bug Fixes
-- **GitHub Pages Workflow**: Fixed deployment to use local code during development
-  * Changed from `npx @chappibunny/repolens@latest` to `npm link && npx repolens`
-  * Added file existence checks before copying dashboard
-  * Created graceful fallback with "Coming Soon" placeholder for missing files
+- Graceful error handling (doesn't fail publish if notifications fail)
 
 ## 0.5.0 (Phase 3: Security Audit)
 

package/README.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="Avatar.png" alt="RepoLens" width="120" />
+</p>
+
 ```
     ██████╗ ███████╗██████╗  ██████╗ ██╗     ███████╗███╗   ██╗███████╗
     ██╔══██╗██╔════╝██╔══██╗██╔═══██╗██║     ██╔════╝████╗  ██║██╔════╝
@@ -16,7 +20,7 @@
 
 AI-assisted documentation intelligence system that generates architecture docs for engineers AND readable system docs for stakeholders
 
-**Current Status**: v0.6.0 — Team Features & Observability Dashboard
+**Current Status**: v0.6.3 — Sentry User Feedback & Team Features
 
 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.
 
@@ -49,7 +53,7 @@ For Confluence:
 ```bash
 # Edit .env and add:
 CONFLUENCE_URL=https://your-company.atlassian.net/wiki
-CONFLUENCE_EMAIL=your@email.com
+CONFLUENCE_EMAIL=trades@rabitaitrades.com
 CONFLUENCE_API_TOKEN=your-token
 CONFLUENCE_SPACE_KEY=DOCS
 ```
@@ -128,56 +132,11 @@ RepoLens automatically detects:
 ✅ **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)  
-✅ **Observability Dashboard** - Interactive HTML metrics dashboard (NEW in v0.6.0)  
 ✅ **Health Score Tracking** - Monitor documentation quality over time (NEW in v0.6.0)  
-✅ **GitHub Pages Deployment** - Automated public dashboard hosting (NEW in v0.6.0)  
 
 ---
 
-## 👥 Team Features & Observability (New in v0.6.0)
-
-### 📊 Interactive Dashboard
-
-RepoLens now generates a beautiful HTML dashboard with real-time metrics and trends:
-
-**Features:**
-- **Health Score** — 0-100 rating based on coverage, freshness, and quality
-- **Coverage Metrics** — Module, API, and page documentation coverage with progress bars
-- **Freshness Tracking** — Identifies stale documentation (>90 days old)
-- **Quality Issues** — Lists undocumented modules, APIs, and pages with severity badges
-- **Trend Charts** — SVG visualization of coverage and health score over time
-- **Quick Links** — Direct links to Notion, GitHub, and Markdown documentation
-
-**Access your dashboard:**
-- **Local**: `.repolens/dashboard/index.html` after running `repolens publish`
-- **Public**: `https://OWNER.github.io/REPO/` (with GitHub Pages enabled)
-
-**Setup GitHub Pages (Optional):**
-
-1. **Add workflow** (created by `repolens init` in v0.6.0+):
-   - File: `.github/workflows/deploy-dashboard.yml`
-   - Triggers: Runs on every push to main
-
-2. **Enable GitHub Pages**:
-   - Go to repo Settings → Pages
-   - Source: **GitHub Actions**
-   - Save
-
-3. **Add secrets** (if using publishers or notifications):
-   ```
-   NOTION_TOKEN
-   NOTION_PARENT_PAGE_ID
-   CONFLUENCE_URL
-   CONFLUENCE_EMAIL
-   CONFLUENCE_API_TOKEN
-   CONFLUENCE_SPACE_KEY
-   CONFLUENCE_PARENT_PAGE_ID  # Optional
-   DISCORD_WEBHOOK_URL  # Optional
-   ```
-   DISCORD_WEBHOOK_URL
-   ```
-
-Your dashboard will be live at `https://OWNER.github.io/REPO/` within minutes!
+## 👥 Team Features (New in v0.6.0)
 
 ### 💬 Discord Notifications
 
@@ -221,7 +180,7 @@ Get notified when documentation changes significantly:
 - Files scanned and modules analyzed
 - Coverage percentage and health score
 - Change percentage from previous run
-- Direct links to dashboard, Notion, and GitHub
+- Direct links to Notion and GitHub documentation
 
 ---
 
@@ -233,7 +192,7 @@ Get notified when documentation changes significantly:
 npm install @chappibunny/repolens
 ```
 
-Installs from npm registry. ✨ **Now available in beta!**
+Installs from npm registry.
 
 ### Alternative Methods
 
@@ -265,7 +224,7 @@ npm link
 Install from a specific version:
 
 ```bash
-npm install https://github.com/CHAPIBUNNY/repolens/releases/download/v0.2.0/repolens-0.2.0.tgz
+npm install https://github.com/CHAPIBUNNY/repolens/releases/download/v0.6.3/chappibunny-repolens-0.6.3.tgz
 ```
 </details>
 
@@ -465,7 +424,7 @@ If using the Confluence publisher:
 Create `.env` in your project root:
 ```bash
 CONFLUENCE_URL=https://your-company.atlassian.net/wiki
-CONFLUENCE_EMAIL=your@email.com
+CONFLUENCE_EMAIL=trades@rabitaitrades.com
 CONFLUENCE_API_TOKEN=your-api-token-here
 CONFLUENCE_SPACE_KEY=DOCS
 CONFLUENCE_PARENT_PAGE_ID=123456789  # Optional
@@ -486,7 +445,7 @@ Add as repository secrets:
 2. Click **"New repository secret"**
 3. Add:
    - Name: `CONFLUENCE_URL`, Value: `https://your-company.atlassian.net/wiki`
-   - Name: `CONFLUENCE_EMAIL`, Value: `your@email.com`
+   - Name: `CONFLUENCE_EMAIL`, Value: `trades@rabitaitrades.com`
    - Name: `CONFLUENCE_API_TOKEN`, Value: `your-token`
    - Name: `CONFLUENCE_SPACE_KEY`, Value: `DOCS`
    - Name: `CONFLUENCE_PARENT_PAGE_ID`, Value: `123456789` (optional)
@@ -557,7 +516,7 @@ npx @chappibunny/repolens publish
 
 **Expected output:**
 ```
-RABITAI 🐰
+RepoLens 🔍
 ────────────────────────────────────────────────────
 [RepoLens] Using config: /path/to/.repolens.yml
 [RepoLens] Loading configuration...
@@ -582,7 +541,7 @@ ls .repolens/
 # api_surface.md
 # route_map.md
 # system_map.md
-# diagrams/system_map.svg
+# system_map.md
 ```
 
 **Notion Output:**
@@ -652,7 +611,7 @@ Validates:
 - ✅ Required config fields present
 - ✅ Publishers configured correctly
 - ✅ Scan patterns defined
-- ✅ Mermaid CLI installation status
+- ✅ Publisher configuration valid
 
 ### Migrate Workflows
 
@@ -854,7 +813,7 @@ RepoLens implements **defense-in-depth** security to protect your credentials, c
 
 ### Vulnerability Reporting
 
-- 📧 **Email**: [your-email@example.com] (replace with actual contact)
+- 📧 **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
@@ -895,6 +854,7 @@ project:
 # Configure output destinations
 publishers:
   - notion
+  - confluence
   - markdown
 
 # Notion-specific settings (optional)
@@ -905,6 +865,11 @@ notion:
     - 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)
@@ -914,12 +879,6 @@ discord:
     - main
     - develop
 
-# Observability dashboard (optional, new in v0.6.0)
-dashboard:
-  enabled: true                  # Default: true
-  githubPages: true             # Deploy to GitHub Pages
-  staleThreshold: 90            # Flag docs older than 90 days
-
 # GitHub integration (optional)
 github:
   owner: "your-username"
@@ -979,18 +938,16 @@ features:
 | `configVersion` | number | No | Schema version (current: 1) for future migrations |
 | `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`, `markdown` |
+| `publishers` | array | Yes | Output targets: `notion`, `confluence`, `markdown` |
 | `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. |
 | `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) |
-| `dashboard.enabled` | boolean | No | Generate HTML dashboard (default: `true`) |
-| `dashboard.githubPages` | boolean | No | Deploy to GitHub Pages (default: `false`) |
-| `dashboard.staleThreshold` | number | No | Days before docs flagged as stale (default: `90`) |
-| `github.owner` | string | No | GitHub org/username for SVG hosting |
-| `github.repo` | string | No | Repository name for SVG hosting |
+| `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 |
@@ -1009,7 +966,17 @@ Required for Notion publisher:
 | `NOTION_PARENT_PAGE_ID` | Yes | Page ID where docs will be created |
 | `NOTION_VERSION` | No | API version (default: `2022-06-28`) |
 
-Optional for Discord notifications (new in v0.6.0):
+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 |
 |----------|----------|-------------|
@@ -1028,8 +995,8 @@ Optional for Discord notifications (new in v0.6.0):
 1. SCAN           2. ANALYZE         3. RENDER           4. PUBLISH
 ──────────────────────────────────────────────────────────────────
 Read files   →   Detect tech     →  Generate docs   →   Notion pages
-from patterns    stack patterns      with insights       + Markdown files
-                                                         + SVG diagrams
+from patterns    stack patterns      with insights       + Confluence pages
+                                                         + Markdown files
 ```
 
 **Scan Phase:**
@@ -1053,8 +1020,7 @@ from patterns    stack patterns      with insights       + Markdown files
 **Publish Phase:**
 - Markdown: Writes files to `.repolens/` directory
 - Notion: Creates/updates pages via API with retry logic
-- SVG: Generates diagrams with optional mermaid-cli
-- Git: Commits diagrams back to repo for GitHub CDN hosting
+- Confluence: Creates/updates pages via REST API v1 (storage format)
 
 ### Module Dependency Detection
 
@@ -1100,7 +1066,7 @@ npm test
 - Integration workflows
 - Doctor command validation
 
-**Coverage:** 32 tests passing
+**Coverage:** 90 tests passing across 11 test files
 
 ### Test Package Installation Locally
 
@@ -1111,7 +1077,7 @@ Simulates the full user installation experience:
 npm pack
 
 # Install globally from tarball
-npm install -g repolens-0.2.0.tgz
+npm install -g chappibunny-repolens-0.6.3.tgz
 
 # Verify
 repolens --version
@@ -1127,28 +1093,49 @@ repolens/
 │   ├── cli.js               # Command orchestration + banner
 │   ├── init.js              # Scaffolding command
 │   ├── doctor.js            # Validation command
+│   ├── migrate.js           # Workflow migration (legacy → current)
 │   ├── 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
+│   ├── 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     # Mermaid dependency graphs
+│   │   └── renderMap.js     # Unicode dependency diagrams
 │   ├── publishers/
 │   │   ├── index.js         # Publisher orchestration + branch filtering
-│   │   ├── publish.js       # Notion publishing pipeline
+│   │   ├── publish.js       # Publishing pipeline
 │   │   ├── notion.js        # Notion API integration
+│   │   ├── confluence.js    # Confluence REST API integration
 │   │   └── markdown.js      # Local Markdown generation
+│   ├── integrations/
+│   │   └── discord.js       # Discord webhook notifications
 │   ├── delivery/
 │   │   └── comment.js       # PR comment delivery
 │   └── utils/
 │       ├── logger.js        # Logging utilities
-│       ├── retry.js         # API retry logic
+│       ├── retry.js         # API retry logic (exponential backoff)
 │       ├── branch.js        # Branch detection (multi-platform)
-│       └── mermaid.js       # SVG rendering + GitHub URL handling
-├── tests/                   # Vitest test suite
+│       ├── 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 (Sentry)
+│       └── update-check.js  # Version update notifications
+├── tests/                   # Vitest test suite (90 tests across 11 files)
 ├── .repolens.yml            # Dogfooding config
 ├── package.json
 ├── CHANGELOG.md
@@ -1165,13 +1152,13 @@ RepoLens uses automated GitHub Actions releases.
 ### Creating a Release
 
 ```bash
-# Patch version (0.2.0 → 0.2.1) - Bug fixes
+# Patch version (0.6.3 → 0.6.4) - Bug fixes
 npm run release:patch
 
-# Minor version (0.2.0 → 0.3.0) - New features
+# Minor version (0.6.3 → 0.7.0) - New features
 npm run release:minor
 
-# Major version (0.2.0 → 1.0.0) - Breaking changes
+# Major version (0.6.3 → 1.0.0) - Breaking changes
 npm run release:major
 
 # Push the tag to trigger workflow
@@ -1179,10 +1166,11 @@ git push --follow-tags
 ```
 
 **What happens:**
-1. ✅ All tests run
-2. ✅ Package tarball created
-3. ✅ GitHub Release published
-4. ✅ Tarball attached as artifact
+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.
 
@@ -1202,30 +1190,30 @@ RepoLens is currently in early access. v1.0 will open for community contribution
 
 ## 🗺️ Roadmap to v1.0
 
-**Current Status:** v0.2.0 — ~92% production-ready
+**Current Status:** v0.6.3 — Sentry User Feedback & Team Features
 
 ### Completed ✅
 
-- [x] CLI commands: `init`, `doctor`, `publish`, `version`, `help`
+- [x] CLI commands: `init`, `doctor`, `publish`, `migrate`, `feedback`, `version`, `help`
 - [x] Config schema v1 with validation
 - [x] Auto-discovery of `.repolens.yml`
-- [x] Publishers: Notion + Markdown
+- [x] Publishers: Notion + Confluence + Markdown
 - [x] Branch-aware publishing with filtering
 - [x] Smart tech stack detection from package.json
-- [x] Dependency graphs with actual module relationships
-- [x] Visual diagrams with optional SVG rendering
-- [x] GitHub Actions automation
+- [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 (32 tests)
-- [x] Interactive mermaid-cli installation
-
-### In Progress 🚧
-
-- [ ] Production stability validation
-- [ ] Enhanced error messages and debugging
-- [ ] Performance optimization for large repos
-- [ ] Additional framework detection (Remix, SvelteKit, Astro)
+- [x] Comprehensive test suite (90 tests across 11 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`)
 
 ### Planned for v1.0 🎯
 
@@ -1234,7 +1222,7 @@ RepoLens is currently in early access. v1.0 will open for community contribution
 - [ ] TypeScript type graph analysis
 - [ ] Interactive configuration wizard
 - [ ] Watch mode for local development
-- [ ] npm registry publication
+- [ ] Additional publishers (GitHub Wiki, Obsidian)
 
 See [ROADMAP.md](./ROADMAP.md) for detailed planning.
 
@@ -1256,6 +1244,6 @@ MIT
 
 <div align="center">
 
-**Made with RABITAI for developers who care about architecture**
+**Made with ❤️ by RepoLens for developers who care about architecture**
 
 </div>

package/RELEASE.md

@@ -4,9 +4,9 @@
 
 RepoLens uses semantic versioning:
 
-- Patch: bug fixes, internal cleanup, non-breaking improvements
-- Minor: new features, new commands, new publishers
-- Major: breaking CLI or config changes
+- **Patch**: bug fixes, internal cleanup, non-breaking improvements
+- **Minor**: new features, new commands, new publishers
+- **Major**: breaking CLI or config changes
 
 ## Release Checklist
 
@@ -18,14 +18,19 @@ RepoLens uses semantic versioning:
 4. Update `CHANGELOG.md`
 5. Bump version in `package.json`
 6. Commit release changes
-7. Tag the release
-8. Push branch and tag
-9. CI validates package installation automatically
+7. Tag the release: `git tag v<version>`
+8. Push branch and tag: `git push --follow-tags`
+9. GitHub Actions `release.yml` runs automatically:
+   - Security audit (dependency + secrets scanning)
+   - Test suite (90 tests)
+   - Create GitHub Release with tarball
+   - Publish to npm (`npm publish --access public`)
+10. Verify on npm: `npm view @chappibunny/repolens version`
 
 ## Example Patch Release
 
 ```bash
-# 1. Update version
+# 1. Bump version + create tag
 npm run release:patch  # or :minor, :major
 
 # 2. Run tests
@@ -34,13 +39,32 @@ npm test
 # 3. Test installation
 npm run test:install
 
-# 4. Push release
+# 4. Push release (triggers release.yml workflow)
 git push --follow-tags
 
 # 5. Verify GitHub Actions
 # Check: https://github.com/CHAPIBUNNY/repolens/actions
+
+# 6. Verify npm publish
+npm view @chappibunny/repolens version
 ```
 
+## CI/CD Notes
+
+### Important: CI Install Strategy
+
+GitHub Actions workflows use `rm -rf node_modules package-lock.json && npm install` instead of `npm ci`. This is because a macOS-generated `package-lock.json` doesn't properly resolve Linux platform-specific optional dependencies (e.g., `@rollup/rollup-linux-x64-gnu` required by Vitest).
+
+- **Do NOT** use `npm ci` in CI workflows
+- **Do NOT** commit `package-lock.json` changes made on CI runners back to the repo
+- Always delete both `node_modules` and `package-lock.json` before install in CI
+
+### npm Publishing
+
+The `release.yml` workflow publishes to npm automatically when a `v*` tag is pushed. It requires:
+- `NPM_TOKEN` secret set in GitHub repository settings
+- Token must have publish access to `@chappibunny` scope
+
 ## Testing Upgrade Path
 
 To test that users can upgrade successfully:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chappibunny/repolens",
-  "version": "0.6.0",
+  "version": "0.6.3",
   "description": "AI-assisted documentation intelligence system for technical and non-technical audiences",
   "license": "MIT",
   "type": "module",
@@ -22,15 +22,15 @@
     "architecture",
     "github",
     "notion",
+    "confluence",
     "markdown",
     "developer-tools",
-    "rabitai",
     "repolens",
     "observability",
-    "dashboard",
     "metrics",
     "team-collaboration",
-    "discord"
+    "discord",
+    "ai-documentation"
   ],
   "repository": {
     "type": "git",