een-api-toolkit 0.3.79 → 0.3.81

package/.claude/agents/een-auth-agent.md

@@ -254,22 +254,24 @@ The EEN OAuth login page uses a **two-step authentication flow**:
 1. **Step 1 - Email**: User enters email address and clicks "Next"
 2. **Step 2 - Password**: Password field appears, user enters password and clicks "Sign in"
 
-This is important for Playwright tests - you cannot fill both fields at once:
+This is important for Playwright tests - you cannot fill both fields at once.
+
+**BEST PRACTICE:** Use `getByPlaceholder()` selectors — they are the most reliable across EEN login page versions:
 
 ```typescript
 // Playwright test example for EEN two-step login
 // Step 1: Enter email and click Next
-const emailInput = page.locator('input[type="email"], input[type="text"]').first()
-await emailInput.fill(TEST_USER)
+await page.getByPlaceholder(/email/i).fill(TEST_USER)
 await page.getByRole('button', { name: /next/i }).click()
 
 // Step 2: Wait for password field and fill it
-const passwordInput = page.locator('input[type="password"]')
-await passwordInput.waitFor({ state: 'visible', timeout: 10000 })
-await passwordInput.fill(TEST_PASSWORD)
-await page.getByRole('button', { name: /sign in/i }).click()
+await page.getByPlaceholder(/password/i).fill(TEST_PASSWORD, { timeout: 15000 })
+await page.getByRole('button', { name: /sign in|next/i }).click()
 ```
 
+**NOTE:** The `#authentication--input__email` and `#authentication--input__password` ID selectors
+may not always be present. The `getByPlaceholder()` approach is more reliable.
+
 ## Playwright E2E Test Patterns
 
 **Reference examples in:** `node_modules/een-api-toolkit/examples/*/e2e/auth.spec.ts`
@@ -283,27 +285,22 @@ Best practices for auth testing:
 ```typescript
 // Complete performLogin helper function
 async function performLogin(page: Page, username: string, password: string): Promise<void> {
-  await page.goto('/login')
-  await page.click('button:has-text("Login with Eagle Eye Networks")')
+  await page.goto('/')
+  await page.getByRole('link', { name: 'Login' }).click()
 
   // Wait for EEN OAuth page
-  await page.waitForURL(/.*eagleeyenetworks.com.*/, { timeout: 30000 })
+  await page.waitForURL(/auth\.eagleeyenetworks\.com|id\.eagleeyenetworks\.com/, { timeout: 15000 })
 
-  // Step 1: Email
-  const emailInput = page.locator('#authentication--input__email, input[type="email"]').first()
-  await emailInput.waitFor({ state: 'visible', timeout: 15000 })
-  await emailInput.fill(username)
-  await page.getByRole('button', { name: 'Next' }).click()
+  // Step 1: Email (use getByPlaceholder - most reliable selector)
+  await page.getByPlaceholder(/email/i).fill(username)
+  await page.getByRole('button', { name: /next/i }).click()
 
-  // Step 2: Password
-  const passwordInput = page.locator('#authentication--input__password, input[type="password"]')
-  await passwordInput.waitFor({ state: 'visible', timeout: 10000 })
-  await passwordInput.fill(password)
-  await page.locator('#next, button:has-text("Sign in")').first().click()
+  // Step 2: Password (appears after Next is clicked)
+  await page.getByPlaceholder(/password/i).fill(password, { timeout: 15000 })
+  await page.getByRole('button', { name: /sign in|next/i }).click()
 
   // Wait for redirect back to app
-  await page.waitForURL(/127\.0\.0\.1:3333/, { timeout: 60000 })
-  await page.waitForURL('**/', { timeout: 60000 })
+  await page.waitForURL('http://127.0.0.1:3333/**', { timeout: 30000 })
 }
 
 // Clear auth state helper

package/.claude/agents/een-events-agent.md

@@ -381,22 +381,32 @@ async function fetchNotifications() {
 4. **Cleanup** - Delete subscription when done (or it auto-expires after 15 min of inactivity)
 
 ### createEventSubscription()
+
+**CRITICAL: The subscription API uses nested `deliveryConfig` and `filters` structures, NOT flat params.**
+
 ```typescript
