@zenuml/core 3.47.9 → 3.48.1

package/bunfig.toml

@@ -1,52 +0,0 @@
-# Bun configuration file
-
-[test]
-# Preload setup file for test environment
-preload = ["./test-setup.ts"]
-
-# Project root directory
-root = "./"
-
-# Note: To exclude /tests folder (Playwright tests), use the npm script:
-# bun run test:bun
-# Or run directly: bun test 'src/**/*.{spec,test}.{ts,tsx}' 'test/**/*.{spec,test}.{ts,tsx}'
-
-# Coverage configuration
-# Disabled by default due to resource issues with large asset files
-# Enable with: bun test --coverage
-coverage = false
-coverageReporter = ["text"]
-coverageDirectory = "./coverage"
-
-# Timeout for tests (in milliseconds)
-timeout = 5000
-
-# Run tests in watch mode by default
-# watch = false
-
-[install]
-# Package manager settings
-peer = true
-dev = true
-optional = true
-
-# Auto install dependencies
-auto = "auto"
-
-# Disable cache if needed
-# disable = false
-
-[install.lockfile]
-# Save exact versions
-save = true
-
-# Print changes to lockfile
-print = "bun"
-
-[run]
-# Bun runtime settings for scripts
-# Silent mode for cleaner output
-# silent = false
-
-# Automatically install missing packages when running scripts
-autoInstall = true

package/docs/UNICODE_SUPPORT.md

@@ -1,179 +0,0 @@
-# Unicode 字符支持
-
-ZenUML 现在完全支持 Unicode 字符，包括中文、日文、韩文、阿拉伯文、俄文等多种语言的标识符。
-
-## 功能特性
-
-### 1. 直接使用 Unicode 字符作为标识符
-
-您可以直接使用任何 Unicode 字母字符作为：
-- 参与者名称
-- 方法名称
-- 变量名称
-- 参数名称
-
-**示例：**
-
-```zenuml
-// 中文标识符
-用户 订单服务 数据库
-
-用户.登录()
-订单服务.创建订单()
-数据库.保存数据()
-return 成功
-```
-
-### 2. 包含空格的文本使用引号
-
-如果标识符中需要包含空格或特殊字符，请使用双引号：
-
-```zenuml
-// 使用引号处理包含空格的名称
-"用户 服务" "订单 管理系统"
-
-"用户 服务"."获取 用户信息"()
-"订单 管理系统"."创建 新订单"()
-return "操作 成功"
-```
-
-### 3. 中英文混合支持
-
-您可以自由混合使用中文和英文：
-
-```zenuml
-UserService 数据库 CacheManager
-
-UserService.获取用户()
-数据库.query("SELECT * FROM users")
-CacheManager.缓存结果()
-```
-
-## 支持的 Unicode 范围
-
-当前实现支持所有 Unicode 字母字符，包括但不限于：
-
-- **中文**：汉字字符
-- **日文**：平假名、片假名、汉字
-- **韩文**：韩文字母
-- **阿拉伯文**：阿拉伯字母
-- **俄文**：西里尔字母
-- **其他**：所有 Unicode 定义的字母字符
-
-## 使用规则
-
-1. **标识符规则**：
-   - 必须以 Unicode 字母或下划线 `_` 开头
-   - 可以包含 Unicode 字母、数字和下划线
-   - 不能包含空格（需要空格请使用引号）
-
-2. **引号字符串**：
-   - 可以包含任何字符（除了换行符）
-   - 适用于包含空格或特殊字符的文本
-
-3. **保留关键字**：
-   - 英文关键字（如 `if`, `while`, `return` 等）保持不变
-   - 不能使用保留关键字作为标识符
-
-## 实际应用示例
-
-### 示例 1：订单处理流程
-
-```zenuml
-title "订单处理流程"
-
-@Actor 用户
-@Service 订单服务
-@Database 数据库
-
-用户->订单服务: 创建订单
-订单服务.验证订单() {
-    if (库存充足) {
-        数据库.保存订单()
-        return "订单创建成功"
-    } else {
-        return "库存不足"
-    }
-}
-```
-
-### 示例 2：用户认证流程
-
-```zenuml
-用户 认证服务 令牌管理器
-
-用户.登录(用户名, 密码)
-认证服务.验证凭据(用户名, 密码) {
-    if (验证成功) {
-        令牌 = 令牌管理器.生成令牌()
-        return 令牌
-    } else {
-        return "认证失败"
-    }
-}
-```
-
-### 示例 3：多语言混合
-
-```zenuml
-// 混合多种语言的示例
-ユーザー // 日文
-사용자   // 韩文
-用户     // 中文
-User     // 英文
-
-ユーザー.ログイン()
-사용자.로그인()
-用户.登录()
-User.login()
-```
-
-## 技术实现
-
-### 词法分析器更改
-
-在 `SequenceLexer.g4` 中，ID token 定义已更新为：
-
-```antlr
-ID
- : [\p{L}_] [\p{L}\p{Nd}_]*
- ;
-```
-
-- `\p{L}` 匹配任何 Unicode 字母
-- `\p{Nd}` 匹配任何 Unicode 十进制数字
-- 保持了对下划线 `_` 的支持
-
-### 向后兼容性
-
-所有现有的 ASCII 标识符仍然完全支持：
-- 英文字母 (a-z, A-Z)
-- 数字 (0-9)
-- 下划线 (_)
-
-现有的 ZenUML 代码无需任何修改即可继续工作。
-
-## 测试
-
-您可以通过以下方式测试 Unicode 支持：
-
-1. **开发服务器测试**：
-   ```bash
-   pnpm dev
-   ```
-   然后访问 http://localhost:8080/test-chinese.html
-
-2. **单元测试**：
-   ```bash
-   pnpm test src/parser/ChineseSupport.spec.ts
-   ```
-
-## 注意事项
-
-1. **编码**：确保您的文件使用 UTF-8 编码保存
-2. **字体支持**：渲染时需要系统或浏览器支持相应的字体
-3. **方向性**：某些语言（如阿拉伯文）是从右到左书写，但在 ZenUML 中仍按从左到右的顺序处理
-
-## 贡献
-
-如果您发现任何 Unicode 相关的问题或有改进建议，欢迎提交 issue 或 pull request。

