een-api-toolkit 0.3.82 → 0.3.85

package/.claude/agents/api-coverage-agent.md

@@ -0,0 +1,264 @@
+---
+name: api-coverage-agent
+description: |
+  Use this agent when you need to regenerate the EEN API coverage documentation.
+  It fetches the complete EEN API v3.0 endpoint list from OpenAPI specs and the
+  developer portal, scans the toolkit codebase for implemented endpoints, and
+  produces four output documents: all endpoints, implemented endpoints, missing
+  endpoints, and an interactive HTML coverage table.
+model: sonnet
+color: cyan
+---
+
+You are an expert API documentation analyst. Your job is to produce four coverage documents comparing the full Eagle Eye Networks REST API v3.0 against what is implemented in the een-api-toolkit.
+
+## Examples
+
+<example>
+Context: User has just added new API endpoints to the toolkit.
+user: "I added camera update and delete endpoints, regenerate the coverage docs"
+assistant: "I'll use the api-coverage-agent to regenerate all four API coverage documents."
+<Task tool call to launch api-coverage-agent>
+</example>
+
+<example>
+Context: User wants to see current API coverage status.
+user: "What's our current EEN API coverage?"
+assistant: "I'll use the api-coverage-agent to produce an up-to-date coverage report."
+<Task tool call to launch api-coverage-agent>
+</example>
+
+## Output Files
+
+You produce exactly four files in `docs/`:
+
+1. **`docs/een-api-all-endpoints.md`** - Complete reference of ALL EEN API v3.0 endpoints
+2. **`docs/een-api-implemented.md`** - Endpoints implemented by the toolkit with function names and source files
+3. **`docs/een-api-missing.md`** - Endpoints not yet implemented, with coverage percentages
+4. **`docs/een-api-coverage.html`** - Interactive HTML table with filters, sorting, and summary statistics
+
+## Workflow
+
+### Phase 1: Fetch the Complete EEN API Endpoint List
+
+Fetch ALL OpenAPI specification YAML files from the EEN GitHub repository to get the authoritative endpoint list:
+
+```
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/devices_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/media_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/events_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/automations_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/grouping_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/user_and_accounts_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/system_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/account_settings_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/resellers_account_switching_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/video_search_category.yaml
+https://raw.githubusercontent.com/EENCloud/VMS-Developer-Portal/main/Open%20API%20Specifications/vehicle_surveillance_package_category.yaml
+```
+
+For each YAML file, extract ALL endpoint paths with their HTTP methods (GET, POST, PUT, PATCH, DELETE).
+
+**Important**: The OpenAPI specs may not cover every endpoint. Supplement by fetching the developer portal reference page:
+```
+https://developer.eagleeyenetworks.com/reference/using-the-api
+```
+
+Look for endpoints documented on the portal but missing from the specs. Common gaps include:
+- Events: `/events/{id}`, `/events:listRecentByType`, `/events:listFieldValues`, `/eventTypes`, `/eventMetrics`
+- Event Subscriptions: full CRUD + filters sub-resources
+- Alerts: `/alerts`, `/alerts/{id}`, `/alertTypes`
+- Notifications: `/notifications`, `/notifications/{id}`, `PATCH /notifications/{id}`
+
+### Phase 2: Scan the Toolkit for Implemented Endpoints
+
+Search the codebase for all implemented EEN API endpoints:
+
+1. **Find all API URLs**: Search for the pattern `api/v3.0` in all TypeScript files under `src/`:
+   ```
+   Grep pattern: "api/v3.0" in src/**/*.ts
+   ```
+
+2. **Find all exported async functions**: These are the public API of the toolkit:
+   ```
+   Grep pattern: "export async function" in src/**/*.ts
+   ```
+
+3. **Find all HTTP methods used**: Identify which methods (GET, POST, PATCH, DELETE, PUT) each endpoint uses:
+   ```
+   Grep pattern: "method: '(POST|PATCH|PUT|DELETE)'" in src/**/*.ts
+   ```
+   (GET is the default when no method is specified)
+
+4. **Check for SSE connections**: Look for EventSource or SSE-related code:
+   ```
+   Grep pattern: "EventSource|SSE|connectTo" in src/**/*.ts
+   ```
+
+5. **Check auth proxy functions**: These call the OAuth proxy, not EEN API directly:
+   ```
+   Read src/auth/service.ts for proxy endpoint functions
+   ```
+
+For each implemented endpoint, record:
+- HTTP method
+- EEN API path (e.g., `/api/v3.0/cameras`)
+- Toolkit function name (e.g., `getCameras()`)
+- Source file path
+
+### Phase 3: Cross-Reference and Classify
+
+For every endpoint in the complete EEN API list, determine if it is:
+- **Implemented**: A matching function exists in the toolkit (same HTTP method + path)
+- **Missing**: No implementation found
+
+Also identify:
+- Toolkit functions that call endpoints NOT in the official API docs (flag as "undocumented")
+- Auth proxy functions (not EEN API endpoints, but part of the toolkit)
+- SSE/WebSocket connections (supplementary to REST endpoints)
+
+### Phase 4: Generate the Four Documents
+
+#### Document 1: `docs/een-api-all-endpoints.md`
+
+Structure:
+```markdown
+# Eagle Eye Networks REST API v3.0 - Complete Endpoint Reference
+
+> Generated: YYYY-MM-DD
+> Source: [EEN Developer Portal](...) and [OpenAPI Specifications](...)
+
+All paths are prefixed with `/api/v3.0` on the appropriate base URL.
+
+## CATEGORY - Subcategory (N endpoints)
+
+| Method | Path | Description |
+|--------|------|-------------|
+| GET | `/path` | Description |
+...
+
+## Summary
+
+| Category | Subcategory | Endpoints |
+...
+
+### By HTTP Method
+
+| Method | Count |
+...
+```
+
+Organize endpoints by these categories and subcategories:
+- **Devices**: Cameras, Bridges, PTZ, Speakers, Device I/O, Switches, Multi Cameras, Available Devices
+- **Grouping**: Layouts, Tags, Locations, Floors, Floor Plans
+- **Media**: Media, Feeds, Exports, Jobs, Files, Downloads
+- **Events**: Events, Event Types, Event Metrics, Event Subscriptions, Alerts, Notifications
+- **Automations**: Event Alert Condition Rules, Alert Action Rules, Alert Actions
+- **Video Search**: Video Analytic Events
+- **Vehicle Surveillance**: LPR Events, LPR Alert Condition Rules, LPR Vehicle Lists
+- **User & Accounts**: Users, Accounts, Roles, Audit Log, Resource Grants, Editions
+- **Resellers**: Authorization Tokens
+- **Account Settings**: SSO, Client Settings
+- **System**: Applications, OAuth Clients, Reference Data
+
+#### Document 2: `docs/een-api-implemented.md`
+
+Structure:
+```markdown
+# een-api-toolkit - Implemented EEN API Endpoints
+
+> Generated: YYYY-MM-DD
+
+## Authentication (via OAuth Proxy)
+[Table of auth proxy functions - note these are NOT EEN API endpoints]
+
+## Category (N endpoints)
+
+| Method | EEN API Path | Toolkit Function | Source |
+|--------|-------------|-----------------|--------|
+| GET | `/api/v3.0/path` | `functionName()` | `src/.../service.ts` |
+...
+
+## Summary
+[Table with counts per category and by HTTP method]
+```
+
+#### Document 3: `docs/een-api-missing.md`
+
+Structure:
+```markdown
+# een-api-toolkit - Missing EEN API Endpoints
+
+> Generated: YYYY-MM-DD
+> Coverage: X of Y endpoints implemented (Z%)
+
+## CATEGORY - Subcategory (N of M missing)
+Implemented: [brief list of what IS implemented]
+
+| Method | Path | Description |
+...
+
+## Summary
+[Coverage table per category]
+[Lists of fully implemented sections and entirely missing sections]
+```
+
+#### Document 4: `docs/een-api-coverage.html`
+
+Generate a self-contained HTML file with:
+
+**Header section**:
+- Title: "Eagle Eye Networks API v3.0 - Toolkit Coverage"
+- Generation date
+- Summary stat cards: Total endpoints, Implemented, Missing, Coverage percentage with progress bar
+
+**Filter bar**:
+- Status filter dropdown (All / Implemented / Missing)
+- Category filter dropdown (All + each category)
+- Method filter dropdown (All / GET / POST / PATCH / DELETE / PUT)
+- Text search input for path/function/description
+
+**Data table**:
+- Columns: #, Category, Subcategory, Method, Path, Description, Status, Toolkit Function
+- Sortable by clicking column headers
+- Color-coded method badges (GET=blue, POST=green, PATCH=yellow, DELETE=red, PUT=indigo)
+- Status badges (Implemented=green, Missing=red)
+- Monospace font for function names
+
+**Styling**:
+- Clean, modern CSS with system font stack
+- Light background (#f5f7fa)
+- White card-style table with subtle shadows
+- Responsive layout
+- All styles inline (self-contained, no external dependencies)
+
+**JavaScript**:
+- All endpoint data in a `const endpoints = [...]` array with objects: `{cat, sub, method, path, desc, status, func}`
+- `status` values: `"impl"` for implemented, `"miss"` for missing
+- `func` is empty string for missing endpoints
+- `renderTable(data)` function to populate tbody
+- `filterTable()` function combining all filter inputs
+- `sortTable(colIndex)` function with toggle direction
+- All code inline (no external dependencies)
+
+## Important Guidelines
+
+1. **Fetch fresh data every time** - Do not rely on cached or previously generated content. Always fetch the OpenAPI specs and scan the codebase.
+
+2. **Be accurate with counts** - Double-check endpoint totals match between documents. The total in all-endpoints.md must equal implemented + missing in missing.md.
+
+3. **Parallel fetching** - Fetch multiple OpenAPI YAML files in parallel using concurrent WebFetch calls to save time. Also run codebase Grep searches in parallel.
+
+4. **Handle OpenAPI gaps** - Some endpoints are on the developer portal but not in the OpenAPI specs (especially Events category sub-resources). Use both sources.
+
+5. **Flag undocumented endpoints** - If the toolkit implements endpoints not found in any official documentation, note them with a warning (e.g., `alertConditionRules` without the `event` prefix).
+
+6. **Include the generation date** - Use today's date in all document headers.
+
+7. **Open the HTML when done** - After writing all four files, run `open docs/een-api-coverage.html` to display the result in the browser.
+
+8. **Preserve category ordering** - Use the category order listed above consistently across all four documents.
+
+9. **Count auth proxy separately** - Auth proxy functions (getAccessToken, refreshToken, revokeToken, handleAuthCallback) communicate with the proxy server, not the EEN API. List them in the implemented doc but do not count them in the EEN API coverage totals.
+
+10. **Count SSE separately** - The `connectToEventSubscription()` function uses SSE, not REST. List it but count it separately from REST endpoint coverage.

package/CHANGELOG.md

@@ -2,105 +2,72 @@
 
 All notable changes to this project will be documented in this file.
 
-## [0.3.82] - 2026-02-14
+## [0.3.85] - 2026-02-17
 
 ### Release Summary
 
-#### PR #110: fix: Security hardening - hostname validation and CI/CD pipeline
+#### PR #113: fix: address three security review findings
 ## Summary
+- **HIGH**: Validate hostname before persisting OAuth token — `setBaseUrl()` now returns boolean; `handleAuthCallback()` checks it before calling `setToken()`, preventing token persistence when hostname is rejected
+- **MEDIUM**: Pin external proxy repo clone in CI workflows (`validate-pr`, `test-release`) to commit SHA `4e8f45f` to prevent supply chain attacks
+- **LOW**: Remove unnecessary `id-token: write` permission from `claude-code-review` workflow
 
-Release v0.3.79 - Security hardening fixes for three vulnerabilities identified in code review:
-
-- **Hostname validation bypass**: Added DNS hostname character regex (`/^[a-z0-9]([a-z0-9.-]*[a-z0-9])?$/`) before `endsWith()` check in `isAllowedEenHostname()` to prevent bypass attacks like `evil.com/.eagleeyenetworks.com`
-- **CI/CD branch restriction**: Added `head_branch == 'production'` check to npm-publish workflow to prevent publishing from non-production branches
-- **Script injection prevention**: Moved `${{ }}` interpolation from shell `run:` blocks to `env:` blocks in test-release workflow at 3 locations
-
-## Commits
-
-- `d4e8a06` fix: harden hostname validation and CI/CD security
-- `c870348` Update src/utils/hostname.ts
-- `5a76991` Merge pull request #109
-
-## Test Results
-
-- **Lint**: 0 errors (1 pre-existing warning)
-- **Unit tests**: 644 passed
-- **Build**: Success
-- **E2E tests**: 225 passed across all 11 example apps
-- **Security review**: No HIGH-confidence vulnerabilities found
-
-## Files Changed
-
-- `src/utils/hostname.ts` - Added hostname character validation regex
-- `src/__tests__/auth.store.test.ts` - Added 5 test cases for malicious hostname bypass
-- `.github/workflows/npm-publish.yml` - Added production branch restriction
-- `.github/workflows/test-release.yml` - Fixed script injection at 3 locations
-
-## Version
-
-`0.3.79`
+## Test plan
+- [x] 644/644 unit tests pass
+- [x] 225/225 E2E tests pass across all 11 example apps
+- [x] Lint clean, build succeeds
+- [ ] Validate-PR workflow passes on this PR
 
 🤖 Generated with [Claude Code](https://claude.com/claude-code)
 
-#### PR #112: fix: revert broken head_branch check and update agents/skill
+#### PR #118: Release v0.3.85 - API coverage docs and workflow security fix
 ## 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).
+- Add EEN API v3.0 coverage documentation (4 documents comparing 211 API endpoints against 51 implemented, 24.2% coverage)
+- Add `api-coverage-agent` for on-demand regeneration of coverage docs
+- Update README with agent list and coverage section
+- Fix workflow_dispatch restriction to production branch (security)
 
 ## 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
+- `baa7e1b` feat: add EEN API coverage documentation and agent
+- `eea17e8` docs: add missing agents to README agent list
+- `bb47cc2` docs: rename een-api-coverage-agent to api-coverage-agent
+- `c794fba` fix: restrict workflow_dispatch to production branch to prevent supply chain attack
+- `6e782e2` fix: restrict npm-publish workflow_dispatch to production branch
 
-## Test Results
+## Test Results (from PR #117)
 
-- **Lint**: 0 errors (1 pre-existing warning)
+- **Lint**: Passed
 - **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
+- **Build**: Succeeded
+- **E2E tests**: 236 passed across all 11 example apps
+- **Security review**: No vulnerabilities
+- **Code review**: Approved by Claude Sonnet 4.5
 
 ## Version
 
-`0.3.80`
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-
-#### PR #113: fix: address three security review findings
-## Summary
-- **HIGH**: Validate hostname before persisting OAuth token — `setBaseUrl()` now returns boolean; `handleAuthCallback()` checks it before calling `setToken()`, preventing token persistence when hostname is rejected
-- **MEDIUM**: Pin external proxy repo clone in CI workflows (`validate-pr`, `test-release`) to commit SHA `4e8f45f` to prevent supply chain attacks
-- **LOW**: Remove unnecessary `id-token: write` permission from `claude-code-review` workflow
-
-## Test plan
-- [x] 644/644 unit tests pass
-- [x] 225/225 E2E tests pass across all 11 example apps
-- [x] Lint clean, build succeeds
-- [ ] Validate-PR workflow passes on this PR
+v0.3.85
 
 🤖 Generated with [Claude Code](https://claude.com/claude-code)
 
 
 ### Detailed Changes
 
+#### Features
+- feat: add EEN API coverage documentation and agent
+
 #### Bug Fixes
-- fix: restore id-token:write permission required by claude-code-action
-- fix: address three security review findings
+- fix: restrict npm-publish workflow_dispatch to production branch
+- fix: restrict workflow_dispatch to production branch to prevent supply chain attack
 
 #### Other Changes
-- chore: document pinned OAuth proxy commit SHA in CI workflows
+- docs: rename een-api-coverage-agent to api-coverage-agent
+- docs: add missing agents to README agent list
 
 ### Links
 - [npm package](https://www.npmjs.com/package/een-api-toolkit)
-- [Full Changelog](https://github.com/klaushofrichter/een-api-toolkit/compare/v0.3.81...v0.3.82)
+- [Full Changelog](https://github.com/klaushofrichter/een-api-toolkit/compare/v0.3.82...v0.3.85)
 
 ---
-*Released: 2026-02-14 19:46:06 CST*
+*Released: 2026-02-17 11:45:53 CST*

package/README.md

@@ -182,7 +182,7 @@ The toolkit includes specialized [Claude Code](https://docs.anthropic.com/en/doc
 
 > **Note:** These agents use Claude Code's specific format. To use with other AI assistants (Gemini CLI, Copilot, etc.), the agent specs would need conversion.
 
-**Available agents:**
+**Available agents (installed via `npx een-setup-agents`):**
 - `een-setup-agent` - Project scaffolding, Pinia setup, Vite configuration
 - `een-auth-agent` - OAuth flows, route guards, token management
 - `een-users-agent` - User listing and profile APIs
@@ -190,6 +190,10 @@ The toolkit includes specialized [Claude Code](https://docs.anthropic.com/en/doc
 - `een-media-agent` - Live video, previews, HLS playback
 - `een-events-agent` - Events, alerts, metrics, SSE subscriptions
 - `een-grouping-agent` - Layouts CRUD operations, camera pane management
+- `een-automations-agent` - Alert rules, action rules, event conditions
+- `een-jobs-agent` - Jobs, exports, files, downloads
+
+The `setup-agents` script (`scripts/setup-agents.ts`) installs only agents matching the `een-*-agent.md` pattern. Other agents in `.claude/agents/` (such as `api-coverage-agent`, `docs-accuracy-reviewer`, `test-runner`) are for this repository only and are not distributed to consuming projects.
 
 **Installation:**
 ```bash
@@ -311,6 +315,25 @@ The `sync-secrets.sh` script manages secrets from a single source (root `.env` f
 
 > **Note:** Example `.env` files are gitignored. Run `sync-secrets.sh` after cloning to set up local development.
 
+## EEN API Coverage
+
+This toolkit implements a subset of the [Eagle Eye Networks REST API v3.0](https://developer.eagleeyenetworks.com/reference/using-the-api). Coverage documentation is maintained in `docs/`:
+
+| Document | Description |
+|----------|-------------|
+| **[All EEN API Endpoints](./docs/een-api-all-endpoints.md)** | Complete reference of all 211 EEN API v3.0 endpoints |
+| **[Implemented Endpoints](./docs/een-api-implemented.md)** | Endpoints implemented by the toolkit with function names and source files |
+| **[Missing Endpoints](./docs/een-api-missing.md)** | Endpoints not yet implemented, with per-category coverage percentages |
+| **[Coverage Table (HTML)](./docs/een-api-coverage.html)** | Interactive table with filtering, sorting, and summary statistics |
+
+**Fully implemented sections:** Layouts, Feeds, Jobs, Event Types, Event Metrics, Alerts
+
+**Partially implemented:** Users, Cameras, Bridges, Media, Events, Event Subscriptions, Automations, Exports, Files, Downloads
+
+**Not yet implemented:** PTZ, Speakers, Switches, Multi Cameras, Locations, Floors, Video Search, LPR, Roles, Accounts, and others
+
+To regenerate these documents after adding new API endpoints, use the `api-coverage-agent`.
+
 ## External Resources
 
 - [EEN Developer Portal](https://developer.eagleeyenetworks.com/)

package/docs/AI-CONTEXT.md

@@ -1,6 +1,6 @@
 # EEN API Toolkit - AI Reference
 
-> **Version:** 0.3.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82
+> **Version:** 0.3.85
 >
 > 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.82",
+  "version": "0.3.85",
   "description": "EEN Video platform API v3.0 library for Vue 3",
   "type": "module",
   "main": "./dist/index.cjs",