@crimsonsunset/jsg-logger 1.1.6 → 1.1.7

package/CONTRIBUTING.md

@@ -5,7 +5,7 @@
 **This is a personal utility project that has been extracted and published for reuse.** 
 
 Contributions are welcome, but please note:
-- This project emerged from a specific use case (Chrome Audio Control Platform)
+- This project emerged from a specific use case but is now a generic multi-environment logger
 - The core functionality is stable and feature-complete for most use cases
 - Major architectural changes should be discussed in an issue first
 

package/README.md

@@ -345,12 +345,12 @@ const stats = logger.controls.getStats();
 ### **🚀 BREAKTHROUGH: Perfect Browser Formatting**
 ```
 // Direct browser logger with 100% style control:
-12:00 AM 🎯 [CACP-CORE] ✨ CACP Extension v0.3.2 - Logger Ready!
+12:00 AM 🎯 [JSG-CORE] ✨ JSG Application v1.0.0 - Logger Ready!
 12:00 AM 🎵 [SOUNDCLOUD] MediaSession track change detected
    ├─ title: Alt-J - Breezeblocks (Gkat Remix)
    ├─ artist: Gkat
    ├─ hasArtwork: true
-12:00 AM 🎯 [CACP-CORE] 🧪 Testing JSON context display
+12:00 AM 🎯 [JSG-CORE] 🧪 Testing JSON context display
    ├─ testData: {nested: {...}, simple: 'test string', boolean: true}
    ├─ location: {href: 'https://soundcloud.com/discover', hostname: 'soundcloud.com'}
    ├─ timestamp: 2025-07-29T06:00:53.837Z

package/docs/next-session.md

@@ -68,10 +68,10 @@
 **Solution**: Build essential patterns directly into the JSG Logger package
 
 ### **✅ COMPLETED THIS SESSION:**
-- [x] **Static Singleton Pattern** - `CACPLogger.getInstance()` methods
+- [x] **Static Singleton Pattern** - `JSGLogger.getInstance()` methods
 - [x] **Auto-Discovery Getters** - Both camelCase and kebab-case component access
 - [x] **Non-Destructive Error Handling** - Missing components log but don't break
-- [x] **Static Performance Logging** - `CACPLogger.logPerformance()` utility
+- [x] **Static Performance Logging** - `JSGLogger.logPerformance()` utility
 - [x] **Enhanced Export Structure** - Components and getComponent available
 
 ### **✅ PHASE 8 API ENHANCEMENT COMPLETE:**

package/docs/roadmap.md

@@ -21,9 +21,9 @@
 
 ## 🎯 Current Status
 **Last Updated:** August 21, 2025  
-**Current Phase:** Phase 9 - Genericize Logger (Remove CACP Hardcoding)  
-**Status:** 🚀 **IN PROGRESS** - Making JSG Logger truly generic by removing CACP-specific hardcoded components  
-**Current Issue:** Logger still loads CACP defaults instead of project-specific `logger-config.json` files
+**Current Phase:** Phase 9 - Genericize Logger (Remove Legacy Hardcoding)  
+**Status:** 🚀 **IN PROGRESS** - Making JSG Logger truly generic by removing legacy-specific hardcoded components  
+**Current Issue:** Logger still loads legacy defaults instead of project-specific `logger-config.json` files
 
 ### Progress Overview
 - ✅ **COMPLETED:** Multi-environment logger with smart detection
@@ -340,14 +340,14 @@ Console filtering updates
 
 ## 📈 Recent Progress
 
-### August 21, 2025 - Phase 9 Discovery: CACP Hardcoding Issues 🔍
-- 🐛 **Critical Discovery**: JSG Logger still deeply hardcoded for CACP use cases
-- 🔍 **Issue Identified**: `logger-config.json` files being ignored, falling back to CACP defaults
+### August 21, 2025 - Phase 9 Discovery: Legacy Hardcoding Issues 🔍
+- 🐛 **Critical Discovery**: JSG Logger still deeply hardcoded for legacy use cases
+- 🔍 **Issue Identified**: `logger-config.json` files being ignored, falling back to legacy defaults
 - 📋 **Root Causes Documented**: 6 major areas requiring genericization
-  1. `CACPLogger` class name and all references
-  2. Default config with 10 hardcoded CACP components
+  1. `JSGLogger` class name and all references ✅ COMPLETED
+  2. Default config with 10 hardcoded legacy components
   3. Component schemes duplication 
-  4. Hardcoded legacy aliases for CACP components
+  4. Hardcoded legacy aliases for legacy components
   5. Core component dependency on 'cacp' logger
   6. Config loading path resolution issues
 - 🎯 **Phase 9 Planned**: Complete roadmap for making logger truly generic
@@ -355,7 +355,7 @@ Console filtering updates
 
 ### August 21, 2025 - Phase 8 API Enhancement Complete ✅
 - ✅ **JSG Logger v1.1.0** - Major API simplification enhancements shipped
-- ✅ **Static Singleton Pattern** - `CACPLogger.getInstance()` with auto-initialization
+- ✅ **Static Singleton Pattern** - `JSGLogger.getInstance()` with auto-initialization
 - ✅ **Auto-Discovery Components** - Both camelCase and kebab-case access patterns
 - ✅ **Non-Destructive Error Handling** - Missing components log but don't break apps
 - ✅ **Built-in Performance Logging** - `JSGLogger.logPerformance()` static utility
@@ -433,7 +433,7 @@ Projects using JSG Logger currently need to implement ~220 lines of boilerplate:
 #### **Solution - Built-in Enhancement Features**
 
 **✅ Design Decisions Made:**
-1. **getInstance location**: Static on CACPLogger class
+1. **getInstance location**: Static on JSGLogger class
 2. **Auto-discovery naming**: Both camelCase and kebab-case support
 3. **Performance logging**: Static utility `JSGLogger.logPerformance(...)`
 4. **Error handling**: Non-destructive with helpful logging (no fallbacks)
@@ -444,12 +444,12 @@ Projects using JSG Logger currently need to implement ~220 lines of boilerplate:
 
 ##### **Enhancement 1: Static Singleton Pattern**
 ```javascript