package/docs/ai-context/deployment-infrastructure.md

@@ -1,21 +0,0 @@
-# Deployment & Infrastructure Documentation
-
-This document contains deployment and infrastructure-related documentation for the project.
-
-## Purpose
-
-This template serves as a placeholder for documenting:
-- Deployment strategies and procedures
-- Infrastructure architecture and configuration
-- CI/CD pipelines and automation
-- Environment management
-- Monitoring and observability setup
-- Scaling strategies and considerations
-
-## Implementation Note
-
-Replace this template with your actual deployment and infrastructure documentation as your project develops. Focus on patterns and decisions that AI agents need to understand when working with infrastructure-related code or making architectural recommendations.
-
----
-
-*Customize this template based on your specific deployment and infrastructure requirements.*

package/docs/ai-context/docs-overview.md

@@ -1,89 +0,0 @@
-# Documentation Architecture
-
-This project uses a **3-tier documentation system** that organizes knowledge by stability and scope, enabling efficient AI context loading and scalable development.
-
-## How the 3-Tier System Works
-
-**Tier 1 (Foundation)**: Stable, system-wide documentation that rarely changes - architectural principles, technology decisions, cross-component patterns, and core development protocols.
-
-**Tier 2 (Component)**: Architectural charters for major components - high-level design principles, integration patterns, and component-wide conventions without feature-specific details.
-
-**Tier 3 (Feature-Specific)**: Granular documentation co-located with code - specific implementation patterns, technical details, and local architectural decisions that evolve with features.
-
-This hierarchy allows AI agents to load targeted context efficiently while maintaining a stable foundation of core knowledge.
-
-## Documentation Principles
-- **Co-location**: Documentation lives near relevant code
-- **Smart Extension**: New documentation files created automatically when warranted
-- **AI-First**: Optimized for efficient AI context loading and machine-readable patterns
-
-## Tier 1: Foundational Documentation (System-Wide)
-
-- **[Master Context](/CLAUDE.md)** - *Essential for every session.* Coding standards, security requirements, MCP server integration patterns, and development protocols
-- **[Project Structure](/docs/ai-context/project-structure.md)** - *REQUIRED reading.* Complete technology stack, file tree, and system architecture. Must be attached to Gemini consultations
-- **[System Integration](/docs/ai-context/system-integration.md)** - *For cross-component work.* Communication patterns, data flow, testing strategies, and performance optimization
-- **[Deployment Infrastructure](/docs/ai-context/deployment-infrastructure.md)** - *Infrastructure patterns.* Containerization, monitoring, CI/CD workflows, and scaling strategies
-- **[Task Management](/docs/ai-context/handoff.md)** - *Session continuity.* Current tasks, documentation system progress, and next session goals
-
-## Tier 2: Component-Level Documentation
-
-### Backend Components
-- **[Backend Context](/backend/CONTEXT.md)** - *Server implementation.* API patterns, database integration, service architecture, and performance considerations
-- **[Worker Services](/workers/CONTEXT.md)** - *Background processing.* Job queue patterns, scheduling, and async task management
-- **[Shared Libraries](/shared/CONTEXT.md)** - *Reusable code.* Common utilities, shared types, and cross-component functionality
-
-### Frontend Components
-- **[Web Application](/frontend/CONTEXT.md)** - *Client implementation.* UI patterns, state management, routing, and user interaction patterns
-- **[Mobile Application](/mobile/CONTEXT.md)** - *Mobile implementation.* Platform-specific patterns, native integrations, and mobile optimizations
-- **[Admin Dashboard](/admin/CONTEXT.md)** - *Administrative interface.* Permission patterns, admin workflows, and management tools
-
-### Infrastructure Components
-- **[Infrastructure Code](/infrastructure/CONTEXT.md)** - *IaC patterns.* Terraform/CloudFormation templates, resource definitions, and deployment automation
-- **[Monitoring Setup](/monitoring/CONTEXT.md)** - *Observability patterns.* Metrics collection, alerting rules, and dashboard configurations
-
-## Tier 3: Feature-Specific Documentation
-
-Granular CONTEXT.md files co-located with code for minimal cascade effects:
-
-### Backend Feature Documentation
-- **[Core Services](/backend/src/core/services/CONTEXT.md)** - *Business logic patterns.* Service architecture, data processing, integration patterns, and error handling
-- **[API Layer](/backend/src/api/CONTEXT.md)** - *API patterns.* Endpoint design, validation, middleware, and request/response handling
-- **[Data Layer](/backend/src/data/CONTEXT.md)** - *Data patterns.* Database models, queries, migrations, and data access patterns
-- **[Authentication](/backend/src/auth/CONTEXT.md)** - *Auth patterns.* Authentication flows, authorization rules, session management, and security
-- **[Integrations](/backend/src/integrations/CONTEXT.md)** - *External services.* Third-party API clients, webhook handlers, and service adapters
-
-### Frontend Feature Documentation
-- **[UI Components](/frontend/src/components/CONTEXT.md)** - *Component patterns.* Reusable components, styling patterns, accessibility, and composition strategies
-- **[State Management](/frontend/src/store/CONTEXT.md)** - *State patterns.* Global state, local state, data flow, and persistence strategies
-- **[API Client](/frontend/src/api/CONTEXT.md)** - *Client patterns.* HTTP clients, error handling, caching, and data synchronization
-- **[Routing](/frontend/src/routes/CONTEXT.md)** - *Navigation patterns.* Route definitions, guards, lazy loading, and deep linking
-- **[Utilities](/frontend/src/utils/CONTEXT.md)** - *Helper functions.* Formatters, validators, transformers, and common utilities
-
-### Shared Feature Documentation
-- **[Common Types](/shared/src/types/CONTEXT.md)** - *Type definitions.* Shared interfaces, enums, and type utilities
-- **[Validation Rules](/shared/src/validation/CONTEXT.md)** - *Validation patterns.* Schema definitions, custom validators, and error messages
-- **[Constants](/shared/src/constants/CONTEXT.md)** - *Shared constants.* Configuration values, enums, and magic numbers
-- **[Utilities](/shared/src/utils/CONTEXT.md)** - *Shared utilities.* Cross-platform helpers, formatters, and common functions
-
-
-
-## Adding New Documentation
-
-### New Component
-1. Create `/new-component/CONTEXT.md` (Tier 2)
-2. Add entry to this file under appropriate section
-3. Create feature-specific Tier 3 docs as features develop
-
-### New Feature
-1. Create `/component/src/feature/CONTEXT.md` (Tier 3)
-2. Reference parent component patterns
-3. Add entry to this file under component's features
-
-### Deprecating Documentation
-1. Remove obsolete CONTEXT.md files
-2. Update this mapping document
-3. Check for broken references in other docs
-
----
-
-*This documentation architecture template should be customized to match your project's actual structure and components. Add or remove sections based on your architecture.*

