aiwf 0.3.7 → 0.3.12

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/2025-06-17-15-08-solid-progress.md

@@ -1,149 +0,0 @@
-# Project Review - 2025-06-17 15:08
-
-## 🎭 Review Sentiment
-
-🚀💪⚠️
-
-## Executive Summary
-
-- **Result:** GOOD
-- **Scope:** Full project review focusing on architecture, test infrastructure, sprint progress, and technical implementation
-- **Overall Judgment:** solid-progress
-
-## Test Infrastructure Assessment
-
-- **Test Suite Status**: FAILING (367/372 tests)
-- **Test Pass Rate**: 98.7% (367 passed, 5 failed)
-- **Test Health Score**: 7/10
-- **Infrastructure Health**: DEGRADED
-  - Import errors: 0
-  - Configuration errors: 0
-  - Fixture issues: 0
-- **Test Categories**:
-  - Unit Tests: 367/372 passing
-  - Integration Tests: Included in unit count
-  - API Tests: E2E tests present but not executed
-- **Critical Issues**:
-  - app.controller.spec.ts - Expectation mismatch
-  - connection.service.spec.ts - TypeScript compilation errors
-  - dataset/database/batch/events controller/service tests failing
-- **Sprint Coverage**: 90% of sprint deliverables have tests
-- **Blocking Status**: CLEAR - Does not block sprint progression (>95% pass rate)
-- **Recommendations**:
-  - Fix failing tests immediately
-  - Address TypeScript type mismatches
-  - Run E2E tests in CI pipeline
-
-## Development Context
-
-- **Current Milestone:** M01 - MVP 안정화 및 핵심 기능 강화 (Active)
-- **Current Sprint:** S01 per manifest, but actually working on S07 tasks
-- **Expected Completeness:** 93% of all tasks complete across all sprints
-
-## Progress Assessment
-
-- **Milestone Progress:** 93% complete (40/43 tasks)
-- **Sprint Status:** 
-  - S01-S06: 100% complete
-  - S07: 62.5% complete (5/8 tasks)
-- **Deliverable Tracking:**
-  - Monitoring infrastructure: ✅ Complete
-  - Performance optimization: ✅ Complete
-  - System stability: ⬜ Not started
-  - Large data handling: ⬜ Not started
-  - Testing enhancement: ⬜ Not started
-
-## Architecture & Technical Assessment
-
-- **Architecture Score:** 7/10 - Well-structured but overly complex in places
-- **Technical Debt Level:** MEDIUM
-  - Duplicate folders (auth/entites vs entities)
-  - Test files in root directory
-  - Overly complex optimization layers
-  - Excessive monitoring systems
-- **Code Quality:** Generally high with good separation of concerns, but suffering from over-engineering
-
-## File Organization Audit
-
-- **Workflow Compliance:** NEEDS_ATTENTION
-- **File Organization Issues:**
-  - Duplicate entity folders: `auth/entites/` and `auth/entities/`
-  - Duplicate query folders: `widget/tabel-query/` and `widget/table-query/`
-  - Test files scattered in root: `test-warmup.js`, `test-connect-info.json`
-  - Temporary controllers in src: `test-compression.controller.ts`, `test-field-selection.controller.ts`
-  - Generated/log files in root: `swagger-spec.json`, `snowflake.log`, `sqlite.db`
-- **Cleanup Tasks Needed:**
-  - Remove duplicate folders and consolidate files
-  - Move test files to appropriate test directories
-  - Remove or properly place temporary test controllers
-  - Add generated files to .gitignore
-
-## Critical Findings
-
-### Critical Issues (Severity 8-10)
-
-#### Test Infrastructure Degradation
-
-- 5 failing tests indicate broken functionality
-- TypeScript compilation errors in connection service
-- Test failures not being addressed promptly
-
-#### File Organization Violations
-
-- Duplicate folders causing confusion
-- Test files polluting root directory
-- Temporary files committed to repository
-
-### Improvement Opportunities (Severity 4-7)
-
-#### Over-Engineering
-
-- Too many monitoring systems (CloudWatch, SlowQuery, Memory, Business metrics)
-- Complex caching layers (Redis + in-memory hybrid)
-- Excessive database optimizers for each DB type
-
-#### Sprint/Task Management
-
-- Manifest shows S01 as current but work happening on S07
-- Some task statuses not updated (T04_S07 marked complete but status still "open")
-
-#### Technical Debt
-
-- Accumulating test failures
-- Complex dependency chains
-- Premature optimization
-
-## John Carmack Critique 🔥
-
-1. **"Stop building monitoring systems and start building features"** - You have CloudWatch integration, slow query monitoring, memory monitoring, business metrics, and performance monitoring. Pick ONE comprehensive solution and delete the rest. Every monitoring system is code that can break.
-
-2. **"Your 5-layer deep optimization stack is a performance anti-pattern"** - ConnectionService → DatabaseOptimizer → QueryOptimizer → CacheService → actual query. Each layer adds latency. Most queries would be faster with a direct connection and good indexes.
-
-3. **"Broken tests are worse than no tests"** - You have 5 failing tests that everyone is ignoring. Either fix them TODAY or delete them. A test suite that doesn't pass 100% trains developers to ignore failures.
-
-## Recommendations
-
-Based on your findings recommend Action items - chose whatever fits your findings
-
-- **Important fixes:**
-  1. Fix all 5 failing tests immediately
-  2. Clean up duplicate folders (auth/entites, widget/tabel-query)
-  3. Remove test files from root directory
-  4. Update task statuses to reflect reality (T04_S07)
-  5. Consolidate monitoring systems into one solution
-
-- **Optional fixes/changes:**
-  1. Simplify database optimization layers
-  2. Remove premature optimization code
-  3. Reduce monitoring overhead
-  4. Implement actual E2E test execution
-  5. Add stricter linting rules for file organization
-
-- **Next Sprint Focus:** 
-  Yes, the project can move to the next sprint, but should prioritize:
-  - System stability improvements (error handling, logging)
-  - Complete remaining S07 tasks (T05, T06)
-  - Address technical debt before adding new features
-  - Focus on core functionality over monitoring
-
-The project shows solid progress with 93% task completion and good architectural foundations. However, it's suffering from over-engineering and needs immediate attention to test failures and file organization. The team should resist adding more monitoring/optimization features and focus on completing the MVP stabilization milestone with simpler, more maintainable solutions.

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/index.json