-// Static method on CACPLogger class
-const logger = CACPLogger.getInstance(config);
-const logger2 = CACPLogger.getInstance(); // Same instance, no config needed
+// Static method on JSGLogger class
+const logger = JSGLogger.getInstance(config);
+const logger2 = JSGLogger.getInstance(); // Same instance, no config needed
 ```
 
-**Implementation Location**: `index.js` CACPLogger class
+**Implementation Location**: `index.js` JSGLogger class
 - Add `static _instance = null`
 - Add `static async getInstance(options = {})`
 - Add `static getInstanceSync(options = {})` for sync environments
@@ -575,32 +575,32 @@ export { logger, JSGLogger };
 
 ---
 
-### **Phase 9: Genericize Logger (Remove CACP Hardcoding)** 🚀 IN PROGRESS
-**Goal**: Make JSG Logger truly generic by removing all CACP-specific hardcoded components and references
+### **Phase 9: Genericize Logger (Remove Legacy Hardcoding)** 🚀 IN PROGRESS
+**Goal**: Make JSG Logger truly generic by removing all legacy-specific hardcoded components and references
 
 #### **Background - The Problem**
-During Phase 8 integration testing with jsg-tech-check-site, we discovered the logger is still deeply hardcoded for CACP (Chrome Audio Control Panel) use cases:
+During Phase 8 integration testing with jsg-tech-check-site, we discovered the logger is still deeply hardcoded for legacy use cases:
 
 **Observable Issues:**
 ```
 [JSG-LOGGER] Component 'astro-build' not found. Available: cacp, soundcloud, youtube, site-detector, websocket, popup, background, priority-manager, settings, test, siteDetector, priorityManager
 ```
 
-Despite providing a proper `logger-config.json` with Astro-specific components, the logger falls back to CACP defaults instead of loading the project's configuration.
+Despite providing a proper `logger-config.json` with Astro-specific components, the logger falls back to legacy defaults instead of loading the project's configuration.
 
-#### **Root Causes - What Makes It CACP-Specific**
+#### **Root Causes - What Makes It Legacy-Specific**
 
 ##### **1. Class Name & Core References**
-- `CACPLogger` class name should be `JSGLogger` or `GenericLogger`
-- All static method references (`CACPLogger.getInstance()`, etc.)
-- Error messages mentioning "CACP Logger"
-- `window.CACP_Logger` global should be `window.JSG_Logger`
+- ✅ `JSGLogger` class name updated 
+- ✅ All static method references (`JSGLogger.getInstance()`, etc.)
+- ✅ Error messages mentioning "JSG Logger"
+- ✅ `window.JSG_Logger` global updated
 
 ##### **2. Default Configuration Hardcoding**
 **File:** `/config/default-config.json`
-- **Hardcoded project name**: `"CACP Logger"`
-- **10 CACP-specific components**:
-  - `cacp` (🎯 CACP-CORE) - should be generic `core`
+- **Hardcoded project name**: ✅ `"JSG Logger"`
+- **10 legacy-specific components**:
+  - `cacp` (🎯 JSG-CORE) - should be generic `core`
   - `soundcloud` (🎵 SoundCloud) 
   - `youtube` (📹 YouTube)
   - `site-detector` (🔍 SiteDetector)
@@ -613,7 +613,7 @@ Despite providing a proper `logger-config.json` with Astro-specific components,
 
 ##### **3. Component Schemes Duplication**
 **File:** `/config/component-schemes.js`
-- Duplicates the same 10 hardcoded CACP components
+- Duplicates the same 10 hardcoded legacy components
 - Should be empty/minimal by default for generic usage
 
 ##### **4. Hardcoded Legacy Aliases**
@@ -627,13 +627,13 @@ this.loggers.priorityManager = this.loggers['priority-manager'];
 ```javascript
 // Initialization requires 'cacp' component:
 if (this.loggers.cacp) {
-    this.loggers.cacp.info('CACP Logger initialized', {...});
+    this.loggers.cacp.info('JSG Logger initialized', {...});
 }
 ```
 
 ##### **6. Config Loading Path Issue** 
 - **Critical**: The logger isn't loading our `logger-config.json` properly
-- Falls back to default CACP config instead of using project-specific configurations
+- Falls back to default legacy config instead of using project-specific configurations
 - **Why our Astro config is ignored**: Path resolution or config merging logic issues
 
 #### **🔧 Implementation Plan**
@@ -660,7 +660,7 @@ if (this.loggers.cacp) {
 - `CACPLogger` → `JSGLogger`
 - Update all static method references
 - Update error messages
-- Update browser global: `window.CACP_Logger` → `window.JSG_Logger`
+- ✅ Update browser global: `window.JSG_Logger`
 
 ##### **Fix 3: Fix Config Loading**
 **Target**: Config manager and initialization
@@ -668,7 +668,7 @@ if (this.loggers.cacp) {
 - Ensure project configs override defaults instead of falling back
 - Fix path resolution for various environments (Node.js vs browser)
 
-##### **Fix 4: Remove CACP-Specific Logic**
+##### **Fix 4: Remove Legacy-Specific Logic**
 **Target**: `/index.js` `createAliases()` method
 - Remove hardcoded legacy aliases for `siteDetector`, `priorityManager`
 - Make aliases configurable if needed, not hardcoded
@@ -681,21 +681,21 @@ if (this.loggers.cacp) {
 
 ##### **Fix 6: Clean Component Schemes**
 **Target**: `/config/component-schemes.js`
-- Remove all CACP-specific hardcoded components
+- Remove all legacy-specific hardcoded components
 - Keep only minimal example or make it empty
 - Let projects define their own components
 
 #### **🎯 Success Criteria**
-1. ✅ **Generic by Default**: Fresh installations work without CACP references
+1. ✅ **Generic by Default**: Fresh installations work without legacy references
 2. ✅ **Config Loading Works**: Project-specific `logger-config.json` files are properly loaded
-3. ✅ **No CACP Dependencies**: Logger works without any CACP-specific components
-4. ✅ **Clean API**: `JSGLogger.getInstance()` instead of `CACPLogger.getInstance()`
+3. ✅ **No Legacy Dependencies**: Logger works without any legacy-specific components
+4. ✅ **Clean API**: `JSGLogger.getInstance()` working correctly
 5. ✅ **Test with Real Project**: jsg-tech-check-site loads Astro components correctly
 
 #### **📋 Implementation Steps**
 1. **Debug config loading** - Fix why `logger-config.json` is ignored
-2. **Rename core class** - `CACPLogger` → `JSGLogger`
-3. **Replace default config** - Remove 10 CACP components, use minimal generic
+2. ✅ **Rename core class** - `JSGLogger` completed
+3. **Replace default config** - Remove 10 legacy components, use minimal generic
 4. **Remove hardcoded aliases** - Make legacy aliases configurable
 5. **Fix core component** - Use configurable core for init logging
 6. **Update browser global** - `window.JSG_Logger`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crimsonsunset/jsg-logger",
-  "version": "1.1.6",
+  "version": "1.1.7",
   "type": "module",
   "description": "JSG Logger - Multi-environment logger with smart detection, file-level overrides, and beautiful console formatting",
   "main": "index.js",