package/docs/ai-context/handoff.md

@@ -1,174 +0,0 @@
-# Task Management & Handoff Template
-
-This file manages task continuity, session transitions, and knowledge transfer for AI-assisted development sessions.
-
-## Purpose
-
-This template helps maintain:
-- **Session continuity** between AI development sessions
-- **Task status tracking** for complex, multi-session work
-- **Context preservation** when switching between team members
-- **Knowledge transfer** for project handoffs
-- **Progress documentation** for ongoing development efforts
-
-## Current Session Status
-
-### Active Tasks
-Document currently in-progress work:
-
-```markdown
-## In Progress
-- [ ] Task 1: [Brief description]
-  - Status: [Started/Blocked/Awaiting review]
-  - Context: [Relevant files, decisions made]
-  - Next steps: [What needs to be done next]
-  - Dependencies: [What this task depends on]
-
-- [ ] Task 2: [Brief description]
-  - Status: [Current status]
-  - Files modified: [List of files changed]
-  - Challenges: [Any issues encountered]
-  - Notes: [Important context for continuation]
-```
-
-### Pending Tasks
-Document queued work:
-
-```markdown
-## Pending
-- [ ] Task A: [Description]
-  - Priority: [High/Medium/Low]
-  - Dependencies: [What must be completed first]
-  - Estimated effort: [Time estimate]
-  - Context: [Background information]
-
-- [ ] Task B: [Description]
-  - Priority: [Priority level]
-  - Requirements: [Specific requirements or constraints]
-  - Resources needed: [Tools, access, information needed]
-```
-
-### Completed Tasks
-Track completed work for context:
-
-```markdown
-## Completed This Session
-- [x] Task X: [Description]
-  - Completed: [Date]
-  - Outcome: [What was accomplished]
-  - Files changed: [Modified files]
-  - Notes: [Important decisions or lessons learned]
-
-- [x] Task Y: [Description]
-  - Completed: [Date]
-  - Impact: [How this affects other tasks]
-  - Follow-up needed: [Any follow-up actions required]
-```
-
-## Architecture & Design Decisions
-
-### Recent Decisions
-Document architectural decisions made during development:
-
-```markdown
-## Design Decisions Made
-- **Decision**: [What was decided]
-  - Date: [When decision was made]
-  - Rationale: [Why this approach was chosen]
-  - Alternatives considered: [Other options evaluated]
-  - Impact: [How this affects the system]
-  - Validation: [How to verify this was the right choice]
-
-- **Decision**: [Another decision]
-  - Context: [Situation that led to this decision]
-  - Trade-offs: [What was gained/lost with this choice]
-  - Dependencies: [What this decision depends on]
-```
-
-### Technical Debt & Issues
-Track technical debt and known issues:
-
-```markdown
-## Technical Debt Identified
-- **Issue**: [Description of technical debt]
-  - Location: [Where in codebase]
-  - Impact: [How it affects development/performance]
-  - Proposed solution: [How to address it]
-  - Priority: [When should this be addressed]
-
-- **Issue**: [Another issue]
-  - Root cause: [Why this debt exists]
-  - Workaround: [Current mitigation strategy]
-  - Long-term fix: [Proper solution approach]
-```
-
-## Next Session Goals
-
-### Immediate Priorities
-Define what should be tackled next:
-
-```markdown
-## Next Session Priorities
-1. **Primary Goal**: [Main objective for next session]
-   - Success criteria: [How to know this is complete]
-   - Prerequisites: [What must be ready beforehand]
-   - Estimated effort: [Time estimate]
-
-2. **Secondary Goal**: [Secondary objective]
-   - Dependencies: [What this depends on]
-   - Resources needed: [Tools, information, access required]
-
-3. **If Time Permits**: [Optional tasks]
-   - Context: [Background on why these are valuable]
-   - Preparation: [What needs to be done to start these]
-```
-
-### Knowledge Gaps
-Document areas needing research or clarification:
-
-```markdown
-## Knowledge Gaps to Address
-- **Question**: [What needs to be clarified]
-  - Impact: [How this affects current work]
-  - Research needed: [What investigation is required]
-  - Decision maker: [Who can answer this]
-
-- **Unknown**: [Technical uncertainty]
-  - Options: [Possible approaches to explore]
-  - Experiments: [What should be tested]
-  - Timeline: [When this needs to be resolved]
-```
-
-## Context for Continuation
-
-### Key Files & Components
-Document important files for session continuity:
-
-```markdown
-## Files Currently Being Modified
-- `[file-path]`: [Purpose and current changes]
-- `[file-path]`: [What's being implemented here]
-- `[file-path]`: [Status and next steps]
-
-## Important Context Files
-- `[context-file]`: [Why this is relevant]
-- `[documentation]`: [What information this contains]
-- `[reference]`: [How this relates to current work]
-```
-
-### Development Environment
-Document environment and setup considerations:
-
-```markdown
-## Environment Status
-- **Development setup**: [Current state of dev environment]
-- **Database**: [Schema changes, migrations, data state]
-- **External services**: [API keys, service configurations]
-- **Testing**: [Test suite status, coverage, failing tests]
-- **Build/Deploy**: [Build status, deployment considerations]
-```
-
-
----
-
-*This template provides a comprehensive framework for managing task continuity and knowledge transfer. Customize it based on your team's workflow, project complexity, and communication needs.*