@@ -1,5 +0,0 @@
-{
-    "milestones": {},
-    "sprints": {},
-    "tasks": {}
-}

package/claude-code/aiwf/en/.aiwf/10_STATE_OF_PROJECT/sync-index.js

@@ -1,78 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-import fg from 'fast-glob';
-import matter from 'gray-matter';
-
-const ROOT = path.resolve(process.cwd(), 'claude-code/aiwf/.aiwf');
-const OUTPUT = path.join(ROOT, '10_STATE_OF_PROJECT', 'index.json');
-
-// Directories to scan for milestone/sprint/task markdown files
-const SCAN_DIRS = [
-    '01_PROJECT_DOCS',
-    '02_REQUIREMENTS',
-    '03_SPRINTS',
-    '04_GENERAL_TASKS'
-].map(dir => path.join(ROOT, dir));
-
-function ensureDirSync(dir) {
-    if (!fs.existsSync(dir)) {
-        fs.mkdirSync(dir, { recursive: true });
-    }
-}
-
-function buildIndex() {
-    /** @type {{milestones: Record<string, any>, sprints: Record<string, any>, tasks: Record<string, any>}} */
-    const index = { milestones: {}, sprints: {}, tasks: {} };
-
-    const patterns = SCAN_DIRS.map(d => `${d}/**/*.md`);
-    const files = fg.sync(patterns, { dot: false, unique: true });
-
-    files.forEach(file => {
-        const relPath = path.relative(ROOT, file);
-        const content = fs.readFileSync(file, 'utf-8');
-        const { data } = matter(content);
-        if (!data || !data.id || !data.type) return; // skip non-annotated files
-
-        const base = {
-            title: data.title || path.basename(file, '.md'),
-            file: relPath,
-            status: data.status || 'todo',
-            ...(data.assignee ? { assignee: data.assignee } : {}),
-            ...(data.tags ? { tags: data.tags } : {}),
-            ...(data.lockedBy ? { lockedBy: data.lockedBy } : {})
-        };
-
-        if (data.type === 'milestone') {
-            index.milestones[data.id] = {
-                ...base,
-                due: data.due || null,
-                sprints: data.sprints || []
-            };
-        } else if (data.type === 'sprint') {
-            index.sprints[data.id] = {
-                ...base,
-                milestone: data.milestone || null,
-                tasks: data.tasks || []
-            };
-        } else if (data.type === 'task') {
-            index.tasks[data.id] = {
-                ...base,
-                sprint: data.sprint || null,
-                milestone: data.milestone || null
-            };
-        }
-    });
-
-    return index;
-}
-
-function main() {
-    const index = buildIndex();
-    ensureDirSync(path.dirname(OUTPUT));
-    fs.writeFileSync(OUTPUT, JSON.stringify(index, null, 2));
-    console.log(`[aiwf] index.json generated with ${Object.keys(index.milestones).length} milestones, ${Object.keys(index.sprints).length} sprints, ${Object.keys(index.tasks).length} tasks.`);
-}
-
-if (require.main === module) {
-    main();
-} 

