@zenuml/core 3.33.0 → 3.34.0

package/.kiro/hooks/README.md

@@ -0,0 +1,38 @@
+# Kiro Agent Hooks
+
+This directory contains custom hooks that automatically execute when specific events occur in Kiro.
+
+## Session Sound Notification Hook
+
+**File:** `session-sound-notification.json` and `session-sound-notification.js`
+
+**Purpose:** Plays system sounds to notify you when:
+
+- An AI session completes
+- User input is required to continue
+- An error occurs
+
+**Sounds Used (macOS):**
+
+- **Session Complete:** Glass.aiff - A pleasant chime when tasks finish
+- **Input Required:** Sosumi.aiff - An attention-getting sound when you need to respond
+- **Error:** Basso.aiff - A distinctive sound for errors
+- **Default:** Ping.aiff - Fallback sound
+
+**Configuration:**
+The hook is enabled by default and will auto-execute. You can disable it by setting `"enabled": false` in the JSON configuration file.
+
+**Platform Notes:**
+
+- Currently optimized for macOS using the `afplay` command
+- Uses built-in system sounds located in `/System/Library/Sounds/`
+- For other platforms, the sound files and playback command would need to be adjusted
+
+## Managing Hooks
+
+You can:
+
+1. View current hooks in the Kiro Explorer under "Agent Hooks"
+2. Use Command Palette → "Open Kiro Hook UI" to create new hooks
+3. Edit hook files directly in this directory
+4. Enable/disable hooks by modifying the `enabled` property

package/.kiro/hooks/session-sound-notification.js

@@ -0,0 +1,44 @@
+/**
+ * Session Sound Notification Hook
+ * Plays a sound when sessions end or user input is required
+ */
+
+const playSound = (soundType = 'default') => {
+  // For macOS, we can use the 'afplay' command to play system sounds
+  const sounds = {
+    default: '/System/Library/Sounds/Ping.aiff',
+    complete: '/System/Library/Sounds/Glass.aiff',
+    attention: '/System/Library/Sounds/Sosumi.aiff',
+    error: '/System/Library/Sounds/Basso.aiff'
+  };
+  
+  const soundFile = sounds[soundType] || sounds.default;
+  
+  try {
+    // Use afplay to play the sound on macOS
+    require('child_process').exec(`afplay "${soundFile}"`, (error) => {
+      if (error) {
+        console.log('Could not play sound:', error.message);
+      }
+    });
+  } catch (err) {
+    console.log('Sound playback failed:', err.message);
+  }
+};
+
+module.exports = {
+  onSessionEnd: () => {
+    console.log('🔊 Session completed - playing completion sound');
+    playSound('complete');
+  },
+  
+  onUserInputRequired: () => {
+    console.log('🔊 User input needed - playing attention sound');
+    playSound('attention');
+  },
+  
+  onError: () => {
+    console.log('🔊 Error occurred - playing error sound');
+    playSound('error');
+  }
+};

package/.kiro/hooks/session-sound-notification.json

@@ -0,0 +1,23 @@
+{
+  "name": "Session Sound Notification",
+  "description": "Plays a sound when a session ends or user input is needed",
+  "triggers": [
+    {
+      "event": "session.end",
+      "description": "Triggered when an AI session completes"
+    },
+    {
+      "event": "user.input.required",
+      "description": "Triggered when the AI needs user input to continue"
+    }
+  ],
+  "actions": [
+    {
+      "type": "system.sound",
+      "sound": "notification",
+      "description": "Play system notification sound"
+    }
+  ],
+  "enabled": true,
+  "autoExecute": true
+}

package/DEPLOYMENT.md

@@ -0,0 +1,62 @@
+# ZenUML Web Renderer Deployment
+
+This document describes the deployment process for the ZenUML Web Renderer to Cloudflare Pages.
+
+## Deployment Strategy
+
+- **Production**: Deploys from `main` branch to `zenuml-web-renderer` project
+- **Staging**: Deploys from any non-main branch to `zenuml-web-renderer-staging` project
+
+## GitHub Actions Workflow
+
+The deployment is automated through GitHub Actions (`.github/workflows/cloudflare-pages.yml`):
+
+1. **Triggers**: 
+   - Push to `main` or `feat/public-renderer` branches
+   - Pull requests to `main` branch
+   - Only when relevant files are changed (renderer.html, public/**, src/**, etc.)
+
+2. **Build Process**:
+   - Install dependencies with pnpm
+   - Build the site using `pnpm build:site`
+   - Deploy to appropriate Cloudflare Pages project
+
+## Required Secrets
+
+Add these secrets to your GitHub repository settings:
+
+- `CLOUDFLARE_API_TOKEN`: Cloudflare API token with Pages permissions
+- `CLOUDFLARE_ACCOUNT_ID`: Your Cloudflare account ID
+
+## Manual Deployment
+
+You can also deploy manually using wrangler:
+
+```bash
+# Deploy to staging
+pnpm pages:deploy:staging
+
+# Deploy to production  
+pnpm pages:deploy
+```
+
+## Project Structure
+
+- `renderer.html`: Main renderer page (root level)
+- `public/renderer.html`: Copy of renderer page for static hosting
+- `dist/`: Build output directory (created by `pnpm build:site`)
+- `wrangler.toml`: Cloudflare configuration
+
+## URLs
+
+- **Production**: `https://zenuml-web-renderer.pages.dev`
+- **Staging**: `https://zenuml-web-renderer-staging.pages.dev`
+
+## Usage
+
+Once deployed, you can use the renderer by visiting:
+- `https://your-domain.pages.dev/renderer.html`
+- `https://your-domain.pages.dev/` (if configured as index)
+
+Future URL parameter support will allow:
+- `https://your-domain.pages.dev/renderer.html?code=<base64-encoded-zenuml>`