@aiready/context-analyzer 0.9.13 → 0.9.16

package/dist/cli.js

@@ -1020,14 +1020,13 @@ async function analyzeContext(options) {
     });
   }
   const allResults = [...results, ...pythonResults];
-  const issuesOnly = allResults.filter((r) => r.severity !== "info");
-  const sorted = issuesOnly.sort((a, b) => {
+  const sorted = allResults.sort((a, b) => {
     const severityOrder = { critical: 0, major: 1, minor: 2, info: 3 };
     const severityDiff = severityOrder[a.severity] - severityOrder[b.severity];
     if (severityDiff !== 0) return severityDiff;
     return b.contextBudget - a.contextBudget;
   });
-  return sorted.length > 0 ? sorted : results;
+  return sorted;
 }
 function generateSummary(results) {
   if (results.length === 0) {

package/dist/cli.mjs

@@ -2,7 +2,7 @@
 import {
   analyzeContext,
   generateSummary
-} from "./chunk-BD4NWUVG.mjs";
+} from "./chunk-VTALAPQZ.mjs";
 import "./chunk-Y6FXYEAI.mjs";
 
 // src/cli.ts

package/dist/index.js

@@ -1244,14 +1244,13 @@ async function analyzeContext(options) {
     });
   }
   const allResults = [...results, ...pythonResults];
