aiwf 0.3.7 → 0.3.12

package/.eslintrc.json

@@ -1,26 +0,0 @@
-{
-  "extends": ["eslint:recommended"],
-  "parserOptions": {
-    "ecmaVersion": 2022,
-    "sourceType": "module"
-  },
-  "env": {
-    "node": true,
-    "es2022": true
-  },
-  "rules": {
-    "no-console": "warn",
-    "no-unused-vars": ["error", { "argsIgnorePattern": "^_" }],
-    "prefer-const": "error",
-    "no-var": "error",
-    "eqeqeq": ["error", "always"],
-    "curly": ["error", "all"],
-    "quotes": ["error", "single"],
-    "semi": ["error", "always"],
-    "indent": ["error", 2],
-    "no-trailing-spaces": "error",
-    "comma-dangle": ["error", "never"],
-    "object-curly-spacing": ["error", "always"],
-    "array-bracket-spacing": ["error", "never"]
-  }
-}

package/.prettierrc

@@ -1,10 +0,0 @@
-{
-  "semi": true,
-  "singleQuote": true,
-  "tabWidth": 2,
-  "printWidth": 100,
-  "trailingComma": "none",
-  "bracketSpacing": true,
-  "arrowParens": "avoid",
-  "endOfLine": "lf"
-}

package/CLAUDE.md

