aiwf 0.3.8 → 0.3.12

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

package/claude-code/aiwf/en/.aiwf/02_REQUIREMENTS/CLAUDE.md

@@ -1,78 +0,0 @@
-# CLAUDE.md - Requirements Folder Structure Guide
-
-## Overview
-This folder contains all project milestones and their associated requirements documentation. Each milestone represents a major project phase or feature set.
-
-## Milestone Naming Convention
-**CRITICAL**: Milestone folders MUST follow this exact pattern:
-```
-M##_Milestone_Name/
-```
-
-- `M##` - Two-digit milestone number (M01, M02, etc.)
-- `_` - Single underscore separator
-- `Milestone_Name` - Descriptive name using underscores for spaces
-
-### Examples:
-- ✅ `M01_Backend_Setup/`
-- ✅ `M02_Frontend_UI/`
-- ✅ `M03_Authentication_System/`
-- ❌ `M1_Backend/` (missing leading zero)
-- ❌ `M01-Backend-Setup/` (wrong separator)
-- ❌ `Backend_Setup/` (missing M## prefix)
-
-## Milestone Structure
-Each milestone folder MUST contain:
-
-### 1. Milestone Meta File (REQUIRED)
-- **Name**: `M##_milestone_meta.md`
-- **Purpose**: Contains milestone metadata and overview
-- **Location**: Root of milestone folder
-
-### 2. Product Requirements Documents (PRD)
-- **Pattern**: `PRD_*.md`
-- **Examples**: `PRD_Backend_Setup.md`, `PRD_User_Authentication.md`
-- **Purpose**: Define product requirements and user stories
-
-### 3. Technical Specifications
-- **Pattern**: `SPECS_*.md`
-- **Examples**: `SPECS_API_V1.md`, `SPECS_Database_Schema.md`
-- **Purpose**: Technical implementation details
-
-### 4. Amendments (as needed)
-- **Pattern**: `PRD_AMEND_##_*.md`
-- **Examples**: `PRD_AMEND_01_Additional_Endpoints.md`
-- **Purpose**: Document changes to original requirements
-
-## Example Structure
-```
-02_REQUIREMENTS/
-├── M01_Backend_Setup/
-│   ├── M01_milestone_meta.md
-│   ├── PRD_Backend_Setup.md
-│   ├── SPECS_API_V1.md
-│   └── PRD_AMEND_01_Cache_Layer.md
-├── M02_Frontend_UI/
-│   ├── M02_milestone_meta.md
-│   ├── PRD_User_Interface.md
-│   └── SPECS_Component_Library.md
-└── M03_Authentication_System/
-    ├── M03_milestone_meta.md
-    ├── PRD_Authentication.md
-    └── SPECS_OAuth_Integration.md
-```
-
-## Important Notes for Claude Code
-
-1. **Always use the M## prefix** when creating milestone folders
-2. **Use underscores** for spaces in milestone names
-3. **Create the milestone meta file first** using the template from `99_TEMPLATES/milestone_meta_template.md`
-4. **Update the project manifest** (`00_PROJECT_MANIFEST.md`) when creating new milestones
-5. **Maintain sequential numbering** - don't skip milestone numbers
-
-## Common Mistakes to Avoid
-- Creating milestones without the M## prefix
-- Using hyphens instead of underscores
-- Forgetting the milestone meta file
-- Not updating the project manifest
-- Creating milestones in the wrong location (must be in 02_REQUIREMENTS)

package/claude-code/aiwf/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/M01_milestone_meta.md

@@ -1,42 +0,0 @@
----
-milestone_id: M01
-title: Backend Setup
-status: active # pending | active | completed | blocked | on_hold
-last_updated: 2023-07-10
----
-
-# Milestone: Backend Setup (EXAMPLE)
-
-## Goals
-
-This milestone focuses on establishing the core backend infrastructure for the project, including:
-
-1. Setting up the initial project structure
-2. Defining the database schema and models
-3. Implementing basic API endpoints
-4. Establishing authentication and authorization systems
-
-## Key Documents
-
-- [Product Requirements Document](./PRD_Backend_Setup.md)
-- [API Specifications V1](./SPECS_API_V1.md)
-- [Auth Flow Update Amendment](./PRD_AMEND_01_Auth_Flow_Update.md)
-
-## Definition of Done (DoD)
-
-This milestone will be considered complete when:
-
-- The backend server can be started and responds to API requests
-- All core models are defined and can be created/updated/deleted via the API
-- Authentication is working with JWT tokens
-- Basic error handling is implemented
-- Integration tests are passing for all endpoints
-
-## Notes / Context
-
-This is an example milestone document to demonstrate how milestones might be structured in a project using the AIWF framework. The backend infrastructure established here would be the foundation for a typical web application.
-
-## Related Sprints
-
-- [S01_M01_Initial_API](../../03_SPRINTS/S01_M01_Initial_API/S01_sprint_meta.md)
-- [S02_M01_Database_Integration](../../03_SPRINTS/S02_M01_Database_Integration/S02_sprint_meta.md)

package/claude-code/aiwf/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_AMEND_01_Auth_Flow_Update.md

@@ -1,73 +0,0 @@
-# Amendment: Auth Flow Update (EXAMPLE)
-
-## Date: 2023-05-17
-
-## Overview
-
-This amendment updates the authentication flow requirements to incorporate OAuth 2.0 support for social logins in addition to the existing email/password authentication.
-
-**Note: This is an example amendment document to demonstrate how requirement changes might be tracked in the AIWF framework.**
-
-## Changes to Product Requirements
-
-### User Management (FR-1)
-
-**Added Requirements:**
-
-- FR-1.6: The system shall allow users to register and log in using Google OAuth
-- FR-1.7: The system shall allow users to register and log in using GitHub OAuth
-- FR-1.8: The system shall link social login accounts with existing email accounts when the email matches
-
-### Data Models (FR-2)
-
-**Updated FR-2.1 (User model):**
-
-Add the following fields to the User model:
-
-- `oauth_provider`: string (null, 'google', 'github')
-- `oauth_id`: string (provider-specific user ID)
-
-### API Endpoints (FR-3)
-
-**Added Endpoints to FR-3.1:**
-
-- GET /api/auth/oauth/google (Redirect URL for Google OAuth)
-- GET /api/auth/oauth/github (Redirect URL for GitHub OAuth)
-- GET /api/auth/oauth/callback (OAuth provider callback)
-
-## Changes to Non-Functional Requirements
-
-**Updated NFR-5:**
-
-- NFR-5: The system shall implement JWT-based authentication with support for OAuth 2.0 providers
-
-**Added NFR:**
-
-- NFR-9: The system shall securely store OAuth provider credentials in environment variables
-
-## Implementation Impact
-
-- Required libraries: `passport`, `passport-google-oauth20`, `passport-github2`
-- Additional environment variables needed:
-  - `GOOGLE_CLIENT_ID`
-  - `GOOGLE_CLIENT_SECRET`
-  - `GITHUB_CLIENT_ID`
-  - `GITHUB_CLIENT_SECRET`
-  - `OAUTH_CALLBACK_URL`
-
-## Test Cases
-
-- TC-1: User can log in with Google account
-- TC-2: User can log in with GitHub account
-- TC-3: Social login with matching email links to existing account
-- TC-4: JWT token works correctly regardless of authentication method
-
-## Timeline Impact
-
-Implementation of these changes is expected to add 3 days to the original timeline.
-
-## Approvals
-
-- Requested by: Sarah Chen (Product Manager)
-- Approved by: Mike Johnson (Technical Lead)
-- Approved by: David Lee (Project Manager)

package/claude-code/aiwf/en/.aiwf/02_REQUIREMENTS/M01_Backend_Setup/PRD_Backend_Setup.md

@@ -1,98 +0,0 @@
-# Product Requirements Document: Backend Setup
-
-## Overview
-
-This document outlines the requirements for setting up the backend infrastructure for our application. The backend will provide API endpoints for client applications, handle data persistence, and implement business logic.
-
-## Functional Requirements
-
-### User Management
-
-- FR-1.1: The system shall allow users to register with email and password
-- FR-1.2: The system shall allow users to log in with their credentials
-- FR-1.3: The system shall allow users to reset their password via email
-- FR-1.4: The system shall allow users to update their profile information
-- FR-1.5: The system shall allow administrators to disable user accounts
-
-### Data Models
-
-- FR-2.1: The system shall implement a User model with fields for:
-  - Email (unique)
-  - Password (hashed)
-  - Profile information (name, avatar, etc.)
-  - Role (user, admin)
-  - Account status (active, disabled)
-
-- FR-2.2: The system shall implement a Project model with fields for:
-  - Title
-  - Description
-  - Creation date
-  - Owner (User reference)
-  - Members (User references)
-  - Status (active, archived)
-
-- FR-2.3: The system shall implement a Task model with fields for:
-  - Title
-  - Description
-  - Due date
-  - Assigned user (User reference)
-  - Project (Project reference)
-  - Status (todo, in_progress, done)
-  - Priority (low, medium, high)
-
-### API Endpoints
-
-- FR-3.1: The system shall provide authentication endpoints:
-  - POST /api/auth/register
-  - POST /api/auth/login
-  - POST /api/auth/reset-password
-  - POST /api/auth/reset-password-confirm
-
-- FR-3.2: The system shall provide user management endpoints:
-  - GET /api/users/me
-  - PUT /api/users/me
-  - GET /api/users (admin only)
-  - PUT /api/users/:id (admin only)
-
-- FR-3.3: The system shall provide project management endpoints:
-  - GET /api/projects
-  - POST /api/projects
-  - GET /api/projects/:id
-  - PUT /api/projects/:id
-  - DELETE /api/projects/:id
-
-- FR-3.4: The system shall provide task management endpoints:
-  - GET /api/projects/:id/tasks
-  - POST /api/projects/:id/tasks
-  - GET /api/tasks/:id
-  - PUT /api/tasks/:id
-  - DELETE /api/tasks/:id
-
-## Non-Functional Requirements
-
-- NFR-1: The backend shall be implemented using Node.js and Express
-- NFR-2: The system shall use MongoDB for data persistence
-- NFR-3: API response time shall be under 200ms for 95% of requests
-- NFR-4: The system shall handle up to 1000 concurrent users
-- NFR-5: The system shall implement JWT-based authentication
-- NFR-6: All API endpoints shall be documented using OpenAPI/Swagger
-- NFR-7: The codebase shall have at least 80% test coverage
-- NFR-8: The system shall log all errors and API requests
-
-## Constraints
-
-- The backend must be deployable to AWS and Azure
-- The system must comply with GDPR requirements for user data
-- The API must be versioned to support future changes
-
-## Assumptions
-
-- The client applications will be responsible for input validation
-- The backend will be accessed only through the API, not directly
-- The database will be hosted on a managed service (MongoDB Atlas)
-
-## Dependencies
-
-- MongoDB Atlas account
-- SMTP service for email sending
-- JWT secret key management