@gala-chain/launchpad-sdk 6.0.0 → 7.0.0-beta.1

package/dist/examples/monitoring/subscribe-liquidity-added.d.ts

@@ -1,30 +0,0 @@
-/**
- * Subscribe to DEX Liquidity Added Events
- *
- * Demonstrates real-time monitoring of liquidity addition events using
- * the `subscribeToDexLiquidityAdded()` SDK method.
- *
- * **Important Backend Behavior:**
- * The backend broadcasts all liquidity position changes without distinguishing
- * between add and remove operations. The `subscribeToDexLiquidityAdded` method
- * is a semantic alias for `subscribeToDexLiquidityChanged` - both receive the
- * same events. Use this method when your intent is to focus on liquidity additions.
- *
- * **Use Cases:**
- * - LP deposit tracking: Monitor when users add liquidity to positions
- * - Whale watching: Detect large liquidity additions
- * - Market analysis: Track overall DEX liquidity growth
- * - Dashboard displays: Show real-time liquidity addition feed
- *
- * @example
- * ```bash
- * # Run with wallet
- * PRIVATE_KEY=0x... npm run demo:monitoring:liquidity-added
- * ```
- *
- * @since 4.3.0
- */
-import '../utils/suppress-logging';
-declare function runLiquidityAddedDemo(): Promise<void>;
-export { runLiquidityAddedDemo };
-//# sourceMappingURL=subscribe-liquidity-added.d.ts.map

package/dist/examples/monitoring/subscribe-liquidity-added.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"subscribe-liquidity-added.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-liquidity-added.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,qBAAqB,kBAuHnC;AAKD,OAAO,EAAE,qBAAqB,EAAE,CAAC"}

package/dist/examples/monitoring/subscribe-liquidity-removed.d.ts

@@ -1,30 +0,0 @@
-/**
- * Subscribe to DEX Liquidity Removed Events
- *
- * Demonstrates real-time monitoring of liquidity removal events using
- * the `subscribeToDexLiquidityRemoved()` SDK method.
- *
- * **Important Backend Behavior:**
- * The backend broadcasts all liquidity position changes without distinguishing
- * between add and remove operations. The `subscribeToDexLiquidityRemoved` method
- * is a semantic alias for `subscribeToDexLiquidityChanged` - both receive the
- * same events. Use this method when your intent is to focus on liquidity removals.
- *
- * **Use Cases:**
- * - LP exit tracking: Monitor when users remove liquidity from positions
- * - Whale watching: Detect large liquidity withdrawals
- * - Risk management: React to liquidity decreases in pools you trade
- * - Market analysis: Track overall DEX liquidity changes
- *
- * @example
- * ```bash
- * # Run with wallet
- * PRIVATE_KEY=0x... npm run demo:monitoring:liquidity-removed
- * ```
- *
- * @since 4.3.0
- */
-import '../utils/suppress-logging';
-declare function runLiquidityRemovedDemo(): Promise<void>;
-export { runLiquidityRemovedDemo };
-//# sourceMappingURL=subscribe-liquidity-removed.d.ts.map

package/dist/examples/monitoring/subscribe-liquidity-removed.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"subscribe-liquidity-removed.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-liquidity-removed.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,uBAAuB,kBAgHrC;AAKD,OAAO,EAAE,uBAAuB,EAAE,CAAC"}

package/dist/examples/monitoring/subscribe-pool-creations.d.ts

@@ -1,29 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Basic Demo: Monitor DEX Pool Creation Events
- *
- * This demo shows how to use `subscribeToDexPoolAdded()` to listen for
- * real-time DEX pool creation events via WebSocket.
- *
- * The demo demonstrates:
- * - Basic subscription setup
- * - Position-independent token filtering
- * - Pair filtering (order-independent)
- * - Fee tier filtering
- * - Combined filters
- * - Cleanup patterns
- *
- * @example
- * ```bash
- * npm run demo:subscribe:pools
- * ```
- *
- * Note: This demo listens for real WebSocket events from the backend.
- * To see actual pool creation events, run the integration test which
- * creates a real pool: `npm run demo:subscribe:pools:integration`
- */
-/**
- * Main demo function
- */
-export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
-//# sourceMappingURL=subscribe-pool-creations.d.ts.map

package/dist/examples/monitoring/subscribe-pool-creations.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"subscribe-pool-creations.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-pool-creations.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAMH;;GAEG;AACH,eAAO,MAAM,OAAO,kDAsNlB,CAAC"}