@@ -1,254 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-This is **aiwf** (AI Workflow Framework), an NPM package that installs the AIWF project management framework for AI-assisted development. It's an updated version of the Simone framework, specifically designed for Claude Code integration.
-
-## Changelog Guidelines
-
-- **Changelog Best Practices**: Always summarize changes concisely by feature or component
-- Aim for clear, brief descriptions that highlight the key modifications in each update
-- Group changes by type: Added, Changed, Fixed, Removed
-- Provide context for significant changes without unnecessary details
-- Always use English
-
-## Project Structure
-
-The AIWF project is organized as follows:
-
-```
-aiwf/
-├── ai-tools/             # AI tool-specific configurations
-│   ├── claude-code/      # Claude Code specific settings
-│   ├── cursor/           # Cursor AI integration
-│   ├── windsurf/        # Windsurf integration
-│   └── github-copilot/   # GitHub Copilot integration
-├── commands/             # AIWF command implementations
-│   ├── ai-persona.js     # AI persona management
-│   ├── compress-context.js # Context compression
-│   ├── evaluate.js       # Evaluation functionality
-│   ├── feature-ledger.js # Feature tracking
-│   └── token-tracking.js # Token usage monitoring
-├── config/               # Configuration files
-│   ├── commit-patterns.js # Git commit patterns
-│   └── language.json     # Language settings
-├── docs/                 # Project documentation
-├── feature-ledger/       # Feature tracking JSON files
-│   ├── FL-001-authentication.json
-│   └── feature-index.json
-├── hooks/                # Git hooks and installation scripts
-│   ├── install-hooks.sh  # Hook installation script
-│   └── post-commit       # Post-commit hook
-├── lib/                  # Core library modules
-├── personas/             # AI persona definitions and knowledge bases
-├── rules/                # Development rules and guidelines
-│   ├── global/          # Global development rules
-│   └── manual/          # Manual operation guides
-├── scripts/              # Build and utility scripts
-├── templates/            # Project templates
-│   ├── api-server/      # Express.js API server template
-│   ├── npm-library/     # NPM library template
-│   └── web-app/         # React web app template
-├── tests/                # Test suites
-│   ├── integration/      # Integration tests
-│   └── unit/            # Unit tests
-├── utils/                # Utility modules
-├── package.json          # NPM package configuration
-├── CLAUDE.md            # This file - Claude Code guidance
-└── README.md            # Project documentation
-```
-
-## AI Tools Directory
-
-The `ai-tools/` directory contains configurations for various AI coding assistants:
-
-- **claude-code/**: Claude Code specific settings and templates
-- **cursor/**: Cursor AI integration files
-- **windsurf/**: Windsurf configuration
-- **github-copilot/**: GitHub Copilot integration
-- **augment/**: Augment AI tool configuration
-
-Each tool directory includes:
-- `config.json`: Tool-specific configuration
-- `template/`: Template files for that specific AI tool
-- `README.md`: Documentation for the integration
-
-## Commands Directory
-
-The `commands/` directory contains all AIWF command implementations:
-
-- **ai-persona.js**: Manages AI personas and their behaviors
-- **compress-context.js**: Compresses context to optimize token usage
-- **evaluate.js**: Evaluates code quality and AI responses
-- **feature-ledger.js**: Tracks features and their development status
-- **feature-commit-report.js**: Generates reports from git commits
-- **persona-context-apply.js**: Applies persona contexts to AI interactions
-- **scan-git-history.js**: Analyzes git history for insights
-- **sync-feature-commits.js**: Synchronizes feature commits with ledger
-- **token-tracking.js**: Monitors and reports token usage
-
-## Templates Directory
-
-The `templates/` directory provides starter templates for different project types:
-
-- **api-server/**: Express.js API server with TypeScript
-  - Includes Swagger documentation
-  - AIWF middleware integration
-  - Jest testing setup
-  
-- **npm-library/**: NPM package template
-  - TypeScript configuration
-  - Rollup bundling
-  - Complete testing setup
-  
-- **web-app/**: React + Vite web application
-  - TypeScript + Tailwind CSS
-  - AIWF dashboard components
-  - State management setup
-
-## Feature Ledger Directory
-
-The `feature-ledger/` directory contains JSON files for tracking feature development:
-
-- **FL-001-authentication.json**: Authentication feature tracking
-- **feature-index.json**: Index of all features and their status
-
-Feature ledgers help track:
-- Feature status (planned, in-progress, completed)
-- Related git commits
-- Development milestones
-- Integration with git workflow through hooks
-
-## Hooks Directory
-
-The `hooks/` directory contains Git hooks for automated workflow:
-
-- **install-hooks.sh**: Script to install git hooks into the project
-- **post-commit**: Automatically syncs feature ledger with git commits
-
-To install hooks:
-```bash
-./hooks/install-hooks.sh
-```
-
-The post-commit hook automatically:
-- Parses commit messages for feature references
-- Updates feature status in the ledger
-- Maintains feature-commit relationships
-
-## Utils Directory
-
-The `utils/` directory contains utility modules for various AIWF features:
-
-- **Compression utilities**: Various strategies for context compression
-- **Git utilities**: Git operation helpers and integrations
-- **Token management**: Token counting, tracking, and optimization
-- **Text processing**: Summarization and content normalization
-- **Persona utilities**: Context parsing and behavior validation
-
-## Key Files and Configurations
-
-### package.json Configuration
-- **Type**: ES Module (`"type": "module"`)
-- **Version**: 0.3.3
-- **Main binaries**:
-  - `aiwf` - Main CLI command
-  - `aiwf-lang` - Language management CLI
-
-### Available Scripts
-- `npm test` - Run Jest tests with ES module support
-- `npm run lang:status` - Check language settings
-- `npm run lang:set` - Set language preference
-- `npm run lang:reset` - Reset to auto-detection
-- `npm run validate:commands` - Validate command implementations
-
-## AIWF Framework Development Rules
-
-- **CRITICAL**: All development and source code modifications for the AIWF framework occur directly in the root project directories.
-- When developing new features or modifying existing ones, work directly with the files in `commands/`, `utils/`, `lib/`, etc.
-- The `.aiwf/` directory (when created in user projects) is a generated instance for the end user. Framework development happens in the main repository.
-- Always test changes thoroughly before committing, as modifications directly affect the framework.
-
-## Development Guidelines
-
-### ES Module Usage
-This project uses ES modules. Always use:
-- `import` instead of `require`
-- `export` instead of `module.exports`
-- File extensions in imports when needed
-
-### Language Support
-- AIWF supports both English and Korean languages
-- Language is managed through the `aiwf-lang` CLI command
-- Documentation is provided in both languages (e.g., README.md, README.ko.md)
-- Commands and interfaces adapt based on the selected language
-
-### Language Content Rules
-**IMPORTANT**: Language management approach:
-- The framework uses a unified codebase with language-specific resources
-- Language selection is handled at runtime through `config/language.json`
-- Documentation files use language suffixes:
-  - English: `GUIDE.md`
-  - Korean: `GUIDE.ko.md`
-- Code comments and inline documentation should be in English for maintainability
-- User-facing messages and prompts are loaded from language-specific resources
-- Technical terms, function names, and variable names remain in English
-
-### Testing
-- Write tests for all new features
-- Maintain integration tests in `tests/integration/`
-- Unit tests go in `tests/unit/`
-- Use Jest with ES module configuration
-
-### Git Workflow
-- Follow the commit patterns defined in `config/commit-patterns.js`
-- Use meaningful commit messages
-- Group related changes together
-
-## Language-Specific Features
-
-### Switching Languages
-Users can switch languages using:
-```bash
-aiwf-lang set ko  # Switch to Korean
-aiwf-lang set en  # Switch to English
-```
-
-### Language Detection
-The system automatically detects system language on first install, with fallback to English.
-
-### Localization
-- Commands can have language-specific suffixes (e.g., `_kr`)
-- Documentation is available in both languages
-- Template content is fully localized
-
-## Core Architecture
-
-AIWF is built on a modular architecture designed for extensibility and AI tool integration:
-
-### Command System
-- Commands are self-contained modules in the `commands/` directory
-- Each command exports a default function that handles the command logic
-- Commands can utilize utilities from `utils/` and libraries from `lib/`
-
-### AI Persona System
-- Personas are defined in JSON format in the `personas/` directory
-- Each persona has associated knowledge bases and best practices
-- The system supports dynamic persona switching and context application
-
-### Token Management
-- Built-in token tracking and optimization
-- Multiple compression strategies for context management
-- Real-time monitoring and reporting capabilities
-
-### Template System
-- Project templates are stored in the `templates/` directory
-- Each template is a complete, working project setup
-- Templates include AIWF integration out of the box
-
-### Multi-Language Support
-- Runtime language switching via `aiwf-lang` command
-- Localized documentation and user interfaces
-- Unified codebase with language-specific resources

package/RELEASE_NOTES_M02.md

@@ -1,177 +0,0 @@
-# AIWF v0.4.0 Release Notes - M02 Milestone
-
-## 🎉 Overview
-
-AIWF v0.4.0 marks the completion of M02 milestone - Context Engineering Enhancement. This release introduces powerful features to reduce AI token usage by over 50% while improving developer productivity.
-
-## ✨ New Features
-
-### 1. Context Compression System
-- Advanced compression algorithms reducing token usage by 50-55%
-- Real-time compression with < 200ms latency
-- Lossless compression ensuring data integrity
-- Automatic compression for large files
-
-### 2. AI Persona System
-- 5 pre-configured personas: analyst, architect, developer, reviewer, tester
-- Dynamic context switching based on task type
-- Persona performance tracking and metrics
-- Custom persona creation support
-
-### 3. Enhanced Feature Ledger
-- Automatic Git integration
-- Feature lifecycle tracking
-- Milestone linking
-- Performance metrics per feature
-
-### 4. AI Tool Integration Templates
-- Claude Code integration template
-- GitHub Copilot configuration
-- Cursor IDE setup guide
-- Windsurf integration
-- Augment tool support
-
-### 5. Comprehensive Documentation
-- Complete Korean documentation
-- Installation and setup guides
-- Feature-specific tutorials
-- Troubleshooting guide
-- API reference
-
-## 📊 Performance Improvements
-
-- **Token Usage**: 53.5% average reduction
-- **Compression Speed**: < 200ms for 99% of files
-- **Memory Overhead**: < 50MB
-- **Cost Savings**: ~$36/month for typical usage
-
-## 🔧 Technical Changes
-
-### Breaking Changes
-None - Full backward compatibility maintained
-
-### API Updates
-```javascript
-// New compression API
-aiwf.compress(content, { level: 'medium' })
-
-// Persona switching
-aiwf.persona.activate('developer')
-
-// Feature ledger Git integration
-aiwf.ledger.linkToCommit(featureId, commitHash)
-```
-
-### Dependencies
-- Added: fs-extra@11.2.0
-- Updated: commander@12.0.0
-- Security: All dependencies updated to latest secure versions
-
-## 🐛 Bug Fixes
-
-- Fixed feature ledger parsing for malformed files
-- Resolved persona context loading race condition
-- Corrected compression ratio calculation
-- Fixed CLI command validation errors
-
-## 📝 Documentation
-
-### New Guides
-- Context Compression Guide (Korean)
-- AI Personas Guide (Korean)
-- Feature Git Integration Guide (Korean)
-- Performance Benchmark Report
-- Usability Test Report
-
-### Updated Documentation
-- Installation Guide - Added troubleshooting section
-- API Reference - New compression and persona APIs
-- Commands Guide - Updated with new CLI commands
-
-## 🚀 Migration Guide
-
-### From v0.3.x to v0.4.0
-
-1. **Update AIWF**
-   ```bash
-   npm update -g aiwf
-   ```
-
-2. **Initialize new features**
-   ```bash
-   aiwf upgrade --to-v0.4
-   ```
-
-3. **Configure compression** (optional)
-   ```bash
-   aiwf config compression --level medium
-   ```
-
-4. **Set default persona** (optional)
-   ```bash
-   aiwf persona set-default developer
-   ```
-
-## ⚠️ Known Issues
-
-1. **Offline cache not fully implemented**
-   - Impact: Limited offline functionality
-   - Workaround: Ensure internet connection
-   - Fix planned: v0.5.0
-
-2. **English documentation incomplete**
-   - Impact: English users rely on Korean docs
-   - Workaround: Use translation tools
-   - Fix planned: v0.4.1
-
-3. **Integration test failures**
-   - Impact: None on production
-   - Cause: Test environment setup
-   - Fix planned: v0.4.1
-
-## 🎯 What's Next
-
-### v0.4.1 (Bug fixes)
-- Complete English documentation
-- Fix integration test environment
-- Minor UI improvements
-
-### v0.5.0 (S04 Sprint)
-- Full offline cache implementation
-- Performance monitoring dashboard
-- Additional AI tool integrations
-- Enhanced error handling
-
-## 🙏 Acknowledgments
-
-Thanks to all contributors who made this release possible:
-- Feature Ledger system design and implementation
-- AI Persona system architecture
-- Context compression algorithm development
-- Comprehensive testing and documentation
-
-## 📦 Installation
-
-### New Installation
-```bash
-npm install -g aiwf@0.4.0
-aiwf init
-```
-
-### Upgrade
-```bash
-npm update -g aiwf
-aiwf upgrade
-```
-
-## 📞 Support
-
-- Documentation: https://aiwf.dev/docs
-- Issues: https://github.com/aiwf/aiwf/issues
-- Discord: https://discord.gg/aiwf
-
----
-
-**Release Date**: 2025-07-08
-**Version**: 0.4.0
-**Codename**: Context Master

package/TEST_RECOVERY_PLAN.md

@@ -1,68 +0,0 @@
-# AIWF 테스트 복구 계획
-
-## 현재 상황
-- 리팩토링 후 테스트 파일들이 손실되거나 불일치 상태
-- GitHub API → file-downloader.js 리팩토링 완료
-- 테스트 실행 시 다수 실패 발생
-
-## 복구 전략
-
-### Phase 1: Critical Tests (필수 테스트)
-**우선순위: 최고**
-- [ ] `basic.test.js` - 기본 프로젝트 구조
-- [ ] `installer.test.js` - 설치 프로그램 기능
-- [ ] `language-utils.test.js` - 언어 관리 유틸리티
-
-### Phase 2: Core Functionality Tests (핵심 기능)
-**우선순위: 높음**
-- [ ] `application.test.js` - 메인 애플리케이션
-- [ ] `commands.test.js` - 명령어 파일 검증
-- [ ] `integration/command-integration.test.js` - 명령어 통합
-
-### Phase 3: Advanced Features (고급 기능)
-**우선순위: 중간**
-- [ ] `unit/ai-persona-manager.test.js` - AI 페르소나 관리
-- [ ] `integration/context-compression.test.js` - 컨텍스트 압축
-- [ ] `token-tracking.test.js` - 토큰 추적
-
-### Phase 4: Optional Tests (선택적 테스트)
-**우선순위: 낮음**
-- [ ] `integration/feature-ledger.test.js` - Feature Ledger
-- [ ] `integration/git-integration.test.js` - Git 통합
-- [ ] `s02-integration.test.js` - S02 통합
-
-## 복구 방법
-
-### 1. 즉시 수정 가능한 테스트
-- 경로 불일치 수정
-- 설정 값 업데이트
-- Import 경로 수정
-
-### 2. 리팩토링 필요한 테스트
-- 삭제된 모듈 참조 제거
-- 새로운 API에 맞게 테스트 수정
-- Mock 객체 업데이트
-
-### 3. 완전히 새로 작성할 테스트
-- 새로운 file-downloader.js 테스트
-- 업데이트된 installer 로직 테스트
-
-## 실행 계획
-
-1. **Phase 1 복구** (1-2시간)
-   - basic.test.js 수정
-   - installer.test.js 업데이트
-   - language-utils.test.js 검증
-
-2. **Phase 2 복구** (2-3시간)
-   - 핵심 기능 테스트 복구
-   - 통합 테스트 수정
-
-3. **Phase 3-4 검토** (필요시)
-   - 고급 기능 테스트 평가
-   - 불필요한 테스트 제거
-
-## 성공 기준
-- [ ] 모든 Critical 테스트 통과
-- [ ] 80% 이상 테스트 커버리지
-- [ ] CI/CD 파이프라인 정상 작동

package/claude-code/aiwf/en/.aiwf/00_PROJECT_MANIFEST.md

@@ -1,49 +0,0 @@
----
-project_name: Your Project Name
-current_milestone_id: M01
-highest_sprint_in_milestone: S02
-current_sprint_id: S01
-status: active
-last_updated: 2025-01-01 00:00:00
----
-
-# Project Manifest: Your Project Name
-
-This manifest serves as the central reference point for the project. It tracks the current focus and links to key documentation.
-
-## 1. Project Vision & Overview
-
-[Describe your project's core vision, purpose, and goals here. What problem does it solve? Who is it for? What makes it unique?]
-
-This project follows a milestone-based development approach.
-
-## 2. Current Focus
-
-- **Milestone:** M01 - [Your First Milestone Name]
-- **Sprint:** S01 - [Current Sprint Focus]
-
-## 3. Sprints in Current Milestone
-
-### S01 [Sprint Name] (🚧 IN PROGRESS)
-
-🚧 [First deliverable or feature]
-📋 [Second deliverable or feature]
-📋 [Third deliverable or feature]
-
-### S02 [Sprint Name] (📋 PLANNED)
-
-📋 [First planned deliverable]
-📋 [Second planned deliverable]
-📋 [Third planned deliverable]
-
-## 4. Key Documentation
-
-- [Architecture Documentation](./01_PROJECT_DOCS/ARCHITECTURE.md)
-- [Current Milestone Requirements](./02_REQUIREMENTS/M01_[Milestone_Name]/)
-- [General Tasks](./04_GENERAL_TASKS/)
-
-## 5. Quick Links
-
-- **Current Sprint:** [S01 Sprint Folder](./03_SPRINTS/S01_M01_[Sprint_Name]/)
-- **Active Tasks:** Check sprint folder for T##_S01_*.md files
-- **Project Reviews:** [Latest Review](./10_STATE_OF_PROJECT/)

package/claude-code/aiwf/en/.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md

@@ -1,55 +0,0 @@
-# Demo Project Architecture (EXAMPLE)
-
-This document outlines the high-level architecture of the Demo Project. **This is an example document to demonstrate how architecture might be documented in the AIWF framework.**
-
-## System Overview
-
-This is a demonstration of how a system architecture document might be structured. In a real project, this would contain actual architectural details.
-
-## Technical Architecture (Example)
-
-### Backend
-
-- **API Layer**: Node.js with Express.js
-- **Database**: MongoDB for primary data storage
-- **Authentication**: JWT-based authentication with OAuth support
-- **Caching**: Redis for performance optimization
-- **Testing**: Jest for unit and integration testing
-
-### Frontend
-
-- **Web Client**: React.js with TypeScript
-- **Mobile Apps**: React Native for iOS and Android
-- **State Management**: Redux for predictable state
-- **UI Framework**: Material-UI for consistent design
-
-## System Components (Example)
-
-1. **Authentication Service**: Handles user signup, login, and session management
-2. **Project Management Service**: Manages projects, teams, and permissions
-3. **Task Service**: Core task CRUD operations and business logic
-4. **Notification Service**: Manages user notifications and alerts
-5. **Analytics Service**: Provides usage statistics and reporting
-
-## Data Flow (Example)
-
-1. Clients authenticate through the Authentication Service
-2. Authenticated requests are routed to the appropriate service
-3. Services interact with the database and return responses
-4. Real-time updates are pushed to clients via WebSockets
-
-## Deployment Architecture (Example)
-
-The system is deployed using containerization with Docker and Kubernetes, providing:
-
-- Horizontal scalability for handling load spikes
-- High availability through multiple replicas
-- Zero-downtime deployments
-- Environment isolation (development, staging, production)
-
-## Security Considerations (Example)
-
-- All API endpoints are protected with proper authentication
-- Sensitive data is encrypted at rest and in transit
-- Rate limiting is implemented to prevent abuse
-- Regular security audits and penetration testing