package/claude-code/aiwf/en/.aiwf/98_PROMPTS/github_integration.md

@@ -1,130 +0,0 @@
-# GitHub Integration with AIWF Framework
-
-This document provides guidance on integrating GitHub issues and pull requests with the AIWF task management system.
-
-## Overview
-
-The AIWF framework now supports seamless integration with GitHub issues and pull requests, enabling better tracking and collaboration through the `gh` CLI tool.
-
-## Key Features
-
-### 1. Task-Issue Linking
-
-- Each task can be linked to a GitHub issue via the `github_issue` field in frontmatter
-- Automatic status synchronization between tasks and issues
-- Bidirectional updates ensure consistency
-
-### 2. Automated Workflows
-
-- Create GitHub issues from tasks: `/project:aiwf:issue_create {task_id}`
-- Generate pull requests with issue linking: `/project:aiwf:pr_create {task_id}`
-- Commit messages automatically include issue references
-
-### 3. Status Management
-
-- Task status changes trigger GitHub issue updates
-- Issues are labeled based on task status (in-progress, completed, etc.)
-- Comments are added to issues for transparency
-
-## Commands Reference
-
-### Issue Creation
-
-```bash
-/project:aiwf:issue_create {task_id}
-```
-
-Creates a GitHub issue from a task file with:
-
-- Title including task ID
-- Description from task content
-- Appropriate labels
-- Automatic assignment
-
-### Pull Request Creation
-
-```bash
-/project:aiwf:pr_create {task_id}
-```
-
-Creates a pull request that:
-
-- Links to the associated issue
-- Includes commit history
-- Auto-closes issue on merge
-- Assigns reviewers
-
-### Manual GitHub Commands
-
-Update issue status:
-
-```bash
-gh issue comment {issue_number} --body "Status update message"
-gh issue edit {issue_number} --add-label "label-name"
-```
-
-Create issue manually:
-
-```bash
-gh issue create \
-  --title "Task: Description" \
-  --body "Detailed description" \
-  --label "task,sprint-01"
-```
-
-## Best Practices
-
-### 1. Issue Creation Timing
-
-- Create issues when starting a sprint
-- Link issues immediately after creation
-- Update frontmatter with issue number
-
-### 2. Commit Messages
-
-- Use `fixes #123` for bug fixes
-- Use `relates to #123` for partial work
-- Include task ID in commit message
-
-### 3. Pull Request Workflow
-
-- Create PR after task completion
-- Ensure all tests pass
-- Link to original issue
-- Request appropriate reviewers
-
-## Integration Points
-
-### Task Files
-
-Add to frontmatter:
-
-```yaml
-github_issue: #123
-```
-
-### Sprint Planning
-
-- Create issues for all tasks at sprint start
-- Use labels to group by sprint
-- Track progress via GitHub Projects
-
-### YOLO Mode
-
-- Automatically creates issues if enabled
-- Creates PRs after successful commits
-- Maintains full automation flow
-
-## Troubleshooting
-
-### Common Issues
-
-1. **Missing gh CLI**: Install GitHub CLI first
-2. **Authentication**: Run `gh auth login`
-3. **Permissions**: Ensure repo access rights
-
-### Error Handling
-
-- Check task file for valid issue number
-- Verify GitHub API limits
-- Ensure branch protection rules allow automation

package/claude-code/aiwf/en/.aiwf/98_PROMPTS/useful-prompts.md