package/dist/examples/monitoring/subscribe-token-creations.d.ts

@@ -1,21 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Real-Time Token Creation Broadcasting
- *
- * Demonstrates the REAL architecture for token creation monitoring:
- * - WebSocket broadcasts token creation events globally to all connected clients
- * - ~1-2 second latency (vs 15-30+ seconds with polling)
- * - No need for polling or REST API calls
- *
- * This replaces the polling-based onLaunchpadTokenCreation() with instant notifications.
- *
- * Usage:
- * ```bash
- * npm run demo:subscribe:tokens
- * ```
- *
- * Costs: Free (just listening, no transactions)
- * Runtime: Continuous until interrupted (Ctrl+C)
- */
-export {};
-//# sourceMappingURL=subscribe-token-creations.d.ts.map

package/dist/examples/monitoring/subscribe-token-creations.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"subscribe-token-creations.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-token-creations.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;GAiBG"}

package/dist/examples/monitoring/token-creation-integration.d.ts

@@ -1,32 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Integration Demo: Token Creation + Monitoring Architecture
- *
- * This demo illustrates two distinct paths for token creation monitoring:
- *
- * ⚡ PATH 1 - CREATOR'S OWN TOKEN (Instant WebSocket):
- * ✅ `launchToken()` returns instant websocket confirmation (<2 seconds)
- * ✅ Result contains transactionId, vaultAddress from backend
- * ✅ This is what happens internally - websocket confirms own transactions
- *
- * 📡 PATH 2 - MONITORING OTHERS' TOKENS (Polling-Based):
- * ⚠️  `onLaunchpadTokenCreation()` uses REST API polling (NOT real-time websocket)
- * ⚠️  Expected delay: 15-30+ seconds (waits for backend indexing)
- * ⚠️  Why? Backend only emits transaction-specific events, no broadcast channel
- * ⚠️  Use for: Trading bots, monitoring third-party token launches
- *
- * ARCHITECTURE NOTE:
- * The backend doesn't emit broadcast events for token creation to all clients.
- * Non-creators must poll REST API to discover new tokens.
- * This demo shows both approaches with accurate timing expectations.
- *
- * @example
- * ```bash
- * npm run demo:watch:integration
- * ```
- *
- * Cost: ~100-110 GALA on STAGE (100 pre-buy + launch fee)
- * Runtime: ~90 seconds (includes polling wait)
- */
-export {};
-//# sourceMappingURL=token-creation-integration.d.ts.map

package/dist/examples/monitoring/token-creation-integration.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"token-creation-integration.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/token-creation-integration.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG"}

package/dist/examples/monitoring/websocket-event-handlers.d.ts

@@ -1,22 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * WebSocket Event Handlers Comprehensive Demo
- *
- * Demonstrates all 25 WebSocket event handler callbacks supported by the SDK:
- * - Authentication events (onAuthenticated, onConnection)
- * - Stream events (onStreamStatusChanged, onViewerCountChanged, etc.)
- * - Chat events (onStreamChatMessage, onUserTyping, etc.)
- * - Ban events (onBanEnforcement, onUserBanned, onUserUnbanned)
- * - Content moderation (onContentFlagged, onFlagResolved, etc.)
- * - Subscription events (onRoomSubscribed, onTokenSubscribed, etc.)
- *
- * Shows how to register and use all available event handler callbacks
- * with proper type safety and error handling.
- *
- * @example
- * ```bash
- * npm run demo:monitoring:websocket-events
- * ```
- */
-export declare const run: import("../utils").WrappedDemoFunction;
-//# sourceMappingURL=websocket-event-handlers.d.ts.map

package/dist/examples/monitoring/websocket-event-handlers.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"websocket-event-handlers.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/websocket-event-handlers.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;GAkBG;AAsYH,eAAO,MAAM,GAAG,wCAAuD,CAAC"}

package/dist/examples/nft/demo-collection-management.d.ts

@@ -1,13 +0,0 @@
-/**
- * NFT Collection Management Demo
- *
- * Demonstrates the complete workflow for claiming and managing NFT collections:
- * - Checking collection name availability
- * - Claiming a collection
- * - Creating token classes within the collection
- * - Fetching user collections
- *
- * This is a foundational demo for all NFT operations.
- */
-export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
-//# sourceMappingURL=demo-collection-management.d.ts.map

