@zenuml/core 3.46.2 → 3.46.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zenuml/core",
-  "version": "3.46.2",
+  "version": "3.46.4",
   "private": false,
   "license": "MIT",
   "repository": {

package/docs/CONTEXT-tier2-component.md

@@ -1,96 +0,0 @@
-# [COMPONENT NAME] - Component Context (Tier 2)
-
-> **Note**: This is component-specific context. See root **CLAUDE.md** for master project context and coding standards.
-
-## Purpose
-[Brief description of this component's role in the system. What problem does it solve and how does it fit into the overall architecture?]
-
-## Current Status: [Status Description] ✅/🚧/📋
-[Current implementation state, what's working, what's in progress, and key milestones achieved]
-
-## Component-Specific Development Guidelines
-- **[Technology/Framework]**: [Specific technology requirements for this component]
-- **[Architecture Pattern]**: [Component-specific architectural approach]
-- **[Code Organization]**: [How code should be structured within this component]
-- **[Integration Patterns]**: [How this component integrates with others]
-- **[Quality Standards]**: [Component-specific quality requirements]
-
-## Key Component Structure
-
-### Core Modules (`[path]/`)
-- **[module1]/** - [Purpose and key functionality]
-  - **[file1].[ext]** - [Specific file purpose and key features]
-  - **[file2].[ext]** - [Specific file purpose and key features]
-- **[module2]/** - [Purpose and key functionality]  
-- **[module3]/** - [Purpose and key functionality]
-
-### [Secondary Structure] (`[path]/`)
-- **[component].[ext]** - [Component purpose and architecture pattern]
-- **[utilities].[ext]** - [Utility functions and helpers]
-- **[config].[ext]** - [Configuration and settings management]
-
-### [Integration Layer] (`[path]/`)
-- **[integration1].[ext]** - [External service integration patterns]
-- **[integration2].[ext]** - [Inter-component communication]
-
-## Implementation Highlights
-
-### [Key Feature 1]
-- **[Technical Implementation]**: [How this feature is implemented]
-- **[Architecture Decision]**: [Why this approach was chosen]
-- **[Performance Considerations]**: [Optimization details]
-- **[Integration Points]**: [How it connects to other components]
-
-### [Key Feature 2]  
-- **[Implementation Pattern]**: [Technical implementation approach]
-- **[Quality Measures]**: [Testing, monitoring, error handling]
-- **[Scalability Considerations]**: [How it handles growth/load]
-
-### [Key Feature 3]
-- **[Technical Details]**: [Implementation specifics]
-- **[Dependencies]**: [External dependencies and integration points]
-- **[Configuration]**: [How it's configured and customized]
-
-## Critical Implementation Details
-
-### [Technical Pattern 1]
-**[Pattern Description]**: [What problem this pattern solves]
-
-```[language]
-// Example implementation showing the pattern
-[code example demonstrating the critical implementation]
-```
-
-### [Technical Pattern 2]  
-**[Architecture Decision]**: [Why this approach was chosen]
-
-```[language]
-// Code example showing architecture implementation
-[code example demonstrating the architecture]
-```
-
-### [Integration Pattern]
-**[Integration Description]**: [How this component integrates with others]
-
-```[language]
-// Integration implementation example  
-[code example showing integration patterns]
-```
-
-## Development Notes
-
-### [Current Challenges]
-- **[Challenge 1]**: [Description and current approach]
-- **[Challenge 2]**: [Description and mitigation strategy]
-
-### [Future Considerations]
-- **[Enhancement 1]**: [Planned improvement and rationale]
-- **[Enhancement 2]**: [Future architectural evolution]
-
-### [Performance Metrics]
-- **[Key Metric 1]**: [Current performance and targets]
-- **[Key Metric 2]**: [Monitoring and optimization approach]
-
----
-
-*This component documentation provides context for AI-assisted development within [COMPONENT NAME]. For system-wide patterns and standards, reference the master CLAUDE.md file.*

package/docs/CONTEXT-tier3-feature.md

@@ -1,162 +0,0 @@
-# [FEATURE NAME] Documentation (Tier 3)
-
-*This file documents [feature/module] patterns, architectural decisions, and implementations within [component name].*
-
-## [Feature] Architecture Overview
-
-### [Architecture Decision Title]
-
-**Context**: [Situation that led to this architectural decision]
-
-**Decision**: [What was decided and implemented]
-
-**Reasoning**:
-- **[Benefit 1]**: [Why this approach provides this benefit]
-- **[Benefit 2]**: [Technical or business advantage]  
-- **[Benefit 3]**: [Performance or maintainability benefit]
-- **[Benefit 4]**: [Developer experience or operational benefit]
-
-**Consequences**:
-- [Positive outcome from this decision]
-- [Technical improvement achieved]
-- [Operational or maintenance benefit]
-- [User experience enhancement]
-
-## [Feature] Implementation Patterns
-
-### [Implementation Pattern 1]
-
-**File Organization**:
-```
-[feature-directory]/
-├── [file1].[ext]      # [Purpose and responsibility]
-├── [file2].[ext]      # [Purpose and responsibility]  
-├── [file3].[ext]      # [Purpose and responsibility]
-└── [file4].[ext]      # [Purpose and responsibility]
-```
-
-**Architecture Benefits**:
-- **[Benefit 1]**: [How this organization provides this benefit]
-- **[Benefit 2]**: [Technical advantage of this structure]
-- **[Benefit 3]**: [Maintainability or scalability benefit]
-- **[Benefit 4]**: [Developer experience improvement]
-
-### [Implementation Pattern 2]
-
-**Architecture Decision**: [Technical approach taken]
-
-**Context**: [Background and requirements that led to this approach]
-
-**Decision**: [Specific implementation choice made]
-
-**Reasoning**:
-- **[Technical Reason]**: [Why this was the best technical choice]
-- **[Performance Reason]**: [Performance benefits]
-- **[Maintainability Reason]**: [Long-term maintenance benefits]
-- **[Integration Reason]**: [How it integrates with other components]
-
-**Implementation Details**:
-```[language]
-// [Description of what this code demonstrates]
-[detailed code example showing the implementation pattern]
-```
-
-### [Implementation Pattern 3]
-
-**[Pattern Name]**: [Description of the pattern]
-
-```[language]
-// [Code example title]
-[comprehensive code example showing the pattern in action]
-```
-
-**Implementation Benefits**:
-- **[Benefit 1]**: [Specific advantage this implementation provides]
-- **[Benefit 2]**: [Performance or reliability improvement]
-- **[Benefit 3]**: [Developer experience enhancement]
-
-## [Technical Domain] Implementation
-
-### [Technical Feature 1]
-
-**[Feature Description]**: [What this feature does and why it's important]
-
-**Architecture Pattern**:
-```[language]
-// [Description of the architectural approach]
-[code example demonstrating the architecture]
-```
-
-**Key Implementation Details**:
-- **[Detail 1]**: [Important implementation consideration]
-- **[Detail 2]**: [Technical constraint or optimization]
-- **[Detail 3]**: [Integration or performance consideration]
-
-### [Technical Feature 2]
-
-**Implementation Approach**: [How this feature is implemented]
-
-```[language]
-// [Code example description]
-[detailed implementation example]
-```
-
-**Technical Considerations**:
-- **[Consideration 1]**: [Important technical factor]
-- **[Consideration 2]**: [Performance or scalability factor]
-- **[Consideration 3]**: [Maintenance or testing consideration]
-
-## [Integration/Communication] Patterns
-
-### [Integration Pattern 1]
-
-**Context**: [When and why this integration pattern is used]
-
-**Implementation**:
-```[language]
-// [Integration example description]
-[code showing integration implementation]
-```
-
-**Benefits**:
-- **[Integration Benefit 1]**: [How this improves system integration]
-- **[Integration Benefit 2]**: [Performance or reliability improvement]
-
-### [Integration Pattern 2]
-
-**Pattern Description**: [What problem this integration pattern solves]
-
-```[language]
-// [Integration code example]
-[implementation showing integration pattern]
-```
-
-## Performance & Optimization Details
-
-### [Performance Optimization 1]
-**Optimization**: [What was optimized and how]
-- **Before**: [Previous performance characteristics]
-- **After**: [Improved performance metrics]
-- **Implementation**: [How the optimization was achieved]
-
-### [Performance Optimization 2]  
-**Technical Improvement**: [Specific performance enhancement]
-- **Impact**: [Measurable improvement achieved]
-- **Method**: [Technical approach used]
-- **Trade-offs**: [Any compromises made for the optimization]
-
-## Error Handling & Edge Cases
-
-### [Error Scenario 1]
-**Scenario**: [What error condition this handles]
-**Handling**: [How the error is detected and managed]
-**Recovery**: [How the system recovers from this error]
-
-### [Error Scenario 2]
-**Edge Case**: [Unusual condition that needs handling]  
-**Solution**: [How the implementation handles this case]
-**Validation**: [How this handling is tested or verified]
-
----
-
-*This feature documentation provides detailed implementation context for AI-assisted development. For broader component context, see the component-level CONTEXT.md file.*

package/docs/README.md

@@ -1,207 +0,0 @@
-# Documentation System Guide
-
-This guide explains how the 3-tier documentation architecture powers the Claude Code Development Kit and why it provides superior results compared to traditional documentation approaches.
-
-## Critical Foundation Files
-
-Two files form the cornerstone of the entire documentation system:
-
-1. **docs-overview.md** - The central routing guide that directs AI agents to appropriate documentation based on task complexity. This file maps your entire documentation structure and enables intelligent context loading.
-
-2. **project-structure.md** - The comprehensive overview of your project's complete file structure and technology stack. This file is required reading for all AI agents and must be attached to Gemini consultations.
-
-These foundation files ensure AI agents always have the essential context needed to understand your project and navigate to relevant documentation.
-
-## Why the 3-Tier System
-
-### Traditional Documentation Problems
-
-Standard documentation approaches create friction for AI-assisted development:
-
-- **Context Overload** - AI agents must process entire documentation sets for simple tasks
-- **Maintenance Burden** - Every code change cascades to multiple documentation locations
-- **Stale Content** - Documentation diverges from implementation reality
-- **No AI Optimization** - Human-readable formats lack structure for machine processing
-
-### The 3-Tier Solution
-
-The kit solves these problems through hierarchical organization:
-
-**Tier 1: Foundation (Rarely Changes)**
-- Project-wide standards, architecture decisions, technology stack
-- Auto-loads for every AI session
-- Provides consistent baseline without redundancy
-- Uses CLAUDE.md as the master context file
-
-**Tier 2: Component (Occasionally Changes)**
-- Component boundaries, architectural patterns, integration points
-- Loads only when working within specific components
-- Isolates architectural decisions from implementation details
-- Uses CONTEXT.md files at component roots
-
-**Tier 3: Feature (Frequently Changes)**
-- Implementation specifics, technical details, local patterns
-- Co-located with code for immediate updates
-- Minimizes documentation cascade when code changes
-- Uses CONTEXT.md files within feature directories
-
-## Benefits vs Traditional Systems
-
-### 1. Intelligent Context Loading
-
-**Traditional**: AI loads entire documentation corpus regardless of task
-**3-Tier**: Commands load only relevant tiers based on complexity
-
-Example:
-- Simple query → Tier 1 only (minimal tokens)
-- Component work → Tier 1 + relevant Tier 2
-- Deep implementation → All relevant tiers
-
-### 2. Maintenance Efficiency
-
-**Traditional**: Update multiple documents for each change
-**3-Tier**: Updates isolated to appropriate tier
-
-Example:
-- API endpoint change → Update only Tier 3 API documentation
-- New component → Add Tier 2 documentation, Tier 1 unchanged
-- Coding standard → Update only Tier 1, applies everywhere
-
-### 3. AI Performance Optimization
-
-**Traditional**: AI struggles to find relevant information
-**3-Tier**: Structured hierarchy guides AI to precise context
-
-The system provides:
-- Clear routing logic for agent navigation
-- Predictable documentation locations
-- Efficient token usage through targeted loading
-
-## Integration with Kit Components
-
-### Command Integration
-
-Commands leverage the 3-tier structure for intelligent operation:
-
-```
-Command Execution → Analyze Task Complexity → Load Appropriate Tiers
-                                            ↓
-                                   Simple: Tier 1 only
-                                   Component: Tiers 1-2
-                                   Complex: All relevant tiers
-```
-
-### MCP Server Integration
-
-External AI services receive proper context through the tier system:
-
-- **Gemini Consultations** - Auto-attach `project-structure.md` (Tier 1)
-- **Context7 Lookups** - Happen within established project context
-- **Recommendations** - Align with documented architecture
-
-### Multi-Agent Routing
-
-The documentation structure determines agent behavior:
-
-- Number of agents spawned based on tiers involved
-- Each agent receives targeted documentation subset
-- Parallel analysis without context overlap
-
-## Key Files and Their Roles
-
-### Foundation Files (ai-context/)
-
-**docs-overview.md**
-- Template for implementing 3-tier documentation
-- Maps documentation structure for AI navigation
-- [View Template](ai-context/docs-overview.md)
-
-**project-structure.md**
-- Complete technology stack and file organization
-- Required reading for all AI agents
-- Auto-attaches to Gemini consultations
-- [View Template](ai-context/project-structure.md)
-
-**system-integration.md**
-- Cross-component communication patterns
-- Integration architectures for multi-agent analysis
-- [View Template](ai-context/system-integration.md)
-
-**deployment-infrastructure.md**
-- Infrastructure patterns and constraints
-- Deployment context for AI recommendations
-- [View Template](ai-context/deployment-infrastructure.md)
-
-**handoff.md**
-- Session continuity between AI interactions
-- Task state preservation
-- [View Template](ai-context/handoff.md)
-
-### Context Templates
-
-**CLAUDE.md** (Tier 1)
-- Master AI context with coding standards
-- Project-wide instructions and patterns
-- [View Template](CLAUDE.md)
-
-**CONTEXT-tier2-component.md**
-- Component-level architectural context
-- [View Template](CONTEXT-tier2-component.md)
-
-**CONTEXT-tier3-feature.md**
-- Feature-specific implementation details
-- [View Template](CONTEXT-tier3-feature.md)
-
-## Implementation Strategy
-
-### 1. Start with Templates
-
-Use provided templates as foundation:
-- Copy and customize for your project
-- Maintain consistent structure
-- Focus on AI-consumable formatting
-
-### 2. Follow Natural Boundaries
-
-Let your architecture guide tier placement:
-- Stable decisions → Tier 1
-- Component design → Tier 2
-- Implementation details → Tier 3
-
-### 3. Co-locate Documentation
-
-Place CONTEXT.md files with related code:
-```
-backend/
-├── CONTEXT.md         # Backend architecture (Tier 2)
-└── src/
-    └── api/
-        └── CONTEXT.md # API implementation (Tier 3)
-```
-
-### 4. Maintain Hierarchy
-
-Ensure clear relationships:
-- Tier 3 references Tier 2 patterns
-- Tier 2 follows Tier 1 standards
-- No circular dependencies
-
-### 5. Use Documentation Commands
-
-The kit provides commands to manage documentation:
-- **`/create-docs`** - Generate initial documentation structure for projects without existing docs
-- **`/update-docs`** - Regenerate and update documentation after code changes to keep everything current
-
-## Measuring Success
-
-The 3-tier system succeeds when:
-
-1. **AI agents find context quickly** - No searching through irrelevant documentation
-2. **Updates stay localized** - Changes don't cascade unnecessarily
-3. **Documentation stays current** - Co-location ensures updates happen
-4. **Commands work efficiently** - Appropriate context loads automatically
-5. **MCP servers provide relevant advice** - External AI understands your project
-
----
-
-*Part of the Claude Code Development Kit - see [main documentation](../README.md) for complete system overview.*

package/docs/module-vs-main-in-package-json.md

@@ -1,17 +0,0 @@
-The `module` field is not officially defined by Node.js and support is not planned.
-Instead, the Node.js community settled on package `exports` which they believe is
-more versatile.
-
-For practical reasons JavaScript bundlers will continue support the `module` field.
-The esbuild docs [explain](https://esbuild.github.io/api/#main-fields)
-when to use `module` as well as related fields like `main` and `browser`.
-
-
-* `main` is the standard field for all packages that are mean to be used with node.
-It is reasonable to expect that the file path in this field is a valid CommonJS module.
-* `module` is a non-standard field that is used to integrate ECMAScript modules into
-node. It is reasonable to expect that the file path in this field is an ECMAScript module (esm).
-
-For @zenuml/core, the `main` field is set to `dist/zenuml.js` and the `module` field
-is set to `dist/zenuml.esm.js`.
-

package/docs/open-issues/example-api-performance-issue.md

@@ -1,79 +0,0 @@
-# API Performance Issue - Example Template
-
-## Issue Description
-
-Describe the specific performance issue or bug that needs to be addressed. Include symptoms, affected features, and user impact.
-
-Example: "API endpoint `/api/data/process` has intermittent high latency (>5 seconds) under normal load conditions, causing user timeout errors."
-
-## Root Cause
-
-Detailed analysis of what's causing the issue. Include:
-- Technical root cause
-- Contributing factors
-- System conditions that trigger the issue
-
-Example: "Database query optimization needed for complex joins. Current query scans entire table without proper indexing."
-
-## Impact Assessment
-
-- **Severity**: Critical/High/Medium/Low
-- **Affected Users**: Percentage or number of users impacted
-- **Business Impact**: Revenue, user experience, or operational impact
-- **Workarounds**: Any temporary solutions currently in place
-
-## Proposed Solution
-
-### Technical Approach
-Detailed technical solution including:
-- Code changes required
-- Architecture modifications
-- Database schema updates
-- Performance improvements expected
-
-### Implementation Plan
-1. **Phase 1**: Initial fixes (timeline)
-2. **Phase 2**: Optimization improvements (timeline)
-3. **Phase 3**: Monitoring and validation (timeline)
-
-## Testing Strategy
-
-- **Unit Tests**: Specific test cases to validate the fix
-- **Integration Tests**: End-to-end testing scenarios
-- **Performance Tests**: Load testing and benchmarking
-- **Regression Tests**: Ensure no existing functionality breaks
-
-## Related Files
-
-List all files that need to be modified:
-- `src/api/routes/data.py` - Main endpoint logic
-- `src/database/models.py` - Database model updates
-- `src/utils/query_optimizer.py` - Query optimization utilities
-- `tests/test_api_performance.py` - Performance test suite
-
-## References
-
-- [External documentation or APIs]
-- [Related GitHub issues or PRs]
-- [Performance benchmarking results]
-- [Stack Overflow discussions or solutions]
-
-## Status
-
-- [ ] **Open** - Issue identified and documented
-- [ ] **In Progress** - Solution being implemented
-- [ ] **Testing** - Fix implemented, undergoing testing
-- [ ] **Fixed** - Issue resolved and deployed
-- [ ] **Closed** - Issue confirmed resolved in production
-
-## Implementation Notes
-
-Track progress and implementation details:
-- Date started: [DATE]
-- Key decisions made: [DECISIONS]
-- Challenges encountered: [CHALLENGES]
-- Performance improvements achieved: [METRICS]
-
----
-
-*This template provides a structured approach to documenting and tracking technical issues. Customize sections based on your project's specific needs and workflow.*

package/docs/osx-unsupported-arm64-node12.md

@@ -1,13 +0,0 @@
-Error when running 'bun run build'
-
-```shell
- ERROR  Failed to compile with 1 error                                                                                                                                                                                       10:15:37 AM
-
- error  in ./src/components/theme-blue-river.scss
-
-Syntax Error: ModuleError: Module Error (from ./node_modules/sass-loader/dist/cjs.js):
-Missing binding /Users/pengxiao/workspaces/zenuml/vue-sequence/node_modules/node-sass/vendor/darwin-x64-83/binding.node
-Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 14.x
-```
-
-Remove 'node_modules' and re-run 'bun run build' under node 14.

package/docs/running-cypress-tests-locally.md

@@ -1,76 +0,0 @@
-# Running Cypress Tests Locally
-
-This document explains how to run Cypress tests locally on your machine, with a focus on ensuring color profiles match those used in GitHub Actions for consistent visual testing results.
-
-## Running Tests
-
-You can run Cypress tests using the following commands:
-
-- Run all tests headlessly:
-
-```bash
-pnpm cy
-```
-
-- Run a specific test file:
-
-```bash
-pnpm cypress run --spec "cypress/e2e/smoke.spec.js"
-```
-
-## Color Profile Configuration
-
-### Why Color Profiles Matter
-
-Visual regression tests in Cypress compare screenshots pixel-by-pixel. Different color profiles can cause the same UI to render with slightly different colors, leading to false test failures. To match the GitHub Actions environment, we use the sRGB color profile.
-
-### Automatic Configuration
-
-Our Cypress configuration automatically forces the sRGB color profile when running tests. This is configured in `cypress/plugins/index.js` with the following code:
-
-```javascript
-on("before:browser:launch", (browser = {}, launchOptions) => {
-  if (browser.family === "chromium" && browser.name !== "electron") {
-    launchOptions.args.push("--force-color-profile=srgb");
-  }
-});
-```
-
-### Configuring macOS Color Profile
-
-For the most consistent results, you should also configure your macOS system to use the sRGB color profile:
-
-1. Open System Preferences (or System Settings on newer macOS versions)
-2. Go to "Displays"
-3. Select the "Color" tab
-4. Click "Calibrate" to open the Display Calibrator Assistant
-5. Follow the wizard and when prompted for a color profile, select "sRGB"
-6. Complete the calibration and save the profile
-
-Alternatively, you can directly select an existing sRGB profile:
-
-1. Open System Preferences > Displays > Color
-2. From the list of color profiles, select "sRGB IEC61966-2.1" or a similar sRGB profile
-3. Click "Apply"
-
-## Troubleshooting Visual Test Failures
-
-If you encounter visual test failures despite using the sRGB profile:
-
-1. Check that your display brightness is set to a consistent level
-2. Ensure you're using the same browser version as GitHub Actions (Chrome)
-3. Verify that your OS theme/appearance settings match the CI environment (light mode is recommended)
-4. If necessary, adjust the threshold in the image snapshot configuration:
-
-```javascript
-cy.document().toMatchImageSnapshot({
-  imageConfig: { threshold: 0.012 }, // Increase this value if needed
-  capture: "viewport",
-});
-```
-
-## Additional Resources
-
-- [Cypress Image Snapshot Documentation](https://github.com/jaredpalmer/cypress-image-snapshot)
-- [Chrome Command Line Switches](https://peter.sh/experiments/chromium-command-line-switches/)
-- [macOS Color Management Guide](https://support.apple.com/guide/mac-help/calibrate-your-display-mchlp2920/mac)