+import { ref, onUnmounted } from 'vue'
 import {
   createEventSubscription,
   connectToEventSubscription,
   deleteEventSubscription,
-  type CreateEventSubscriptionParams
+  type SSEEvent,
+  type SSEConnection,
+  type SSEConnectionStatus
 } from 'een-api-toolkit'
 
+const sseConnection = ref<SSEConnection | null>(null)
 const subscriptionId = ref<string | null>(null)
-const sseConnection = ref<EventSource | null>(null)
 
-async function startRealTimeEvents(cameraId: string) {
+async function startRealTimeEvents(cameraId: string, eventTypes: string[]) {
   // Step 1: Create subscription
+  // IMPORTANT: types must be objects with { id: string }, not plain strings
   const result = await createEventSubscription({
-    actors: [`camera:${cameraId}`],
-    types: ['een.motionDetectionEvent.v1', 'een.objectDetectionEvent.v1']
+    deliveryConfig: { type: 'serverSentEvents.v1' },
+    filters: [{
+      actors: [`camera:${cameraId}`],
+      types: eventTypes.map(t => ({ id: t }))
+    }]
   })
 
   if (result.error) {
@@ -406,34 +416,54 @@ async function startRealTimeEvents(cameraId: string) {
 
   subscriptionId.value = result.data.id
 
-  // Step 2: Connect to SSE stream
-  const connection = connectToEventSubscription(result.data.sseUrl, {
-    onEvent: (event) => {
-      console.log('Real-time event:', event)
-      // Add to events list, show notification, etc.
+  // Step 2: Extract SSE URL from deliveryConfig (NOT from result.data.sseUrl)
+  const sseUrl = result.data.deliveryConfig.type === 'serverSentEvents.v1'
+    ? result.data.deliveryConfig.sseUrl
+    : undefined
+
+  if (!sseUrl) return
+
+  // Step 3: Connect to SSE stream
+  // IMPORTANT: Returns a Result type { data, error }, NOT the connection directly
+  const connectionResult = connectToEventSubscription(sseUrl, {
+    onEvent: (event: SSEEvent) => {
+      console.log('Real-time event:', event.type, event.startTimestamp)
     },
-    onError: (error) => {
-      console.error('SSE error:', error)
+    onError: (err: Error) => {
+      console.error('SSE error:', err.message)
     },
-    onOpen: () => {
-      console.log('SSE connection opened')
+    onStatusChange: (status: SSEConnectionStatus) => {
+      // status: 'connected' | 'connecting' | 'disconnected' | 'error'
+      console.log('SSE status:', status)
     }
   })
 
-  sseConnection.value = connection
+  if (connectionResult.error) {
+    console.error('Failed to connect:', connectionResult.error.message)
+    return
+  }
+
+  sseConnection.value = connectionResult.data
 }
 
-// Cleanup when component unmounts
-onUnmounted(async () => {
-  // Close SSE connection
+// Cleanup when component unmounts or camera changes
+async function cleanupSSE() {
   if (sseConnection.value) {
     sseConnection.value.close()
+    sseConnection.value = null
   }
-
-  // Delete subscription
   if (subscriptionId.value) {
-    await deleteEventSubscription(subscriptionId.value)
+    try {
+      await deleteEventSubscription(subscriptionId.value)
+    } catch {
+      // Ignore cleanup errors
+    }
+    subscriptionId.value = null
   }
+}
+
+onUnmounted(() => {
+  cleanupSSE()
 })
 ```
 
@@ -568,9 +598,21 @@ async function createMetricsChart(canvas: HTMLCanvasElement, cameraId: string) {
 | SUBSCRIPTION_LIMIT | Too many subscriptions | Delete old subscriptions |
 | SSE_CONNECTION_FAILED | Can't connect to stream | Retry with backoff |
 
+## Common SSE Mistakes
+
+| Mistake | Correct Approach |
+|---------|-----------------|
+| `createEventSubscription({ actors, types })` flat params | Use `{ deliveryConfig: { type: 'serverSentEvents.v1' }, filters: [{ actors, types }] }` |
+| `types: ['een.motionDetectionEvent.v1']` as strings | Use `types: [{ id: 'een.motionDetectionEvent.v1' }]` as objects |
+| `result.data.sseUrl` for the SSE URL | Use `result.data.deliveryConfig.sseUrl` |
+| Treating `connectToEventSubscription()` return as the connection | Returns `{ data: SSEConnection, error }` Result type |
+| Using `onOpen` callback | Use `onStatusChange` with `SSEConnectionStatus` type |
+| Forgetting to clean up when subscribed resource changes | Always clean up existing subscription before starting a new one |
+
 ## Constraints
 - Always use actor format: `camera:{cameraId}` or `account:{accountId}`
-- Always clean up SSE subscriptions on component unmount
+- Always clean up SSE subscriptions on component unmount and when the subscribed resource changes
 - Use formatTimestamp() for all timestamp parameters
 - Include 'data.overlays' in include[] to get bounding box SVGs
 - Handle SSE reconnection for long-running streams
+- Use `listEventFieldValues()` to discover available event types before subscribing

package/.claude/agents/een-media-agent.md

@@ -67,13 +67,17 @@ assistant: "I'll use the een-media-agent to diagnose the HLS configuration and a
 - Check authentication before media operations
 - Pass config to LivePlayer's `start()` method, NOT the constructor
 
-## Choosing the Right Preview Method
+## Choosing the Right Video Method
+
+**IMPORTANT DECISION RULE:** When the user asks for "HD video", "main video", "full quality",
+or "live video feed", you MUST use the **Live Video SDK** (`@een/live-video-web-sdk`).
+Only use `multipartUrl` when explicitly asked for "preview", "thumbnail", or "low bandwidth" options.
 
 | Use Case | Method | Why |
 |----------|--------|-----|
 | Grid of 20+ cameras | `getLiveImage()` | Lower bandwidth, manual refresh |
 | Auto-updating preview | `multipartUrl` + `initMediaSession()` | Automatic updates, higher bandwidth |
-| Full-quality live video | Live Video SDK | Full resolution, lowest latency |
+| **Full-quality live video** | **Live Video SDK** | **Full resolution, lowest latency** |
 | Recorded video playback | HLS via `listMedia()` | Seek capability, standard player |
 
 **CRITICAL: Main feeds do NOT support multipartUrl**
@@ -83,7 +87,8 @@ The EEN API only returns `multipartUrl` for **preview feeds** (`type: 'preview'`
 - **Preview feeds** → Use `multipartUrl` (MJPEG in `<img>` element)
 - **Main feeds** → Use **Live Video SDK** (full HD in `<video>` element)
 
-If you need HD quality video, you MUST use the Live Video SDK. Do not attempt to use `multipartUrl` with main feeds - it won't work.
+If you need HD quality video, you MUST use the Live Video SDK (`npm install @een/live-video-web-sdk`).
+Do not attempt to use `multipartUrl` with main feeds - it won't work.
 
 ## Key Functions
 
@@ -312,6 +317,52 @@ The video element MUST be rendered in the DOM before calling `player.start()`.
 </style>
 ```
 
+## CRITICAL: Camera Switching with LivePlayer
+
+The LivePlayer SDK does **NOT cleanly release** the `<video>` element when `stop()` is called.
+Reusing the same `<video>` element for a new LivePlayer instance will result in the video feed
+**not updating** when the user switches cameras.
+
+**Solution:** Use a Vue `:key` to force a fresh `<video>` element on each camera switch:
+
+```vue
+<script setup lang="ts">
+const videoRef = ref<HTMLVideoElement | null>(null)
+const videoKey = ref(0)
+let livePlayer: LivePlayer | null = null
+
+async function startStream(cameraId: string) {
+  // Stop previous player
+  if (livePlayer) {
+    livePlayer.stop()
+    livePlayer = null
+  }
+
+  // CRITICAL: Increment key to force Vue to create a new <video> element
+  videoKey.value++
+  await nextTick()  // Wait for new element to be in DOM
+
+  livePlayer = new LivePlayer()
+  await livePlayer.start({
+    videoElement: videoRef.value!,
+    cameraId,
+    baseUrl: authStore.baseUrl ?? '',
+    jwt: authStore.token ?? ''
+  })
+}
+</script>
+
+<template>
+  <!-- :key forces a fresh DOM element when videoKey changes -->
+  <video :key="videoKey" ref="videoRef" autoplay muted playsinline />
+</template>
+```
+
+**Why this is needed:** After `livePlayer.stop()`, the old `<video>` element retains stale
+MediaSource/WebSocket state. Creating a new LivePlayer on the same element fails silently —
+the video appears frozen on the previous camera's last frame. The `:key` trick makes Vue
+destroy and recreate the DOM element, giving the new LivePlayer a clean slate.
+
 ## Error Handling
 
 | Error Code | Meaning | Action |
@@ -332,3 +383,5 @@ The video element MUST be rendered in the DOM before calling `player.start()`.
 | "Video Stream is done" immediately | Config passed to LivePlayer constructor | MUST use `new LivePlayer()` with no args, then `player.start(config)` |
 | "Video element not found" | Video element not in DOM | Ensure video element is rendered (not hidden by v-if) before SDK init |
 | Black video, no errors (LivePlayer) | Video element hidden by v-if | Use CSS visibility/opacity instead of v-if for conditional video display |
+| Video doesn't change on camera switch | LivePlayer doesn't release video element cleanly | Use Vue `:key` on `<video>` element, increment on each switch (see Camera Switching section) |
+| Used multipartUrl for "HD video" request | multipartUrl only supports preview feeds | Use Live Video SDK (`@een/live-video-web-sdk`) for HD/main feed video |

package/.claude/agents/een-setup-agent.md

@@ -2,8 +2,8 @@
 name: een-setup-agent
 description: |
   Use this agent when creating a new Vue 3 application with een-api-toolkit,
-  when fixing Pinia initialization errors, when troubleshooting OAuth redirect
-  URI issues, or when setting up Vite configuration for EEN applications.
+  when fixing Pinia initialization errors, or when setting up Vite configuration
+  for EEN applications.
 model: inherit
 color: green
 ---
@@ -26,34 +26,37 @@ assistant: "I'll use the een-setup-agent to diagnose and fix the Pinia initializ
 <Task tool call to launch een-setup-agent>
 </example>
 
-<example>
-Context: User has OAuth redirect issues.
-user: "My OAuth login redirects to the wrong URL"
-assistant: "I'll use the een-setup-agent to check your vite.config.ts and redirect URI configuration."
-<Task tool call to launch een-setup-agent>
-</example>
-
 ## Context Files
 Load these documentation files before starting:
 - docs/AI-CONTEXT.md (overview)
 - docs/ai-reference/AI-SETUP.md (primary reference)
 
+## Scope and Agent Delegation
+
+This agent handles **project scaffolding only**: Vite config, main.ts initialization,
+basic router structure, placeholder views, and environment variables.
+
+**After scaffolding, delegate to specialized agents for feature implementation:**
+
+- **een-auth-agent** — OAuth login/logout views, auth callback handling, route guards,
+  session restoration (`authStore.initialize()`), Playwright E2E auth tests.
+  Knows the EEN two-step login flow and correct Playwright selectors.
+- **een-media-agent** — Live video, camera previews, recorded images, HLS playback.
+  Knows when to use Live Video SDK vs multipartUrl and how to handle camera switching.
+- **een-devices-agent** — Camera/bridge listing, filtering, and device details.
+
+**Do NOT implement OAuth views (Login.vue, Callback.vue, Logout.vue) or media components
+yourself.** Create placeholder views, then let the caller invoke the specialized agent.
+
 ## Your Capabilities
-1. Create new Vue 3 project structure for EEN applications
-2. Configure main.ts with proper Pinia + toolkit initialization
-3. Set up vite.config.ts for EEN requirements (127.0.0.1:3333)
-4. Configure Vue Router with OAuth callback handling
-5. Set up environment variables
-6. Debug common setup errors (Pinia not active, redirect URI mismatch)
-
-## Workflow
-1. Verify prerequisites (Node 20+, Vue 3, Pinia)
-2. Create or modify configuration files
-3. Set up router with OAuth callback pattern
-4. Verify setup by checking for common errors
-5. Reference examples/vue-users/ for working patterns
-
-## Key Configuration Points
+1. Create Vue 3 + Vite + TypeScript project structure
+2. Configure main.ts with proper Pinia + toolkit initialization order
+3. Set up vite.config.ts (host: 127.0.0.1, port: 3333)
+4. Create basic router with placeholder routes for /, /login, /callback, /logout
+5. Set up .env environment variables
+6. Debug Pinia initialization errors
+
+## Key Configuration
 
 ### main.ts Initialization Order
 ```typescript
@@ -74,36 +77,7 @@ app.use(router)
 app.mount('#app')
 ```
 
-### App.vue Session Restoration (CRITICAL)
-**Users will need to re-login after every page refresh unless you call `authStore.initialize()` in App.vue.**
-
-```vue
-<script setup lang="ts">
-import { onMounted, computed } from 'vue'
-import { useAuthStore } from 'een-api-toolkit'
-
-const authStore = useAuthStore()
-const isAuthenticated = computed(() => authStore.isAuthenticated)
-
-// CRITICAL: Initialize auth store from storage on app mount
-// This restores the session if a valid token exists in localStorage/sessionStorage
-onMounted(() => {
-  authStore.initialize()
-})
-</script>
-```
-
-Without `initialize()`:
-- Token is saved to localStorage after login ✓
-- On page refresh, Pinia store starts with empty state
-- `isAuthenticated` returns false → user must login again
-
-With `initialize()`:
-- Token is loaded from localStorage on app mount
-- `isAuthenticated` returns true → session is restored
-- User can continue without re-logging in
-
-### vite.config.ts for EEN OAuth
+### vite.config.ts
 ```typescript
 import { defineConfig } from 'vite'
 import vue from '@vitejs/plugin-vue'
@@ -111,48 +85,25 @@ import vue from '@vitejs/plugin-vue'
 export default defineConfig({
   plugins: [vue()],
   server: {
-    // IMPORTANT: Must use 127.0.0.1:3333 for EEN OAuth callback
-    // The EEN Identity Provider only permits this specific redirect URI
-    host: '127.0.0.1',
+    host: '127.0.0.1',  // REQUIRED: Must match EEN OAuth redirect URI
     port: 3333
   }
 })
 ```
 
-### Router with OAuth Callback
-```typescript
-import { createRouter, createWebHistory } from 'vue-router'
-
-const routes = [
-  { path: '/', component: () => import('@/views/Home.vue') },
-  { path: '/login', component: () => import('@/views/Login.vue') },
-  { path: '/callback', component: () => import('@/views/Callback.vue') },
-  { path: '/logout', component: () => import('@/views/Logout.vue') }
-]
-
-const router = createRouter({
-  history: createWebHistory(),
-  routes
-})
-
-export default router
-```
+### Router Skeleton
+Create routes for /, /login, /callback, /logout. Auth guards and OAuth callback
+handling should be implemented by the **een-auth-agent**.
 
 ## Constraints
 - Always use 127.0.0.1, never localhost
 - Always use port 3333
 - Pinia must be installed before initEenToolkit()
-- Never add trailing slashes to redirect URIs
-- Ensure VITE_PROXY_URL is set in .env file
-- **Always call `authStore.initialize()` in App.vue onMounted** for session persistence
+- Ensure VITE_PROXY_URL and VITE_EEN_CLIENT_ID are set in .env
 
-## Common Errors and Solutions
+## Common Errors
 
 | Error | Cause | Solution |
 |-------|-------|----------|
-| "Pinia not active" | initEenToolkit() called before pinia.use() | Reorder initialization in main.ts |
-| "redirect_uri mismatch" | Wrong host/port | Use 127.0.0.1:3333 in vite.config.ts |
-| "Invalid redirect_uri" | Trailing slash | Remove trailing slash from redirect URI |
-| "CORS error" | Proxy not running | Start the OAuth proxy server |
-| Session lost on refresh | Missing initialize() call | Add `authStore.initialize()` in App.vue onMounted |
-| Must login after refresh | Missing initialize() call | Add `authStore.initialize()` in App.vue onMounted |
+| "Pinia not active" | initEenToolkit() called before app.use(pinia) | Reorder initialization in main.ts |
+| Auth/OAuth errors | See **een-auth-agent** | Delegate to een-auth-agent |

package/CHANGELOG.md

@@ -2,37 +2,10 @@
 
 All notable changes to this project will be documented in this file.
 
-## [0.3.79] - 2026-02-14
+## [0.3.81] - 2026-02-14
 
 ### Release Summary
 
-#### PR #108: Release v0.3.76: Hostname validation security hardening
-## Summary
-- **Security Fix**: Validate hostname against EEN domain allowlist to prevent token exfiltration via malicious base URL injection
-- **Hardening**: Fail-secure on tampered storage - clears all auth data when poisoned hostname/port detected
-- **Validation**: Port validation (1-65535 range), protocol bypass prevention, subdomain spoofing protection
-- **Tests**: Comprehensive hostname validation test suite for auth store (46 new tests)
-- **Robustness**: Added `isAllowedEenHostname` utility with falsy guard, console.warn for rejected hostnames, `@internal` JSDoc tag on `ALLOWED_DOMAINS`
-
-## Commits
-- fix: Validate hostname against EEN domain allowlist to prevent token exfiltration
-- test: Add hostname validation tests for auth store security fix
-- docs: Add @internal JSDoc tag to ALLOWED_DOMAINS constant
-- fix: Use console.warn for rejected hostname validation messages
-- fix: Add falsy guard to isAllowedEenHostname for robustness
-- fix: harden hostname/port validation and fail-secure on tampered storage
-
-## Test Results
-- **Lint**: Passed (1 warning - pre-existing)
-- **Unit Tests**: 639 passed (23 test files)
-- **Build**: Successful (ESM + CJS)
-- **E2E Tests**: All 11 example apps passed
-
-## Version
-`0.3.76`
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
 #### PR #110: fix: Security hardening - hostname validation and CI/CD pipeline
 ## Summary
 
@@ -69,18 +42,51 @@ Release v0.3.79 - Security hardening fixes for three vulnerabilities identified
 
 🤖 Generated with [Claude Code](https://claude.com/claude-code)
 
+#### PR #112: fix: revert broken head_branch check and update agents/skill
+## Summary
+
+Release v0.3.80 with two key changes:
+
+1. **Fix broken publish workflow** — The `head_branch == 'production'` check added in v0.3.79 caused all automated npm publish runs to be skipped. GitHub's `workflow_run.head_branch` refers to the PR source branch (e.g. `develop`), not the target. The upstream `test-release.yml` already restricts to PRs merged to production.
+
+2. **Add confidential data scan to PR-and-check skill** — New step that scans changed `.md` files for secrets, credentials, or confidential data before PR creation. Critical safeguard for a public npm package.
+
+3. **Agent documentation improvements** — Updated Playwright selectors (getByPlaceholder), SSE API patterns (nested deliveryConfig/filters), LivePlayer camera switching (:key trick), and setup agent scope (delegation to specialized agents).
+
+## Commits
+
+- `1bb7297` fix: revert broken head_branch check in npm-publish workflow
+- `6afd34a` chore: add confidential data scan to PR-and-check skill and update agents
+- `c5ff7eb` Merge pull request #111
+
+## Test Results
+
+- **Lint**: 0 errors (1 pre-existing warning)
+- **Unit tests**: 644 passed
+- **Build**: Success
+- **E2E tests**: 3/11 passed before flaky auth timeout in vue-cameras (camera-settings.spec.ts:328, unrelated to changes)
+- **Security review**: No vulnerabilities found
+- **Confidential data scan**: No secrets in 224 .md files
+
+## Version
+
+`0.3.80`
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
 
 ### Detailed Changes
 
 #### Bug Fixes
-- fix: harden hostname validation and CI/CD security
+- fix: use Vue ref() pattern in een-events-agent SSE example
+- fix: revert broken head_branch check in npm-publish workflow
 
 #### Other Changes
-- Update src/utils/hostname.ts
+- chore: add confidential data scan to PR-and-check skill and update agents
 
 ### Links
 - [npm package](https://www.npmjs.com/package/een-api-toolkit)
-- [Full Changelog](https://github.com/klaushofrichter/een-api-toolkit/compare/v0.3.78...v0.3.79)
+- [Full Changelog](https://github.com/klaushofrichter/een-api-toolkit/compare/v0.3.79...v0.3.81)
 
 ---
-*Released: 2026-02-14 07:56:49 CST*
+*Released: 2026-02-14 10:39:08 CST*

package/docs/AI-CONTEXT.md

@@ -1,6 +1,6 @@
 # EEN API Toolkit - AI Reference
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > This documentation is optimized for AI assistants. It provides focused, domain-specific
 > references to help you understand and use the een-api-toolkit efficiently.

package/docs/ai-reference/AI-AUTH.md

@@ -1,6 +1,6 @@
 # Authentication - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > OAuth flow implementation, token management, and session handling.
 > Load this document when implementing login, logout, or auth guards.

package/docs/ai-reference/AI-AUTOMATIONS.md

@@ -1,6 +1,6 @@
 # Automations API - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for automation rules and alert actions.
 > Load this document when working with automated alert workflows.

package/docs/ai-reference/AI-DEVICES.md

@@ -1,6 +1,6 @@
 # Cameras & Bridges API - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for camera and bridge management.
 > Load this document when working with devices.

package/docs/ai-reference/AI-EVENT-DATA-SCHEMAS.md

@@ -1,6 +1,6 @@
 # Event Type to Data Schemas Mapping - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for event type to data schema mappings.
 > Load this document when building dynamic event queries with the `include` parameter.

package/docs/ai-reference/AI-EVENTS.md

@@ -1,6 +1,6 @@
 # Events, Alerts & Real-Time Streaming - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for events, alerts, metrics, and SSE subscriptions.
 > Load this document when implementing event-driven features.

package/docs/ai-reference/AI-GROUPING.md

@@ -1,6 +1,6 @@
 # Layouts API - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for layout management (camera grouping).
 > Load this document when working with layouts.

package/docs/ai-reference/AI-JOBS.md

@@ -1,6 +1,6 @@
 # Jobs, Exports, Files & Downloads - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for async jobs, video exports, and file management.
 > Load this document when implementing export workflows or file downloads.

package/docs/ai-reference/AI-MEDIA.md

@@ -1,6 +1,6 @@
 # Media & Live Video - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for media retrieval, live streaming, and video playback.
 > Load this document when implementing video features.

package/docs/ai-reference/AI-SETUP.md

@@ -1,6 +1,6 @@
 # Vue 3 Application Setup - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete guide for setting up a Vue 3 application with the een-api-toolkit.
 > Load this document when creating a new project or troubleshooting setup issues.

package/docs/ai-reference/AI-USERS.md

@@ -1,6 +1,6 @@
 # Users API - EEN API Toolkit
 
-> **Version:** 0.3.79
+> **Version:** 0.3.81
 >
 > Complete reference for user management.
 > Load this document when working with user data.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "een-api-toolkit",
-  "version": "0.3.79",
+  "version": "0.3.81",
   "description": "EEN Video platform API v3.0 library for Vue 3",
   "type": "module",
   "main": "./dist/index.cjs",