@@ -1,31 +0,0 @@
-# 유용한 프롬프트
-
-## 프로젝트 분석
-
-[Ask, sonnet4 그리고 o3 연속으로..]
-
-```
-이 프로젝트 구조를 자세히 파악해줘
-코드 컨벤션 스타일 디자인 규칙을 모두 분석해서 자세히 설명해줘
-```
-
-## 커서 Rule 생성
-
-[Agent, sonnet4]
-
-```
-/Generate Cursor Rules
-위의 분석한 내용을 기반으로 rule 만들어줘
-내용은 영어로 작성해.
-대표적인 프롬프트 엔지니어링 기법을 적용해서 최적화해줘.
-반드시 지켜야할 규칙, 반드시 하지말아야할 것들을 특히 강조해서 적어줘.
-```
-
-[Agent, sonnet4]
-
-```
-/Generate Cursor Rules
-지금까지 너는 실수를 했지이 실수의 원인을 자세히 분석하고, 로 작성해.
-대표적인 프롬프트 엔지니어링 기법을 적용해서 최적화해줘.
-반드시 지켜야할 규칙, 반드시 하지말아야할 것들을 특히 강조해서 적어줘.
-```

package/claude-code/aiwf/en/.aiwf/98_PROMPTS/vibe-front-prompts.md

@@ -1,89 +0,0 @@
-# VIBE 코딩 프론트엔드 프롬프트
-
-https://github.com/roboco-io/handson-vibecoding-demo
-
-## STEP1
-
-지금부터 간단한 앱을 만드는 것을 데모로 보여주려 고해. TODO앱을 웹 앱으로 만들려고해. 우선 docs 폴더 아래에 요건 정의를 문서화 해 줘. 요건정의를 위해서 필요한 질문들을 포함해줘.
-
-- requirements.md 리뷰
-- .windsurfrules 생성
-
-@requirements.md 참고해서 설계문서 작성을 진행해줘
-
-- design.dm 리뷰
-  mermaid -> svg 로 설계문서를 작성
-
-@design.md 에서 아키텍처 다이어그램은 SVG를 사용해서 정확하고 상서하게 그려줘.
-
-리퀘스트 처리 부분에 대해서 시퀀스 다이어 그램을 추가해줘. 시퀀스 다이어그램은 mermaid 로 그려줘
-
-UI 설계에서 모바일뷰와 데스크톱 뷰의 와이어프레임도 SVG로 생성해줘
-
-카드뷰 보다는 리스트로 표시해줘
-
-@design.md 문서에 기반해서 앞으로 수행해 야 할 작업들을 순서대로 체크리스트로 만들어 줘. UI/UX를 제외한 코어 비즈니스 로직은 TDD 에 기반해서 작업해야해. 작업이 확인 가능한 단 위별로 커밋 포인트도 체크리스트에 표시해줘.
-
-## STEP2
-
-나는 좀 더 간편한 UI Kit을 사용해서 프론트를 구현하고 싶어. 어떤 UI Kit이 좋을까?
-
-Mantine 을 사용해서 UI를 구현하도록 요건과 설계문서를 업데이트 해줘
-
-@implementation-checklist.md 의 이름을 checklist.md 로 바꿔줘
-
-업데이트된 @design.md 내용에 맞춰서 @checklist.md 를 업데이트 해줘
-
-Windsurf rules 수정 :
-
-- 커뮤니케이션은 한국어로 해줘
-- 프론트엔드 UI 구현시에는 실행 코드를 먼저 작성한다. 코어 비즈니스 로직 구현 시에만 TDD로 진행 할 것.
-- 백엔드는 TDD로 구현할 것
-- 커밋 전에 docs/checklist.md에 진행상황을 업데이트 한다.
-- 설계 변경시에는 requirements.md 와 design.md 를 수정한다.
-
-업데이트 된 계획들을 커밋해줘
-
-이제 체크리스트 항목을 시작해줘
-
-프로젝트 설명을 위한 README 를 root 폴더에 만들어줘
-
-[자동화]
-Rules 파일은 자동화에 큰 역할을 담당한다
-Awesome cursor rules 를 참고해서 업데이트 해야한다
-
-@web https://github.com/PatrickJS/awesome-cursorrules/blob/main/rules/nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file/.cursorrules 참고해서 이 프로젝트의 아키텍처와 요구사항 edesign.md, erequirements.nd 을 반영한 규칙 파일을 edocs 에 windsurfruels.md 에 만들어줘
-
-git hook을 이용해서 커밋시에 Iint fix, build, test가 자동으로 수행되도록 하고싶어. 실행 코드에 변경시에만 작동되어야 해.
-우선은 프론트에 대해서 적용해줘
-
-체크리스트에 방금 작업한 내용을 반영해줘. 설계문서와 README 에도 반영해줘
-
-변경사항을 커밋해줘
-
-@pre-commit 을 수정해서 좀 더 디테일한 로그를 남겨서 디버깅을 용이하게 해줘
-
-## STEP3
-
-[P] 나는 프른트 개발을 독립적으로 완료하고 그 다음 백엔드에 연결하는 방식으로 개발을 하고 싶어.
-
-- 관련 체크리스트 조정됨
-
-[P] 체크리스트에 따라서 다음 작업을 진행해줘
-
-- lint 작성확인
-- npm run lint
-
-[P] 이제부터 mantain v7 으로 UI를 구현해줘. 최신버전의 사용법은 @web https://mantine.dev 를 참고해서 구현해줘
-(시안 이미지 복붙후)
-이미지를 참고해서 모바일과 데스크톱 모두 대응되는 반응형 디자인으로 작성해줘.
-이미지는 와이어프레임 이므로 배치만 참고해줘
-
-- 공식문서 파일들을 rules에 업데이트 하자
-- 관련 MCP도 업데이트 되고 있으니 참고하자
-
-@checklist.md 에 데모로서 불필요한 부분을 삭제했어. 삭제된 내용을 @requirements.md, @design.md 에 반영해줘.
-
-@checklist.md 를 보고 다음 구현을 진행해줘. 우선 브라우저 전체 너비를 사용 하도록 레이아웃을 조정해줘. 현재 코드는 고정폭을 사용하고 있어. 수정 하기 전에 관련 코드를 먼저 꼼꼼히 살펴보고 수정을 계획을 세운다음 나에게 확인을 받고 진행 해.
-
-- 중간에 헤맬때는 조사를 하라고 시키면 좋다

