agileflow 2.51.0 → 2.56.0

package/README.md

@@ -3,531 +3,151 @@
 </p>
 
 [![npm version](https://img.shields.io/npm/v/agileflow?color=brightgreen)](https://www.npmjs.com/package/agileflow)
-[![Commands](https://img.shields.io/badge/commands-41-blue)](#commands)
-[![Subagents](https://img.shields.io/badge/subagents-26-orange)](SUBAGENTS.md)
-[![Skills](https://img.shields.io/badge/skills-23-purple)](#skills)
+[![Commands](https://img.shields.io/badge/commands-41-blue)](docs/04-architecture/commands.md)
+[![Agents/Experts](https://img.shields.io/badge/agents%2Fexperts-26-orange)](docs/04-architecture/subagents.md)
+[![Skills](https://img.shields.io/badge/skills-23-purple)](docs/04-architecture/skills.md)
 
-**AI-driven agile development for Claude Code, Cursor, Windsurf, and more.** Combining Scrum, Kanban, ADRs, and docs-as-code principles into one framework-agnostic system.
+**AI-driven agile development for Claude Code, Cursor, Windsurf, OpenAI Codex CLI, and more.** Combining Scrum, Kanban, ADRs, and docs-as-code principles into one framework-agnostic system.
+
+---
 
 ## Quick Start
 
 ### Installation
 
-#### Option 1: Global Installation (Recommended)
-
+**Global (Recommended):**
 ```bash
 npm install -g agileflow
 agileflow setup
 ```
 
-#### Option 2: Project-Level Installation
-
+**Project-Level:**
 ```bash
 npm install agileflow
 npx agileflow setup
 ```
 
-This will:
-1. Prompt where to install AgileFlow
-2. Prompt to select your IDE(s)
-3. Install AgileFlow core (commands, agents, skills)
-4. Configure your selected IDEs
-5. Create documentation structure
-
-### CLI Commands
-
-**Global installation:**
-```bash
-agileflow setup       # Set up AgileFlow in project
-agileflow status      # Check installation + updates
-agileflow update      # Update to latest version
-agileflow list        # List installed components
-agileflow doctor      # Diagnose issues
-agileflow uninstall   # Remove from project
-```
-
-**Project-level installation (use `npx`):**
-```bash
-npx agileflow setup       # Set up AgileFlow in project
-npx agileflow status      # Check installation + updates
-npx agileflow update      # Update to latest version
-npx agileflow list        # List installed components
-npx agileflow doctor      # Diagnose issues
-npx agileflow uninstall   # Remove from project
-```
-
 ### After Setup
 
-**Initialize the system:**
-```
-/agileflow:setup
-```
-Scaffolds docs structure, templates, and optional CI configuration.
-
-**Get help:**
-```
-/agileflow:help
-```
-View system overview and available commands.
-
-**Use the mentor (recommended):**
-```
-Use the mentor subagent to guide me through implementing <feature>
+```bash
+/agileflow:help              # View all commands
+/agileflow:babysit           # Interactive mentor for implementation
+/agileflow:configure         # Configure hooks, status line, etc.
 ```
-Interactive mentor guides you through epic/story creation, implementation, and PR preparation.
 
 ### Supported IDEs
 
 | IDE | Status | Config Location |
 |-----|--------|-----------------|
-| Claude Code | ✅ Supported | `.claude/commands/agileflow/` |
-| Cursor | ✅ Supported | `.cursor/rules/agileflow/` |
-| Windsurf | ✅ Supported | `.windsurf/workflows/agileflow/` |
+| Claude Code | Supported | `.claude/commands/agileflow/` |
+| Cursor | Supported | `.cursor/rules/agileflow/` |
+| Windsurf | Supported | `.windsurf/workflows/agileflow/` |
+| OpenAI Codex CLI | Supported | `.codex/skills/` |
+
+---
 
 ## Why AgileFlow?
 
 AgileFlow combines three proven methodologies:
 
-- **Agile (Scrum/Kanban)** - Break work into Epics → Stories → Acceptance Criteria with WIP limits
+- **Agile (Scrum/Kanban)** - Break work into Epics → Stories → Acceptance Criteria
 - **ADRs** - Record architectural decisions so future teams don't re-debate
-- **Docs-as-Code** - Humans and AI agents coordinate via versioned files (traceable, reviewable, automatable)
+- **Docs-as-Code** - Humans and AI agents coordinate via versioned files
 
 **Key Benefits:**
 - Clear priorities and testable increments
 - Durable memory and decision history
-- Effortless multi-agent collaboration via message bus
+- Multi-agent collaboration via message bus
 - Works with any tech stack or framework
 
-<details>
-<summary><strong>📁 Folder Structure</strong> (click to expand)</summary>
-
-After running `/agileflow:setup`:
-
-```
-docs/
-  00-meta/             # Templates, glossary, conventions
-  01-brainstorming/    # Ideas and sketches
-  02-practices/        # Testing, git, CI, security practices
-    prompts/agents/    # Agent profiles and contracts
-  03-decisions/        # ADRs (Architecture Decision Records)
-  04-architecture/     # Architecture documentation
-  05-epics/            # Epic definitions
-  06-stories/          # User stories (grouped by epic)
-  07-testing/          # Test cases and acceptance criteria
-  08-project/          # Roadmap, backlog, milestones, risks
-  09-agents/           # Agent status and message bus
-    bus/log.jsonl      # Agent communication log
-    status.json        # Current story statuses
-  10-research/         # Saved research notes
-  context.md           # One-page context brief for web AI tools
-```
-
-</details>
-
-<details>
-<summary><strong>📚 Commands</strong> (41 total - click to expand)</summary>
-
-### Core Workflow
-- `/agileflow:setup` - Bootstrap the entire system
-- `/agileflow:help` - Display system overview
-- `/agileflow:babysit` - Interactive mentor for end-to-end implementation
-
-### Planning & Structure
-- `/agileflow:epic` - Create a new epic
-- `/agileflow:story` - Create a user story with acceptance criteria
-- `/agileflow:story-validate` - Validate story completeness before development
-- `/agileflow:sprint` - Data-driven sprint planning with velocity forecasting
-- `/agileflow:adr` - Create an Architecture Decision Record
-- `/agileflow:agent` - Onboard a new agent
-
-### Task Management
-- `/agileflow:assign` - Assign/reassign a story
-- `/agileflow:status` - Update story status
-- `/agileflow:handoff` - Document handoff between agents
-
-### Quality & CI
-- `/agileflow:pr` - Generate PR description
-- `/agileflow:ci` - Bootstrap CI workflow
-- `/agileflow:readme-sync` - Sync folder READMEs
-- `/agileflow:tests` - Automated testing infrastructure setup
-- `/agileflow:review` - AI-powered code review
-- `/agileflow:verify` - Run tests and update story test status (Session Harness)
-- `/agileflow:session-init` - Initialize session harness with test verification (Phase 2)
-- `/agileflow:resume` - Resume session with environment verification and context (Phase 2)
-- `/agileflow:baseline` - Mark current state as verified baseline (Phase 2)
-- `/agileflow:compress` - Compress status.json (fixes token limit issues)
-
-### Automation & DevOps
-- `/agileflow:packages` - Manage dependencies (dashboard, updates, security audits)
-- `/agileflow:docs` - Synchronize docs with code changes
-- `/agileflow:impact` - Analyze change impact on codebase
-- `/agileflow:debt` - Track and prioritize technical debt
-- `/agileflow:deploy` - Automated deployment pipeline setup
-- `/agileflow:changelog` - Auto-generate changelog from commits
-- `/agileflow:auto` - Generate stories from PRDs/mockups/specs
-- `/agileflow:template` - Create and manage custom templates
-- `/agileflow:feedback` - Collect feedback for continuous improvement
-- `/agileflow:update` - Generate stakeholder reports
-
-### Visualization & Analytics
-- `/agileflow:board` - Visual kanban board with WIP limits
-- `/agileflow:blockers` - Comprehensive blocker tracking with resolution suggestions
-- `/agileflow:velocity` - Velocity tracking and forecasting
-- `/agileflow:metrics` - Analytics dashboard (cycle time, lead time, throughput, flow efficiency)
-- `/agileflow:retro` - Automated retrospective generator with insights
-- `/agileflow:deps` - Dependency graph visualization with critical path detection
-
-### Web AI Integration
-- `/agileflow:context` - Generate/export/manage context for web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.)
-- `/agileflow:research` - Save research notes
-
-</details>
-
-<details>
-<summary><strong>🤖 Subagents</strong> (26 specialized agents - click to expand)</summary>
-
-AgileFlow includes **26 specialized subagents** that operate in separate context windows for focused work. See [SUBAGENTS.md](SUBAGENTS.md) for complete documentation.
-
-### Core Implementation Agents
-
-**`ui`** - UI/Presentation Layer Specialist
-- Front-end components, styling, theming, accessibility (WCAG 2.1 AA)
-- Invocation: "Use the ui subagent to implement this UI feature"
-
-**`api`** - Services/Data Layer Specialist
-- Backend APIs, business logic, data models, API tests
-- Invocation: "Use the api subagent to implement this API endpoint"
-
-**`ci`** - CI/CD & Quality Specialist
-- CI/CD pipelines, linting, type checking, test coverage
-- Invocation: "Use the ci subagent to set up the test pipeline"
-
-### Orchestration & Planning Agents
-
-**`mentor`** - End-to-End Implementation Mentor
-- Guides feature implementation from idea to PR
-- Invocation: "Use the mentor subagent to guide me through this feature"
-
-**`epic-planner`** - Epic & Story Planning Specialist
-- Breaks down features into epics and stories with acceptance criteria
-- Invocation: "Use the epic-planner subagent to plan this feature"
-
-**`adr-writer`** - Architecture Decision Record Specialist
-- Documents technical decisions, trade-offs, alternatives
-- Invocation: "Use the adr-writer subagent to document this decision"
-
-**`research`** - Research & Knowledge Management Specialist
-- Conducts technical research, builds research prompts, saves notes
-- Invocation: "Use the research subagent to research authentication approaches"
-
-### Additional Specialized Agents
-- `devops` - DevOps & Automation
-- `security` - Security & Compliance
-- `database` - Database & Data Layer
-- `testing` - Testing & QA Automation
-- `product` - Product Management & Prioritization
-- `performance` - Performance Optimization
-- `mobile` - Mobile Development
-- `integrations` - Third-Party Integrations
-- `refactor` - Code Refactoring & Technical Debt
-- `design` - Design Systems & UI/UX
-- `accessibility` - Accessibility Compliance (WCAG)
-- `analytics` - Analytics & Metrics Implementation
-- `datamigration` - Data Migration & ETL
-- `qa` - Quality Assurance & Test Planning
-- And more...
-
-**When to Use Subagents:**
-- Complex, multi-step implementation work
-- Specialized tasks requiring focused expertise
-- Work benefiting from separate context
-- Tasks needing to run commands or write code
-
-**When to Use Commands:**
-- Quick, single-purpose actions
-- Status updates and assignments
-- Generating templates or prompts
-- Simple file operations
-
-</details>
-
-<details>
-<summary><strong>🎯 Skills</strong> (23 auto-loaded skills - click to expand)</summary>
-
-Skills are **context-aware helpers** that activate automatically based on keywords (no manual invocation needed).
-
-### How Skills Work
-- **Activation:** Automatic (keyword-based detection)
-- **Context:** Main conversation
-- **Purpose:** Quick enhancements and formatting
-- **Structure:** Follow Anthropic's minimal specification (v2.21.0+)
-
-### Skills by Category
-
-#### AgileFlow Skills (8 skills)
-Auto-formatted outputs following AgileFlow templates:
-- `agileflow-story-writer` - Converts discussions to user stories
-- `agileflow-acceptance-criteria` - Generates Given/When/Then AC
-- `epic-planner` - Breaks features into epics/stories
-- `agileflow-sprint-planner` - Plans sprints with velocity
-- `agileflow-retro-facilitator` - Structures retrospectives
-- `agileflow-adr` - Captures architectural decisions
-- `agileflow-commit-messages` - Formats Conventional Commits
-- `agileflow-tech-debt` - Tracks technical debt
-
-#### Template Generators (15 skills)
-Generate code templates and documentation:
-- `story-skeleton` - Story template scaffolding
-- `acceptance-criteria-generator` - AC formatting
-- `commit-message-formatter` - Git commit messages
-- `adr-template` - Architecture decision records
-- `api-documentation-generator` - OpenAPI/Swagger docs
-- `changelog-entry` - Keep a Changelog format
-- `pr-description` - Pull request descriptions
-- `test-case-generator` - Test cases from AC
-- `type-definitions` - TypeScript interfaces
-- `sql-schema-generator` - SQL schemas with migrations
-- `error-handler-template` - Error handling patterns
-- `diagram-generator` - Mermaid/ASCII diagrams
-- `validation-schema-generator` - Joi/Zod/Yup schemas
-- `deployment-guide-generator` - Deployment runbooks
-- `migration-checklist` - Data migration checklists
-
-### Example Activation
-```
-User: "I need to create a user story for login functionality"
-[agileflow-story-writer skill activates automatically]
-Claude: Generates formatted story with AC, owner, priority, estimate
-```
-
-</details>
-
-<details>
-<summary><strong>🎯 Hooks System</strong> (event-driven automation - click to expand)</summary>
-
-AgileFlow supports **event-driven automation** through Claude Code's official hooks system.
-
-### What Are Hooks?
-
-Hooks are automatic triggers that execute commands in response to events:
-- **SessionStart** - Runs when Claude Code session starts
-- **UserPromptSubmit** - Runs after you submit a prompt
-- **Stop** - Runs when Claude stops responding
-
-### Quick Setup
-
-1. **Create .claude directory:**
-   ```bash
-   mkdir -p .claude
-   ```
-
-2. **Copy template:**
-   ```bash
-   cp templates/claude-settings.example.json .claude/settings.json
-   ```
-
-3. **Customize hooks** (edit `.claude/settings.json`):
-   ```json
-   {
-     "hooks": {
-       "SessionStart": [{
-         "hooks": [{
-           "type": "command",
-           "command": "echo '🚀 AgileFlow loaded - Type /agileflow:help'"
-         }]
-       }]
-     }
-   }
-   ```
-
-4. **Restart Claude Code**
-
-### Example Use Cases
-
-**Welcome message:**
-```json
-{
-  "SessionStart": [{
-    "hooks": [{
-      "type": "command",
-      "command": "echo '👋 Welcome! Current sprint: $(cat docs/08-project/current-sprint.txt)'"
-    }]
-  }]
-}
-```
-
-**Activity logging:**
-```json
-{
-  "UserPromptSubmit": [{
-    "hooks": [{
-      "type": "command",
-      "command": "echo '[LOG] Prompt at $(date)' >> .claude/activity.log"
-    }]
-  }]
-}
-```
+---
 
-### Configuration Files
-- `.claude/settings.json` - Project-level config (committed to git)
-- `.claude/settings.local.json` - User-specific overrides (gitignored)
+## Core Components
 
-</details>
+| Component | Count | Description |
+|-----------|-------|-------------|
+| [Commands](docs/04-architecture/commands.md) | 41 | Slash commands for agile workflows |
+| [Agents/Experts](docs/04-architecture/subagents.md) | 26 | Specialized agents with self-improving knowledge bases |
+| [Skills](docs/04-architecture/skills.md) | 23 | Auto-activated context helpers |
 
-<details>
-<summary><strong>🔧 Advanced Topics</strong> (click to expand)</summary>
+---
 
-### Daily Workflow
+## Documentation
 
-1. **Pick a story** - Use `mentor` or check `docs/09-agents/status.json`
-2. **Implement to AC** - Follow acceptance criteria
-3. **Write tests** - Reference `docs/07-testing/test-cases/<STORY_ID>.md`
-4. **Update status** - Use `/agileflow:status`
-5. **Create PR** - Use `/agileflow:pr`
-6. **Mark done** - Update status after merge
+Full documentation lives in [`docs/04-architecture/`](docs/04-architecture/):
 
-### Multi-Agent Collaboration
+### Reference
+- [Commands](docs/04-architecture/commands.md) - All 41 slash commands
+- [Agents/Experts](docs/04-architecture/subagents.md) - 26 specialized agents with self-improving knowledge
+- [Skills](docs/04-architecture/skills.md) - 23 auto-loaded skills
 
-AgileFlow uses a message bus (`docs/09-agents/bus/log.jsonl`) for coordination:
-- Agents update `docs/09-agents/status.json` with current work
-- Messages logged to bus for async communication
-- Use `/agileflow:handoff` to transfer work between agents
-- WIP limit: max 2 stories per agent
+### Architecture
+- [AgileFlow CLI Overview](docs/04-architecture/agileflow-cli-overview.md) - System architecture
+- [Agent Expert System](docs/04-architecture/agent-expert-system.md) - Self-improving agents
+- [Multi-Expert Orchestration](docs/04-architecture/multi-expert-orchestration.md) - Parallel expert analysis
+- [Multi-Session Coordination](docs/04-architecture/multi-session-coordination.md) - Parallel Claude Code sessions
 
-### Git Worktrees for Context Preservation
+### Configuration
+- [Configuration System](docs/04-architecture/configuration-system.md) - 8 configuration agents
+- [Hooks System](docs/04-architecture/hooks-system.md) - Event-driven automation
+- [Session Harness](docs/04-architecture/session-harness.md) - Test verification and sessions
+- [PreCompact Context](docs/04-architecture/precompact-context.md) - Context preservation during compacts
 
-For advanced users handling urgent hotfixes during feature work:
+---
 
-**Benefits:**
-- Preserve AI context when switching tasks
-- Handle production bugs without losing feature flow
-- Compare implementations side-by-side
-- Test risky refactors in isolation
+## Examples
 
-**Quick Start:**
+### Create an Epic with Stories
 ```bash
-# Use helper script (created by /agileflow:setup)
-./docs/00-meta/scripts/worktree-create.sh auth-hotfix
-
-# Open in new window
-code ../myapp-auth-hotfix
-/agileflow:babysit
+/agileflow:epic EPIC=EP-0001 TITLE="User Authentication" OWNER=AG-API GOAL="Secure login"
 ```
 
-See `docs/00-meta/guides/worktrees.md` for comprehensive guide.
-
-### Web AI Integration
-
-Share context with web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.):
-
-1. Run `/agileflow:context` to generate/refresh context
-2. Use `/agileflow:context MODE=export` for concise excerpt
-3. Paste into web AI tool for research/ideation
-4. Use `/agileflow:context MODE=research TOPIC="..."` for structured prompts
-5. Save results with `/agileflow:research`
-
-### Session Harness System (v2.24.0+)
-
-Ensures test verification and session continuity for long-running projects. Prevents agents from breaking functionality and maintains progress across context windows.
-
-**The Problem:**
-Without verification, agents can:
-- Break existing functionality without noticing
-- Claim features work when tests fail
-- Lose context between sessions
-- Mark incomplete work as finished
-
-**The Solution:**
-Session Harness System tracks test status, verifies baselines, and maintains session state.
-
-**Quick Start:**
+### Work on a Story
 ```bash
-# First time setup (interactive)
-/agileflow:session-init
-
-# Start each session (or auto-run via hook)
-/agileflow:resume
-
-# Run tests and update test status
-/agileflow:verify
-
-# Create verified checkpoint
-/agileflow:baseline "Sprint 12 complete"
+/agileflow:assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress
+# ... implement ...
+/agileflow:status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete"
 ```
 
-**How It Works:**
-1. **Test Tracking**: Every story has `test_status` field (passing/failing/not_run)
-2. **Pre-Implementation**: Agents check test_status before starting work
-3. **Post-Implementation**: Agents run `/agileflow:verify` before marking complete
-4. **Session Resume**: Loads context and detects regressions
-5. **Baselines**: Git tags mark known-good states for reset points
-
-**Benefits:**
-- **No Broken Baselines**: Agents can't mark stories complete with failing tests
-- **Fail Fast**: Catch regressions immediately, not at PR review
-- **Context Continuity**: Structured handoff between sessions
-- **Regression Detection**: Alerts when tests were passing, now failing
-
-**Agent Integration (v2.26.0):**
-All 18 dev agents now include verification protocol:
-- ui, api, ci, devops
-- security, database, testing
-- performance, mobile, integrations
-- refactor, design, accessibility
-- analytics, datamigration, monitoring
-- compliance, qa
-
-**Learn More:** See CLAUDE.md "Session Harness System" section for complete documentation.
-
-### Status.json Compression
-
-Prevent "file too large" errors:
-
+### Use Multi-Expert Analysis
 ```bash
-# Compress status.json (removes verbose fields)
-/agileflow:compress
-
-# Typical result: 80-90% size reduction
+/agileflow:multi-expert Is this authentication implementation secure?
 ```
 
-Full story content remains in `docs/06-stories/` markdown files (no data loss).
+### Work in Parallel Sessions
+```bash
+/agileflow:session:new       # Create isolated workspace
+/agileflow:session:status    # View all sessions
+```
 
-</details>
+---
 
-## Examples
+## Project Structure
 
-### Creating an Epic with Stories
-```
-/agileflow:epic EPIC=EP-0001 TITLE="User Authentication" OWNER=AG-API GOAL="Secure user login and registration" STORIES="US-0001|Login form|AG-UI,US-0002|Auth API|AG-API"
-```
+After running `agileflow setup`:
 
-### Working on a Story
 ```
-/agileflow:assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress NOTE="Starting implementation"
-# ... do the work ...
-/agileflow:status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete with tests" PR=https://github.com/...
-```
-
-### Recording a Decision
-```
-/agileflow:adr NUMBER=0001 TITLE="Use JWT for authentication" CONTEXT="Need stateless auth for API" DECISION="JWT with 15min access + refresh tokens" CONSEQUENCES="Simpler scaling but requires token refresh flow"
+docs/
+  00-meta/             # Templates, conventions
+  01-brainstorming/    # Ideas and sketches
+  02-practices/        # Testing, git, CI practices
+  03-decisions/        # ADRs
+  04-architecture/     # Architecture documentation
+  05-epics/            # Epic definitions
+  06-stories/          # User stories
+  07-testing/          # Test cases
+  08-project/          # Roadmap, backlog
+  09-agents/           # Agent status, message bus
+  10-research/         # Research notes
 ```
 
-## Templates
-
-All templates are located in `templates/` and `docs/00-meta/templates/`:
+---
 
-- `epic-template.md` - Epic structure
-- `story-template.md` - User story format
-- `adr-template.md` - Architecture decision record
-- `agent-profile-template.md` - Agent profile and contract
-- `comms-note-template.md` - Handoff documentation
-- `research-template.md` - Research note structure
-- `README-template.md` - Folder README template
+## Online Documentation
 
-## Contributing
+Visit [projectquestorg.com](https://projectquestorg.com) for the full documentation site.
 
-This plugin is designed to be framework-agnostic. Customize templates and commands to fit your team's workflow.
+---
 
 ## License
 
@@ -535,4 +155,4 @@ MIT
 
 ## Support
 
-For issues or questions, please visit the [GitHub repository](https://github.com/projectquestorg/AgileFlow).
+For issues or questions, visit the [GitHub repository](https://github.com/projectquestorg/AgileFlow).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agileflow",
-  "version": "2.51.0",
+  "version": "2.56.0",
   "description": "AI-driven agile development system for Claude Code, Cursor, Windsurf, and more",
   "keywords": [
     "agile",
@@ -41,8 +41,14 @@
     "agileflow:setup": "node tools/cli/agileflow-cli.js setup",
     "agileflow:status": "node tools/cli/agileflow-cli.js status",
     "agileflow:update": "node tools/cli/agileflow-cli.js update",
-    "lint": "echo 'No linting configured yet'",
-    "test": "echo 'No tests configured yet'"
+    "lint": "eslint .",
+    "lint:strict": "eslint . --max-warnings 0",
+    "lint:fix": "eslint . --fix",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "test": "jest",
+    "test:watch": "jest --watch",
+    "test:coverage": "jest --coverage"
   },
   "dependencies": {
     "chalk": "^4.1.2",
@@ -58,5 +64,14 @@
   },
   "publishConfig": {
     "access": "public"
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.39.2",
+    "eslint": "^9.39.2",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-prettier": "^5.5.4",
+    "globals": "^16.5.0",
+    "jest": "^30.2.0",
+    "prettier": "^3.7.4"
   }
 }