package/dist/examples/nft/demo-collection-management.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"demo-collection-management.d.ts","sourceRoot":"","sources":["../../../examples/nft/demo-collection-management.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAIH,eAAO,MAAM,OAAO,kDAwFlB,CAAC"}

package/dist/examples/nft/demo-fee-calculations.d.ts

@@ -1,14 +0,0 @@
-/**
- * NFT Fee Calculations Demo
- *
- * Demonstrates all fee-related operations:
- * - Getting individual operation fees (fixed rates)
- * - Estimating mint fees (dynamic via DryRun)
- * - Bundling fee estimates for multiple operations
- * - Fee planning for complete workflows
- *
- * This demo helps users understand NFT costs before executing operations.
- */
-import '../utils/suppress-logging';
-export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
-//# sourceMappingURL=demo-fee-calculations.d.ts.map

package/dist/examples/nft/demo-fee-calculations.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"demo-fee-calculations.d.ts","sourceRoot":"","sources":["../../../examples/nft/demo-fee-calculations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAGH,OAAO,2BAA2B,CAAC;AAInC,eAAO,MAAM,OAAO,kDA8LlB,CAAC"}

package/dist/examples/nft/demo-minting.d.ts

@@ -1,13 +0,0 @@
-/**
- * NFT Minting Demo
- *
- * Demonstrates the complete workflow for minting NFTs:
- * - Estimating mint fees via DryRun
- * - Minting NFTs with various quantities
- * - Fetching NFT balances
- * - Querying specific token classes
- *
- * Prerequisites: Run demo-collection-management.ts first to create a collection
- */
-export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
-//# sourceMappingURL=demo-minting.d.ts.map

package/dist/examples/nft/demo-minting.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"demo-minting.d.ts","sourceRoot":"","sources":["../../../examples/nft/demo-minting.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAIH,eAAO,MAAM,OAAO,kDAsKlB,CAAC"}

package/dist/examples/nft/demo-portfolio-query.d.ts

@@ -1,14 +0,0 @@
-/**
- * NFT Portfolio Query Demo
- *
- * Demonstrates comprehensive portfolio analysis:
- * - Fetching all NFT collections
- * - Analyzing token class distribution
- * - Querying balances by collection
- * - Computing portfolio statistics
- * - Holder tier analysis
- *
- * This demo is useful for portfolio management and analytics.
- */
-export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
-//# sourceMappingURL=demo-portfolio-query.d.ts.map

package/dist/examples/nft/demo-portfolio-query.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"demo-portfolio-query.d.ts","sourceRoot":"","sources":["../../../examples/nft/demo-portfolio-query.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAIH,eAAO,MAAM,OAAO,kDAwNlB,CAAC"}

package/dist/examples/nft/nft-collection-lifecycle.d.ts

@@ -1,22 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * NFT Collection Lifecycle Demo
- *
- * Demonstrates NFT collection management:
- * - claimNftCollection() - Claim an NFT collection
- * - isNftCollectionAvailable() - Check collection availability
- * - fetchUserCollections() - List user's authorized collections
- *
- * Shows the complete workflow for claiming and managing NFT collections
- * on GalaChain, including availability checking.
- */
-export declare const runNftCollectionLifecycleDemo: import("../utils").WrappedDemoFunction;
-export declare const metadata: {
-    name: string;
-    description: string;
-    category: string;
-    sdkMethods: string[];
-    requiresAuth: boolean;
-    requiresWallet: boolean;
-};
-//# sourceMappingURL=nft-collection-lifecycle.d.ts.map

package/dist/examples/nft/nft-collection-lifecycle.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nft-collection-lifecycle.d.ts","sourceRoot":"","sources":["../../../examples/nft/nft-collection-lifecycle.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;GAUG;AAaH,eAAO,MAAM,6BAA6B,wCAgJxC,CAAC;AAwBH,eAAO,MAAM,QAAQ;;;;;;;CAYpB,CAAC"}

package/dist/examples/nft/nft-data-queries.d.ts

@@ -1,22 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * NFT Data Queries Demo
- *
- * Demonstrates querying NFT data:
- * - fetchNftBalances() - Get NFTs owned by an address
- * - fetchUserCollections() - Get collections authorized to a user
- * - fetchTokenClasses() - Get token classes within a collection
- *
- * Shows how to discover and analyze NFT holdings, collections,
- * and token class structures on GalaChain.
- */
-export declare const runNftDataQueriesDemo: import("../utils").WrappedDemoFunction;
-export declare const metadata: {
-    name: string;
-    description: string;
-    category: string;
-    sdkMethods: string[];
-    requiresAuth: boolean;
-    requiresWallet: boolean;
-};
-//# sourceMappingURL=nft-data-queries.d.ts.map