package/claude-code/aiwf/en/.aiwf/99_TEMPLATES/adr_template.md

@@ -1,49 +0,0 @@
----
-adr_id: ADR{{number}}
-title: "{{title}}"
-status: "proposed" # proposed | accepted | deprecated | superseded
-date: {{YYYY-MM-DD}}
-authors: ["{{author}}"]
----
-
-# ADR{{number}}: {{title}}
-
-## Status
-
-{{status}} - {{YYYY-MM-DD}}
-
-## Context
-
-{{What is the issue that we're seeing that is motivating this decision or change?}}
-
-## Decision
-
-{{What is the change that we're proposing or have agreed to implement?}}
-
-## Consequences
-
-### Positive
-
-- {{e.g., improvement of quality attribute satisfaction, follows the architectural principles, ...}}
-
-### Negative
-
-- {{e.g., compromising quality attribute, follows the architectural principles, ...}}
-
-## Alternatives Considered
-
-### {{Alternative 1}}
-
-{{Description and reasoning for why this was not chosen}}
-
-### {{Alternative 2}}
-
-{{Description and reasoning for why this was not chosen}}
-
-## Implementation Notes
-
-{{Any specific implementation details, migration steps, or technical considerations}}
-
-## Related
-
-- {{Links to related ADRs, issues, or documentation}}

package/claude-code/aiwf/en/.aiwf/99_TEMPLATES/milestone_meta_template.md

@@ -1,25 +0,0 @@
----
-milestone_id: M<ID>
-title: Milestone Title
-status: pending # pending | active | completed | blocked | on_hold
-last_updated: YYYY-MM-DD HH:MM
----
-
-## Milestone: {{ title }}
-
-### Goals
-- Clearly define the primary objectives of this milestone.
-- What should be achieved by the end of this milestone?
-
-### Key Documents
-
-List the main requirement documents associated with this milestone (e.g., PRD, Technical Specifications).
-
-- `PRD_<Milestone_Name>.md`
-- `SPECS_<Milestone_Name>.md`
-
-### Definition of Done (DoD)
-- Specific, measurable criteria that must be met for this milestone to be considered complete.
-
-### Notes / Context (Optional)
-- Any additional context, high-level strategy, or important notes related to this milestone for Claude.

package/claude-code/aiwf/en/.aiwf/99_TEMPLATES/project_manifest_template.md

@@ -1,39 +0,0 @@
----
-project_name: {{project_name}}
-current_milestone_id: {{current_milestone_id}}
-highest_sprint_in_milestone: {{highest_sprint_in_milestone}}
-current_sprint_id: {{current_sprint_id}}
-status: active
-last_updated: {{timestamp}}
----
-
-# Project Manifest: {{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
-
-{{project_vision}}
-
-This project follows a milestone-based development approach.
-
-## 2. Current Focus
-
-- **Milestone:** {{current_milestone_id}} - {{current_milestone_name}}
-- **Sprint:** {{current_sprint_id}} - {{current_sprint_name}}
-
-## 3. Sprints in Current Milestone
-
-{{sprint_list}}
-
-## 4. Key Documentation
-
-- [Architecture Documentation](./01_PROJECT_DOCS/ARCHITECTURE.md)
-- [Current Milestone Requirements](./02_REQUIREMENTS/{{current_milestone_id}}_{{current_milestone_slug}}/)
-- [General Tasks](./04_GENERAL_TASKS/)
-
-## 5. Quick Links
-
-- **Current Sprint:** [{{current_sprint_id}} Sprint Folder](./03_SPRINTS/{{current_sprint_id}}_{{current_milestone_id}}_{{current_sprint_slug}}/)
-- **Active Tasks:** Check sprint folder for T##_{{current_sprint_id}}_*.md files
-- **Project Reviews:** [Latest Review](./10_STATE_OF_PROJECT/)

package/claude-code/aiwf/en/.aiwf/99_TEMPLATES/sprint_meta_template.md

@@ -1,23 +0,0 @@
----
-sprint_folder_name: S<SprintSequenceID>_M<MilestoneID>_<Short_Name>
-sprint_sequence_id: S<ID>
-milestone_id: M<ID>
-title: Sprint Title - Focus of this Sprint
-status: pending # pending | active | completed | aborted
-goal: Clearly state the primary objective of this sprint.
-last_updated: YYYY-MM-DDTHH:MM:SSZ
----
-
-# Sprint: {{ title }} ({{ sprint_sequence_id }})
-
-## Sprint Goal
-{{ goal }}
-
-## Scope & Key Deliverables (Optional)
-- What specific features, fixes, or outcomes are targeted in this sprint for Claude to work on?
-
-## Definition of Done (for the Sprint) (Optional)
-- What conditions must be met for the sprint itself to be considered successfully completed?
-
-## Notes / Retrospective Points (Optional)
-- Any specific notes for this sprint.

package/claude-code/aiwf/en/.aiwf/99_TEMPLATES/task_template.md

@@ -1,36 +0,0 @@
----
-task_id: T<TaskNN>_S<SprintSequenceID> # For Sprint Tasks (e.g., T01_S01) OR T<NNN> for General Tasks (e.g., T501)
-sprint_sequence_id: S<ID> # e.g., S01 (If part of a sprint, otherwise null or absent)
-status: open # open | in_progress | pending_review | done | failed | blocked
-complexity: Medium # Low | Medium | High
-last_updated: YYYY-MM-DDTHH:MM:SSZ
-github_issue: # Optional: GitHub issue number (e.g., #123)
----
-
-# Task: (Filename serves as the descriptive title)
-
-## Description
-Briefly explain what this task is about. Provide necessary context to understand the 'why' behind the task.
-
-## Goal / Objectives
-Clearly state what needs to be achieved by completing this task. What does success look like?
-- Objective 1
-- Objective 2
-
-## Acceptance Criteria
-Specific, measurable conditions that must be met for this task to be considered 'done'.
-- [ ] Criterion 1 is met.
-- [ ] Criterion 2 is verified.
-
-## Subtasks
-A checklist of smaller steps to complete this task.
-- [ ] Subtask 1
-- [ ] Subtask 2
-
-## Output Log
-*(This section is populated as work progresses on the task)*
-
-[YYYY-MM-DD HH:MM:SS] Started task
-[YYYY-MM-DD HH:MM:SS] Modified files: file1.js, file2.js
-[YYYY-MM-DD HH:MM:SS] Completed subtask: Implemented feature X
-[YYYY-MM-DD HH:MM:SS] Task completed