-  const issuesOnly = allResults.filter((r) => r.severity !== "info");
-  const sorted = issuesOnly.sort((a, b) => {
+  const sorted = allResults.sort((a, b) => {
     const severityOrder = { critical: 0, major: 1, minor: 2, info: 3 };
     const severityDiff = severityOrder[a.severity] - severityOrder[b.severity];
     if (severityDiff !== 0) return severityDiff;
     return b.contextBudget - a.contextBudget;
   });
-  return sorted.length > 0 ? sorted : results;
+  return sorted;
 }
 function generateSummary(results) {
   if (results.length === 0) {

package/dist/index.mjs

@@ -10,7 +10,7 @@ import {
   getCoUsageData,
   getSmartDefaults,
   inferDomainFromSemantics
-} from "./chunk-BD4NWUVG.mjs";
+} from "./chunk-VTALAPQZ.mjs";
 import "./chunk-Y6FXYEAI.mjs";
 export {
   analyzeContext,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aiready/context-analyzer",
-  "version": "0.9.13",
+  "version": "0.9.16",
   "description": "AI context window cost analysis - detect fragmented code, deep import chains, and expensive context budgets",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",
@@ -49,7 +49,7 @@
     "commander": "^14.0.0",
     "chalk": "^5.3.0",
     "prompts": "^2.4.2",
-    "@aiready/core": "0.9.13"
+    "@aiready/core": "0.9.16"
   },
   "devDependencies": {
     "@types/node": "^24.0.0",

package/src/index.ts

@@ -299,20 +299,16 @@ export async function analyzeContext(
   // Merge Python and TS/JS results
   const allResults = [...results, ...pythonResults];
 
-  // Filter to only files with actual issues (not just info)
-  // This reduces output noise and focuses on actionable problems
-  const issuesOnly = allResults.filter(r => r.severity !== 'info');
-  
-  // Sort by severity and context budget
-  const sorted = issuesOnly.sort((a, b) => {
+  // Keep ALL results including info severity for visualization purposes
+  // The visualizer needs to show all files as nodes
+  const sorted = allResults.sort((a, b) => {
     const severityOrder = { critical: 0, major: 1, minor: 2, info: 3 };
     const severityDiff = severityOrder[a.severity] - severityOrder[b.severity];
     if (severityDiff !== 0) return severityDiff;
     return b.contextBudget - a.contextBudget;
   });
-  
-  // If we have issues, return them; otherwise return all results
-  return sorted.length > 0 ? sorted : results;
+
+  return sorted;
 }
 
 /**

package/SEMANTIC-VALIDATION.md

@@ -1,235 +0,0 @@
-# Semantic Analysis Validation Results
-
-**Date:** 14 January 2026  
-**Test Project:** receiptclaimer (real-world Next.js application)  
-**Analysis Version:** v0.7.0 (semantic analysis)
-
-## Executive Summary
-
-✅ Semantic analysis successfully deployed and validated on production codebase  
-✅ 181 files analyzed in 0.99s (~5.5ms per file)  
-✅ Identified 10 semantic domains with high accuracy  
-✅ Average cohesion: 75% (up from folder-based approach)  
-✅ Zero false positives or analysis failures
-
-## Key Findings
-
-### 1. Domain Identification Accuracy
-
-**Top Semantic Domains Detected:**
-- `partner`: 7 files, 97% fragmentation, 74% cohesion
-- `gift`: 6 files, 96% fragmentation, 78% cohesion  
-- `google`: 4 files, 95% fragmentation, 90% cohesion
-- `shared`: 3 files, 100% fragmentation, 100% cohesion
-- `categorization`: 3 files, 100% fragmentation, 78% cohesion
-
-**Improvements Over Folder-Based:**
-- ✅ No more "unknown" domains for generic file names
-- ✅ Detected cross-cutting concerns (`shared`, `hook`)
-- ✅ Identified infrastructure domains (`google`, `export`)
-- ✅ Found business logic clusters (`partner`, `gift`, `mileage`)
-
-### 2. Cohesion Analysis
-
-**Distribution:**
-- High cohesion (≥80%): Majority of files
-- Medium cohesion (40-80%): Some integration points
-- Low cohesion (<40%): Cross-cutting concerns (expected)
-
-**Average Cohesion: 75%**  
-This is a strong indicator that semantic analysis correctly identifies when exports belong together vs. when files serve as integration points.
-
-### 3. Fragmentation Detection
-
-**10 Fragmented Module Clusters Identified:**
-
-All clusters show high fragmentation (95-100%), indicating these domains are correctly scattered across the codebase for legitimate architectural reasons:
-
-- Partner management spread across API, UI, blog content
-- Gift functionality across admin, partner APIs, email templates
-- Google integrations across analytics, document AI, layout
-
-**This is correct behavior** - not all fragmentation is bad. Integration layers SHOULD reference multiple domains.
-
-### 4. Performance
-
-```
-Total files: 181
-Analysis time: 0.99s
-Per-file average: ~5.5ms
-```
-
-**Semantic analysis overhead:** Minimal
-- Co-usage matrix building: Fast
-- Type graph construction: Fast  
-- Confidence scoring: Negligible
-
-The 3-pass analysis (basic → semantic → enhancement) adds ~10-15% overhead compared to folder-based approach, but provides dramatically better accuracy.
-
-## Semantic Analysis In Action
-
-### Example: Partner Domain
-
-**Files Detected:**
-1. `shared/src/types/partners.ts` - Type definitions
-2. `web/lib/partners.ts` - Business logic
-3. `web/app/partners/_lib/hooks.ts` - React hooks
-4. `web/app/blog/property-managers-referral-program/content.tsx` - Content
-5. `web/app/blog/accountant-referral-programs-australia/content.tsx` - Content
-6. `web/app/api/partners/gifts/__tests__/test-helpers.ts` - Tests
-7. `web/app/api/partners/gifts/__tests__/fixtures.ts` - Test fixtures
-
-**Why This Is Correct:**
-- All files relate to partner functionality
-- Spread across types, logic, UI, content, tests (appropriate separation)
-- Semantic analysis correctly identified them as belonging to same domain despite different folders
-- Fragmentation score 97% is accurate - these SHOULD be in different folders
-
-**Confidence Signals:**
-- ✅ **Type references** - All reference `Partner` types
-- ✅ **Co-usage** - Often imported together in partner features
-- ✅ **Import paths** - Import from `partners/` folders
-- ✅ **Folder structure** - Most in `partners/` related folders
-
-### Example: Google Domain
-
-**Files Detected:**
-1. `web/app/layout.tsx` - Google Analytics integration
-2. `web/pages/api/internal/top-pages.ts` - Analytics API
-3. `infra/lib/lambda/utils/google-document-ai-client.ts` - Document AI client
-4. `infra/lib/lambda/documentai-adapter.ts` - Document AI adapter
-
-**Why This Is Correct:**
-- All files integrate with Google services
-- Layout → Analytics, Lambda → Document AI (different concerns)
-- 90% cohesion indicates strong semantic relationship despite different purposes
-- Correctly identified as infrastructure domain, not business logic
-
-**Confidence Signals:**
-- ✅ **Co-usage** - Google libraries imported together
-- ✅ **Type references** - Share Google API types
-- ✅ **Import paths** - Reference `google` in imports
-
-## Comparison: Folder-Based vs. Semantic
-
-### Before (Folder-Based Heuristics)
-
-**Problems:**
-- Generic file names → "unknown" domain
-- Folder structure assumed = semantic relationship
-- No confidence scores
-- Single domain per file
-- Missed cross-cutting concerns
-
-**Example Issue:**
-```
-lib/session.ts → "unknown" (generic name)
-lib/dynamodb.ts → "unknown" (generic name)
-components/nav/nav-links.ts → "unknown" (generic name)
-```
-
-### After (Semantic Analysis)
-
-**Improvements:**
-- Real usage patterns → accurate domains
-- Co-usage + types > folder convention
-- Confidence scores show signal strength
-- Multi-domain support for integration points
-- Correctly identifies cross-cutting concerns
-
-**Example Fix:**
-```
-lib/session.ts → "gift" domain (35% co-usage, 30% types)
-lib/dynamodb.ts → "customer" domain (imports from customers/)
-components/nav/nav-links.ts → "order" domain (imports from orders/)
-```
-
-## Validation Criteria
-
-| Criterion | Status | Evidence |
-|-----------|--------|----------|
-| **Accuracy** | ✅ Pass | All detected domains align with actual codebase structure |
-| **Performance** | ✅ Pass | <1s for 181 files, negligible overhead |
-| **Backward Compat** | ✅ Pass | `inferredDomain` still works, existing code unaffected |
-| **Zero Crashes** | ✅ Pass | No analysis failures or errors |
-| **Scalability** | ✅ Pass | O(n²) co-usage acceptable for typical codebases |
-| **Usefulness** | ✅ Pass | Consolidation recommendations are actionable |
-
-## Consolidation Recommendations
-
-Based on semantic analysis, the tool correctly identified:
-
-1. **Partner files (7 files)** - Consolidate into 3 files
-   - Reason: High co-usage, shared types
-   - Estimated savings: 4,022 tokens (30%)
-
-2. **Gift files (6 files)** - Consolidate into 2 files
-   - Reason: Very high co-usage
-   - Estimated savings: 3,296 tokens (30%)
-
-3. **Google files (4 files)** - Consolidate into 2 files
-   - Reason: Infrastructure cluster
-   - Estimated savings: 769 tokens (30%)
-
-**These are evidence-based recommendations**, not guesses based on folder names.
-
-## Confidence Scoring Validation
-
-Spot-checked 10 random files:
-
-| File | Primary Domain | Confidence | Signals | Correct? |
-|------|---------------|------------|---------|----------|
-| partners.ts | partner | High | 4/5 signals | ✅ |
-| gift-notification.ts | gift | High | 4/5 signals | ✅ |
-| documentai-adapter.ts | google | Medium | 3/5 signals | ✅ |
-| session.ts | gift | Medium | 2/5 signals | ✅ |
-| categorization.ts | categorization | High | 4/5 signals | ✅ |
-| mileage-test-helpers.ts | mileage | High | 4/5 signals | ✅ |
-| layout.tsx | google | Low | 2/5 signals | ✅ |
-| rate-limit.ts | export | Low | 1/5 signals | ✅ |
-| nav-links.ts | order | Medium | 2/5 signals | ✅ |
-| PartnerDashboardClient.tsx | partner | High | 4/5 signals | ✅ |
-
-**10/10 correct** - 100% accuracy on spot check
-
-## Edge Cases Handled Correctly
-
-1. **Cross-cutting concerns** - `shared` domain correctly identified
-2. **Integration layers** - Multi-domain files work as expected
-3. **Test files** - Correctly grouped with tested domain
-4. **Infrastructure** - `google`, `export` domains separate from business logic
-5. **Generic names** - No longer result in "unknown"
-
-## Known Limitations
-
-1. **New codebases with few files** - Co-usage matrix sparse, confidence low (expected)
-2. **Very isolated files** - May fall back to folder heuristics (acceptable)
-3. **No imports** - Can't infer from co-usage (expected, rare)
-
-## Conclusion
-
-✅ **Semantic analysis is production-ready**
-
-The pivot from folder-based heuristics to semantic analysis (co-usage + types) dramatically improves domain identification accuracy while maintaining performance.
-
-**Key Achievement:** We now answer the right question:  
-~~"What folder is this file in?"~~  
-✅ **"Which files need to be loaded together to understand this code?"**
-
-This is the correct foundation for AI context optimization.
-
-## Recommendations
-
-1. ✅ **Deploy to production** - Validated and ready
-2. ✅ **Release as v0.7.0** - Major improvement
-3. ✅ **Config-free approach** - Domain detection fully automatic, no user configuration needed
-4. 🔬 **Add call graph analysis** - Next enhancement (v0.8.0)
-5. 🔬 **Add embedding-based clustering** - Future enhancement (v1.0.0)
-
-## Next Steps
-
-- [x] Implement semantic analysis
-- [x] Validate on real codebase
-- [ ] Add comprehensive tests for semantic features
-- [ ] Document confidence scoring for users
-- [ ] Release v0.7.0