package/dist/examples/nft/nft-data-queries.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nft-data-queries.d.ts","sourceRoot":"","sources":["../../../examples/nft/nft-data-queries.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;GAUG;AAcH,eAAO,MAAM,qBAAqB,wCA+PhC,CAAC;AAwBH,eAAO,MAAM,QAAQ;;;;;;;CAYpB,CAAC"}

package/dist/examples/nft/nft-fee-estimation.d.ts

@@ -1,23 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * NFT Fee Estimation Demo
- *
- * Demonstrates NFT operation fee estimation:
- * - estimateNftMintFee() - Estimate fee for minting NFTs
- * - estimateNftOperationFees() - Calculate fees for multiple operations
- * - getNftCollectionClaimFee() - Get fixed collection claim fee
- * - getNftTokenClassCreateFee() - Get fixed token class creation fee
- *
- * Shows comprehensive fee structure and cost planning for NFT operations
- * on GalaChain.
- */
-export declare const runNftFeeEstimationDemo: import("../utils").WrappedDemoFunction;
-export declare const metadata: {
-    name: string;
-    description: string;
-    category: string;
-    sdkMethods: string[];
-    requiresAuth: boolean;
-    requiresWallet: boolean;
-};
-//# sourceMappingURL=nft-fee-estimation.d.ts.map

package/dist/examples/nft/nft-fee-estimation.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nft-fee-estimation.d.ts","sourceRoot":"","sources":["../../../examples/nft/nft-fee-estimation.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;GAWG;AAiBH,eAAO,MAAM,uBAAuB,wCAqQlC,CAAC;AAyBH,eAAO,MAAM,QAAQ;;;;;;;CAapB,CAAC"}

package/dist/examples/nft/nft-token-creation.d.ts

@@ -1,22 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * NFT Token Creation Demo
- *
- * Demonstrates NFT token class creation and minting:
- * - createNftTokenClass() - Create a token class within a collection
- * - mintNft() - Mint NFT instances from a token class
- * - fetchTokenClasses() - Query existing token classes
- *
- * Shows the workflow for creating token classes and minting NFTs,
- * including parameter validation and cost estimations.
- */
-export declare const runNftTokenCreationDemo: import("../utils").WrappedDemoFunction;
-export declare const metadata: {
-    name: string;
-    description: string;
-    category: string;
-    sdkMethods: string[];
-    requiresAuth: boolean;
-    requiresWallet: boolean;
-};
-//# sourceMappingURL=nft-token-creation.d.ts.map

package/dist/examples/nft/nft-token-creation.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nft-token-creation.d.ts","sourceRoot":"","sources":["../../../examples/nft/nft-token-creation.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;GAUG;AAeH,eAAO,MAAM,uBAAuB,wCAsPlC,CAAC;AAqBH,eAAO,MAAM,QAAQ;;;;;;;CAcpB,CAAC"}

package/dist/examples/nft/nft-utilities.d.ts

@@ -1,23 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * NFT Utilities Demo
- *
- * Demonstrates NFT utility and validation methods:
- * - isNftCollectionAvailable() - Check if a collection name is available
- * - fetchUserCollections() - List authorized collections for validation
- * - getNftCollectionClaimFee() - Get collection claim fee
- * - fetchAvailableBalance() - Check wallet balance
- *
- * Shows validation patterns and utility operations for NFT collection
- * management, helping ensure data integrity before operations.
- */
-export declare const runNftUtilitiesDemo: import("../utils").WrappedDemoFunction;
-export declare const metadata: {
-    name: string;
-    description: string;
-    category: string;
-    sdkMethods: string[];
-    requiresAuth: boolean;
-    requiresWallet: boolean;
-};
-//# sourceMappingURL=nft-utilities.d.ts.map

package/dist/examples/nft/nft-utilities.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nft-utilities.d.ts","sourceRoot":"","sources":["../../../examples/nft/nft-utilities.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;GAWG;AAcH,eAAO,MAAM,mBAAmB,wCA4Q9B,CAAC;AAsBH,eAAO,MAAM,QAAQ;;;;;;;CAapB,CAAC"}

package/dist/examples/orchestrator-master.d.ts

