@chappibunny/repolens 0.6.2 → 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

@@ -20,7 +20,7 @@
 
 AI-assisted documentation intelligence system that generates architecture docs for engineers AND readable system docs for stakeholders
 
-**Current Status**: v0.6.1 — Confluence Publisher & Team Features
+**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.
 
@@ -224,7 +224,7 @@ npm link
 Install from a specific version:
 
 ```bash
-npm install https://github.com/CHAPIBUNNY/repolens/releases/download/v0.6.1/chappibunny-repolens-0.6.1.tgz
+npm install https://github.com/CHAPIBUNNY/repolens/releases/download/v0.6.3/chappibunny-repolens-0.6.3.tgz
 ```
 </details>
 
@@ -1077,7 +1077,7 @@ Simulates the full user installation experience:
 npm pack
 
 # Install globally from tarball
-npm install -g chappibunny-repolens-0.6.1.tgz
+npm install -g chappibunny-repolens-0.6.3.tgz
 
 # Verify
 repolens --version
@@ -1152,13 +1152,13 @@ RepoLens uses automated GitHub Actions releases.
 ### Creating a Release
 
 ```bash
-# Patch version (0.6.1 → 0.6.2) - Bug fixes
+# Patch version (0.6.3 → 0.6.4) - Bug fixes
 npm run release:patch
 
-# Minor version (0.6.1 → 0.7.0) - New features
+# Minor version (0.6.3 → 0.7.0) - New features
 npm run release:minor
 
-# Major version (0.6.1 → 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
@@ -1190,11 +1190,11 @@ RepoLens is currently in early access. v1.0 will open for community contribution
 
 ## 🗺️ Roadmap to v1.0
 
-**Current Status:** v0.6.1 — Confluence Publisher & Team Features
+**Current Status:** v0.6.3 — Sentry User Feedback & Team Features
 
 ### Completed ✅
 
-- [x] CLI commands: `init`, `doctor`, `publish`, `migrate`, `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 + Confluence + Markdown

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.2",
+  "version": "0.6.3",
   "description": "AI-assisted documentation intelligence system for technical and non-technical audiences",
   "license": "MIT",
   "type": "module",

package/src/cli.js

@@ -31,8 +31,10 @@ import {
   closeTelemetry,
   trackUsage,
   startTimer,
-  stopTimer
+  stopTimer,
+  sendFeedback
 } from "./utils/telemetry.js";
+import { createInterface } from "node:readline";
 
 async function getPackageVersion() {
   const __filename = fileURLToPath(import.meta.url);
@@ -109,6 +111,7 @@ Commands:
   doctor      Validate your RepoLens setup
   migrate     Upgrade workflow files to v0.4.0 format
   publish     Scan, render, and publish documentation
+  feedback    Send feedback to the RepoLens team
   version     Print the current RepoLens version
 
 Options:
@@ -341,8 +344,51 @@ async function main() {
     return;
   }
 
+  if (command === "feedback") {
+    await printBanner();
+    info("Send feedback to the RepoLens team");
+    info("Your feedback is anonymous and helps us improve RepoLens.\n");
+
+    const rl = createInterface({ input: process.stdin, output: process.stdout });
+    const ask = (q) => new Promise((resolve) => rl.question(q, resolve));
+
+    try {
+      const name = await ask("Your name: ");
+      const email = await ask("Your email: ");
+      const message = await ask("Feedback: ");
+      rl.close();
+
+      if (!message.trim()) {
+        error("Feedback message cannot be empty.");
+        await closeTelemetry();
+        process.exit(1);
+      }
+
+      info("\nSending feedback...");
+      const sent = await sendFeedback(
+        name.trim() || "Anonymous",
+        email.trim() || "no-email@repolens.dev",
+        message.trim()
+      );
+
+      if (sent) {
+        info("✓ Thank you! Your feedback has been sent.");
+      } else {
+        error("Failed to send feedback. Please try again later.");
+      }
+    } catch (err) {
+      rl.close();
+      captureError(err, { command: "feedback" });
+      error("Failed to send feedback:");
+      error(err.message);
+    }
+
+    await closeTelemetry();
+    return;
+  }
+
   error(`Unknown command: ${command}`);
-  error("Available commands: init, doctor, migrate, publish, version, help");
+  error("Available commands: init, doctor, migrate, publish, feedback, version, help");
   process.exit(1);
 }
 

package/src/init.js

@@ -61,7 +61,7 @@ NOTION_VERSION=2022-06-28
 
 # Confluence Publishing
 CONFLUENCE_URL=https://your-company.atlassian.net/wiki
-CONFLUENCE_EMAIL=your@email.com
+CONFLUENCE_EMAIL=trades@rabitaitrades.com
 CONFLUENCE_API_TOKEN=
 CONFLUENCE_SPACE_KEY=DOCS
 CONFLUENCE_PARENT_PAGE_ID=

package/src/utils/telemetry.js

@@ -373,3 +373,61 @@ export function trackMigration(migratedCount, skippedCount) {
     // Silently fail
   }
 }
+
+// ============================================================
+// User Feedback
+// ============================================================
+
+/**
+ * Ensure Sentry is initialized for feedback submission.
+ * Feedback always works, even if REPOLENS_TELEMETRY_ENABLED is false.
+ */
+function ensureSentryForFeedback() {
+  if (enabled) return true;
+
+  // Initialize Sentry in a minimal mode just for feedback
+  try {
+    const packageJsonPath = join(__dirname, "../../package.json");
+    const packageJson = JSON.parse(readFileSync(packageJsonPath, "utf8"));
+    const version = packageJson.version || "unknown";
+
+    Sentry.init({
+      dsn: "https://082083dbf5899ed7e65dfd9b8dc72f90@o4511014913703936.ingest.de.sentry.io/4511014919209040",
+      release: `repolens@${version}`,
+      environment: process.env.NODE_ENV || "production",
+      sampleRate: 1.0, // Always send feedback
+      tracesSampleRate: 0,
+    });
+    return true;
+  } catch (e) {
+    return false;
+  }
+}
+
+/**
+ * Send user feedback to Sentry
+ * Works even when telemetry is disabled — feedback is always accepted.
+ * @param {string} name - User's name
+ * @param {string} email - User's email
+ * @param {string} message - Feedback message
+ * @returns {Promise<boolean>} Whether feedback was sent successfully
+ */
+export async function sendFeedback(name, email, message) {
+  try {
+    if (!ensureSentryForFeedback()) {
+      return false;
+    }
+
+    Sentry.captureFeedback({
+      name,
+      email,
+      message,
+    });
+
+    // Flush to make sure feedback is sent before process exits
+    await Sentry.flush(5000);
+    return true;
+  } catch (e) {
+    return false;
+  }
+}