package/docs/ai-context/project-structure.md

@@ -1,160 +0,0 @@
-# Project Structure Template
-
-This document provides a template for documenting the complete technology stack and file tree structure for your project. **AI agents MUST read this file to understand the project organization before making any changes.**
-
-## Technology Stack Template
-
-### Backend Technologies
-Document your backend technology choices:
-- **[Language] [Version]** with **[Package Manager]** - Dependency management and packaging
-- **[Web Framework] [Version]** - Web framework with specific features (async, type hints, etc.)
-- **[Server] [Version]** - Application server configuration
-- **[Configuration] [Version]** - Configuration management approach
-
-Example:
-```
-- Python 3.11+ with Poetry - Dependency management and packaging
-- FastAPI 0.115.0+ - Web framework with type hints and async support
-- Uvicorn 0.32.0+ - ASGI server with standard extras
-- Pydantic Settings 2.5.2+ - Configuration management with type validation
-```
-
-### Integration Services & APIs
-Document external services and integrations:
-- **[Service Name] [API/SDK Version]** - Purpose and usage pattern
-- **[AI Service] [Version]** - AI/ML service integration details
-- **[Database] [Version]** - Data storage and management
-- **[Monitoring] [Version]** - Observability and logging
-
-### Real-time Communication
-Document real-time features:
-- **[WebSocket Library]** - Real-time communication patterns
-- **[HTTP Client]** - Async HTTP communication
-- **[Message Queue]** - Event processing (if applicable)
-
-### Development & Quality Tools
-Document development toolchain:
-- **[Formatter] [Version]** - Code formatting
-- **[Linter] [Version]** - Code quality and linting
-- **[Type Checker] [Version]** - Static type checking
-- **[Testing Framework] [Version]** - Testing approach
-- **[Task Runner]** - Build automation and task orchestration
-
-### Frontend Technologies (if applicable)
-Document frontend technology stack:
-- **[Language] [Version]** - Frontend development language
-- **[Framework] [Version]** - UI framework
-- **[Build Tool] [Version]** - Development and build tooling
-- **[Deployment] [Version]** - Deployment and hosting approach
-
-### Future Technologies
-Document planned technology additions:
-- **[Planned Technology]** - Future integration plans
-- **[Platform]** - Target platform expansion
-- **[Service]** - Planned service integrations
-
-## Complete Project Structure Template
-
-```
-[PROJECT-NAME]/
-├── README.md                           # Project overview and setup
-├── CLAUDE.md                           # Master AI context file
-├── [BUILD-FILE]                        # Build configuration (Makefile, package.json, etc.)
-├── .gitignore                          # Git ignore patterns
-├── .[IDE-CONFIG]/                      # IDE workspace configuration
-│   ├── settings.[ext]                  # IDE settings
-│   ├── extensions.[ext]                # Recommended extensions
-│   └── launch.[ext]                    # Debug configurations
-├── [BACKEND-DIR]/                      # Backend application
-│   ├── CONTEXT.md                      # Backend-specific AI context
-│   ├── src/                            # Source code
-│   │   ├── config/                     # Configuration management
-│   │   │   └── settings.[ext]          # Application settings
-│   │   ├── core/                       # Core business logic
-│   │   │   ├── CONTEXT.md              # Core logic patterns
-│   │   │   ├── services/               # Business services
-│   │   │   │   ├── [service1].[ext]    # Service implementations
-│   │   │   │   └── [service2].[ext]
-│   │   │   ├── models/                 # Data models
-│   │   │   │   ├── [model1].[ext]      # Model definitions
-│   │   │   │   └── [model2].[ext]
-│   │   │   └── utils/                  # Utility functions
-│   │   │       ├── logging.[ext]       # Structured logging
-│   │   │       ├── validation.[ext]    # Input validation
-│   │   │       └── helpers.[ext]       # Helper functions
-│   │   ├── api/                        # API layer
-│   │   │   ├── CONTEXT.md              # API patterns and conventions
-│   │   │   ├── routes/                 # API route definitions
-│   │   │   │   ├── [resource1].[ext]   # Resource-specific routes
-│   │   │   │   └── [resource2].[ext]
-│   │   │   ├── middleware/             # API middleware
-│   │   │   │   ├── auth.[ext]          # Authentication middleware
-│   │   │   │   ├── logging.[ext]       # Request logging
-│   │   │   │   └── validation.[ext]    # Request validation
-│   │   │   └── schemas/                # Request/response schemas
-│   │   │       ├── [schema1].[ext]     # Data schemas
-│   │   │       └── [schema2].[ext]
-│   │   └── integrations/               # External service integrations
-│   │       ├── CONTEXT.md              # Integration patterns
-│   │       ├── [service1]/             # Service-specific integration
-│   │       │   ├── client.[ext]        # API client
-│   │       │   ├── models.[ext]        # Integration models
-│   │       │   └── handlers.[ext]      # Response handlers
-│   │       └── [service2]/
-│   ├── tests/                          # Test suite
-│   │   ├── unit/                       # Unit tests
-│   │   ├── integration/                # Integration tests
-│   │   └── fixtures/                   # Test fixtures and data
-│   ├── [PACKAGE-FILE]                  # Package configuration
-│   └── [ENV-FILE]                      # Environment configuration
-├── [FRONTEND-DIR]/                     # Frontend application (if applicable)
-│   ├── CONTEXT.md                      # Frontend-specific AI context
-│   ├── src/                            # Source code
-│   │   ├── components/                 # UI components
-│   │   │   ├── CONTEXT.md              # Component patterns
-│   │   │   ├── common/                 # Shared components
-│   │   │   └── [feature]/              # Feature-specific components
-│   │   ├── pages/                      # Page components/routes
-│   │   │   ├── [page1].[ext]           # Page implementations
-│   │   │   └── [page2].[ext]
-│   │   ├── stores/                     # State management
-│   │   │   ├── CONTEXT.md              # State management patterns
-│   │   │   ├── [store1].[ext]          # Store implementations
-│   │   │   └── [store2].[ext]
-│   │   ├── api/                        # API client layer
-│   │   │   ├── CONTEXT.md              # Client patterns
-│   │   │   ├── client.[ext]            # HTTP client setup
-│   │   │   └── endpoints/              # API endpoint definitions
-│   │   ├── utils/                      # Utility functions
-│   │   │   ├── logging.[ext]           # Client-side logging
-│   │   │   ├── validation.[ext]        # Form validation
-│   │   │   └── helpers.[ext]           # Helper functions
-│   │   └── assets/                     # Static assets
-│   ├── tests/                          # Frontend tests
-│   ├── [BUILD-CONFIG]                  # Build configuration
-│   └── [PACKAGE-FILE]                  # Package configuration
-├── docs/                               # Documentation
-│   ├── ai-context/                     # AI-specific documentation
-│   │   ├── project-structure.md        # This file
-│   │   ├── docs-overview.md            # Documentation architecture
-│   │   ├── system-integration.md       # Integration patterns
-│   │   ├── deployment-infrastructure.md # Infrastructure docs
-│   │   └── handoff.md                  # Task management
-│   ├── api/                            # API documentation
-│   ├── deployment/                     # Deployment guides
-│   └── development/                    # Development guides
-├── scripts/                            # Automation scripts
-│   ├── setup.[ext]                     # Environment setup
-│   ├── deploy.[ext]                    # Deployment scripts
-│   └── maintenance/                    # Maintenance scripts
-├── [INFRASTRUCTURE-DIR]/               # Infrastructure as code (if applicable)
-│   ├── [PROVIDER]/                     # Cloud provider configurations
-│   ├── docker/                         # Container configurations
-│   └── monitoring/                     # Monitoring and alerting
-└── [CONFIG-FILES]                      # Root-level configuration files
-```
-
-
----
-
-*This template provides a comprehensive foundation for documenting project structure. Adapt it based on your specific technology stack, architecture decisions, and organizational requirements.*