@@ -1,22 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Master Orchestrator - Comprehensive demo execution with category filtering
- *
- * Runs demos against localhost:4000 environment with flexible category selection.
- * Tracks success/failure for each demo and provides comprehensive reporting.
- *
- * Usage:
- *   npm run demo:all                           # Run all demos
- *   npm run demo:all -- --dry-run              # Preview demos (no execution)
- *   npm run demo:all -- --category=bridge,dex  # Run only bridge and dex demos
- *   npm run demo:all -- --only=liquidity       # Alias for --category
- *   npm run demo:all -- --skip=fees,streaming  # Run all except fees and streaming
- *   npm run demo:all -- --list-categories      # Show available categories
- *
- * Environment: ALWAYS localhost:4000 (development/testing)
- * - No STAGE or production execution
- * - Unlimited monopoly money for testing
- * - Full state control for demos
- */
-export {};
-//# sourceMappingURL=orchestrator-master.d.ts.map

package/dist/examples/orchestrator-master.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"orchestrator-master.d.ts","sourceRoot":"","sources":["../../examples/orchestrator-master.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;GAkBG"}

package/dist/examples/orchestrator-tasks.d.ts

@@ -1,38 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Task-Based Demo Batch Orchestrator - Transparent demo execution with batch tracking
- *
- * Divides all 193 demos into controllable batches and executes them with clear,
- * trackable progress through Claude Code's Task system. Each demo and batch is
- * created as a separate Task for full transparency and progress tracking.
- *
- * Usage:
- *   npm run demo:tasks                # Run all demos in 10 batches (20 per batch)
- *   npm run demo:tasks:small          # Run demos in 20 batches (10 per batch)
- *   npm run demo:tasks:large          # Run demos in 7 batches (30 per batch)
- *
- * Architecture:
- * - Divide 193 demos into batches
- * - For each batch:
- *   1. Create parent batch Task
- *   2. Create individual demo Tasks
- *   3. Execute all demos in batch in parallel (Promise.all)
- *   4. Wait for all to complete
- *   5. Update batch Task with results
- * - Display final summary
- *
- * Benefits:
- * ✅ Each demo is a trackable Task (user's explicit request)
- * ✅ Parallel execution within batches (maintains performance)
- * ✅ Sequential batch execution (prevents overwhelming Task list)
- * ✅ Clear progress indicators (batch 1/10, demo 5/20 in batch)
- * ✅ No invisible background processes
- * ✅ Full transparency through Task system
- *
- * Environment: ALWAYS localhost:4000 (development/testing)
- * - No STAGE or production execution
- * - Unlimited monopoly money for testing
- * - Full state control for demos
- */
-export {};
-//# sourceMappingURL=orchestrator-tasks.d.ts.map

package/dist/examples/orchestrator-tasks.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"orchestrator-tasks.d.ts","sourceRoot":"","sources":["../../examples/orchestrator-tasks.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG"}

package/dist/examples/overseers/claim-invite.d.ts

@@ -1,31 +0,0 @@
-/**
- * Claim Overseer Invite Demo
- *
- * Demonstrates claiming overseer invites and platform oversight functions.
- * Overseers have global platform moderation capabilities.
- *
- * **Key Difference from Moderators:**
- * - Moderators: Token-scoped access (invited per-token)
- * - Overseers: GLOBAL access (MANAGER on ALL tokens)
- *
- * **Prerequisites:**
- * - JWT authentication required for claiming invites
- * - A valid invite code (obtained from admin or existing overseer)
- *
- * **Security Warning:**
- * Overseers have MANAGER-level permissions across ALL tokens on the platform.
- * Only grant overseer access to highly trusted platform administrators.
- *
- * @example
- * ```bash
- * # Basic run (shows workflow without actual claiming)
- * npm run demo:overseers:claim-invite
- *
- * # With an actual invite code
- * OVERSEER_INVITE_CODE=xyz789... npm run demo:overseers:claim-invite
- * ```
- *
- * @since 5.9.0
- */
-export declare const runClaimOverseerInviteDemo: import("../utils").WrappedDemoFunction;
-//# sourceMappingURL=claim-invite.d.ts.map

package/dist/examples/overseers/claim-invite.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"claim-invite.d.ts","sourceRoot":"","sources":["../../../examples/overseers/claim-invite.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAMH,eAAO,MAAM,0BAA0B,wCA0LrC,CAAC"}

package/dist/examples/overseers/demo-list-users.d.ts

@@ -1,19 +0,0 @@
-/**
- * Overseer User Management Demo
- *
- * This example demonstrates overseer (admin) user management:
- * - List users with filtering and pagination
- * - Sort by different criteria
- * - Search for specific users
- * - Get detailed user summary with activity metrics
- *
- * Requires overseer/admin authentication.
- *
- * @example
- * ```bash
- * # Run with overseer credentials
- * PRIVATE_KEY=0x... ENVIRONMENT=production npm run demo:overseers:users
- * ```
- */
-export {};
-//# sourceMappingURL=demo-list-users.d.ts.map

package/dist/examples/overseers/demo-list-users.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"demo-list-users.d.ts","sourceRoot":"","sources":["../../../examples/overseers/demo-list-users.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG"}

package/dist/examples/overseers/direct-promotion.d.ts

@@ -1,39 +0,0 @@
-#!/usr/bin/env tsx
-/**
- * Overseer Direct Promotion Demo
- *
- * This example demonstrates the direct overseer promotion workflow:
- * - Promote a user to overseer directly (bypassing invite flow)
- * - Verify the new overseer's status
- * - Optionally revoke the overseer access
- *
- * **Key Use Cases:**
- * - CLI admin tools for quick promotions
- * - Automated testing with self-contained overseer setup
- * - Programmatic access management without user interaction
- *
- * **Key Difference from Invite Flow:**
- * - Invite Flow: Create invite → Share link → User claims
- * - Direct Flow: Admin/Overseer promotes user immediately
- *
- * **Prerequisites:**
- * - Admin API key (recommended) OR existing Overseer JWT
- * - Target address to promote (defaults to current wallet for demo)
- *
- * **Security Warning:**
- * This bypasses the invite claim step. Only use when you have verified
- * the target user's identity through other means.
- *
- * @example
- * ```bash
- * # Run with admin API key (recommended)
- * STREAM_ADMIN_API_KEY=key123 PRIVATE_KEY=0x... ENVIRONMENT=development tsx examples/overseers/direct-promotion.ts
- *
- * # Run with existing overseer JWT
- * PRIVATE_KEY=0x... ENVIRONMENT=development tsx examples/overseers/direct-promotion.ts
- * ```
- *
- * @since 8.3.0
- */
-export declare const runOverseerDirectPromotionDemo: import("../utils").WrappedDemoFunction;
-//# sourceMappingURL=direct-promotion.d.ts.map

package/dist/examples/overseers/direct-promotion.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"direct-promotion.d.ts","sourceRoot":"","sources":["../../../examples/overseers/direct-promotion.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmCG;AAQH,eAAO,MAAM,8BAA8B,wCAmNzC,CAAC"}

package/dist/examples/overseers/invite-management.d.ts

@@ -1,38 +0,0 @@
-/**
- * Overseer Invite Management Demo
- *
- * This example demonstrates the complete overseer invite lifecycle:
- * - Creating overseer invites (global platform access)
- * - Listing all overseer invites
- * - Getting invite details by code (public endpoint)
- * - Checking your own overseer status
- * - Revoking invites
- * - Claiming invites (as the invited user)
- * - Listing all overseers
- * - Revoking overseer access
- *
- * **Key Difference from Moderators:**
- * - Moderators: Token-scoped access (invited per-token)
- * - Overseers: GLOBAL platform access (all tokens, current and future)
- *
- * **Prerequisites:**
- * - Admin API key OR existing Overseer JWT for most operations
- * - JWT authentication required for claiming invites
- *
- * **Security Warning:**
- * Overseers have MANAGER-level permissions across ALL tokens on the platform.
- * Only grant overseer access to highly trusted platform administrators.
- *
- * @example
- * ```bash
- * # Run with admin API key (preferred)
- * STREAM_ADMIN_API_KEY=key123 PRIVATE_KEY=0x... ENVIRONMENT=development npm run demo:overseers
- *
- * # Run with existing overseer JWT
- * PRIVATE_KEY=0x... ENVIRONMENT=development npm run demo:overseers
- * ```
- *
- * @since 5.9.0
- */
-export declare const runOverseerInviteManagementDemo: import("../utils").WrappedDemoFunction;
-//# sourceMappingURL=invite-management.d.ts.map

package/dist/examples/overseers/invite-management.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"invite-management.d.ts","sourceRoot":"","sources":["../../../examples/overseers/invite-management.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmCG;AAMH,eAAO,MAAM,+BAA+B,wCA8Q1C,CAAC"}