claude-flow-novice 2.6.0 → 2.9.0

package/.claude/skills/transparency-middleware/wrap-agent.sh

@@ -1,132 +0,0 @@
-#!/usr/bin/env bash
-# Transparency Middleware Wrapper
-# Wraps agent execution with automatic memory capture
-
-# Strict error handling
-set -euo pipefail
-
-# Logging configuration
-LOG_DIR="/var/log/claude-flow/transparency-middleware"
-TIMESTAMP=$(date +"%Y%m%d_%H%M%S")
-
-# Validate input arguments
-if [[ $# -lt 3 ]]; then
-    echo "Error: Insufficient arguments" >&2
-    echo "Usage: $0 <AGENT_ROLE> <AGENT_ID> <TASK_ID> [ADDITIONAL_ARGS...]" >&2
-    exit 1
-fi
-
-# Parse arguments
-AGENT_ROLE="$1"
-AGENT_ID="$2"
-TASK_ID="$3"
-shift 3  # Remove first three arguments, leaving any additional args
-
-# Create log directory if it doesn't exist
-mkdir -p "${LOG_DIR}/${TASK_ID}"
-
-# Initialize middleware and pre-execution hooks
-initialize_middleware() {
-    node -e "
-    import {TransparencyMiddleware} from '../../../src/middleware/transparency-middleware.js';
-    const middleware = new TransparencyMiddleware();
-    await middleware.initialize({
-        agentRole: '${AGENT_ROLE}',
-        agentId: '${AGENT_ID}',
-        taskId: '${TASK_ID}'
-    });
-    await middleware.preExecutionHook();
-    " || {
-        echo "Middleware initialization failed" >&2
-        exit 2
-    }
-}
-
-# Capture execution metrics
-execute_agent() {
-    local log_file="${LOG_DIR}/${TASK_ID}/${AGENT_ID}_${TIMESTAMP}.log"
-    local metrics_file="${LOG_DIR}/${TASK_ID}/${AGENT_ID}_${TIMESTAMP}_metrics.json"
-
-    # Start time capture
-    local start_time=$(date +%s.%N)
-
-    # Execute the actual agent command with all remaining arguments
-    # Redirect output to log file
-    if ! "$@" 2>&1 | tee "${log_file}"; then
-        local exit_code=${PIPESTATUS[0]}
-
-        # Capture error metrics
-        node -e "
-        import fs from 'fs';
-        import {TransparencyMiddleware} from '../../../src/middleware/transparency-middleware.js';
-        const middleware = new TransparencyMiddleware();
-
-        const metrics = {
-            taskId: '${TASK_ID}',
-            agentId: '${AGENT_ID}',
-            agentRole: '${AGENT_ROLE}',
-            startTime: ${start_time},
-            endTime: $(date +%s.%N),
-            exitCode: ${exit_code},
-            status: 'FAILED'
-        };
-
-        await middleware.postExecutionHook(metrics);
-        fs.writeFileSync('${metrics_file}', JSON.stringify(metrics, null, 2));
-        " || echo "Error tracking failed"
-
-        return ${exit_code}
-    fi
-
-    # Capture successful execution metrics
-    node -e "
-    import fs from 'fs';
-    import {TransparencyMiddleware} from '../../../src/middleware/transparency-middleware.js';
-    const middleware = new TransparencyMiddleware();
-
-    const metrics = {
-        taskId: '${TASK_ID}',
-        agentId: '${AGENT_ID}',
-        agentRole: '${AGENT_ROLE}',
-        startTime: ${start_time},
-        endTime: $(date +%s.%N),
-        exitCode: 0,
-        status: 'SUCCESS'
-    };
-
-    await middleware.postExecutionHook(metrics);
-    fs.writeFileSync('${metrics_file}', JSON.stringify(metrics, null, 2));
-    " || echo "Metrics tracking failed"
-}
-
-# Main execution flow
-main() {
-    # Initialize middleware before execution
-    initialize_middleware
-
-    # Execute agent with remaining arguments
-    execute_agent "$@"
-}
-
-# Execute main function and capture its exit status
-main "$@"
-exit_status=$?
-
-# Signal completion to Redis coordination
-redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete" > /dev/null
-
-# Invoke waiting mode report
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh report \
-  --task-id "${TASK_ID}" \
-  --agent-id "${AGENT_ID}" \
-  --confidence 0.80 \
-  --iteration 1
-
-# Enter waiting mode
-./.claude/skills/redis-coordination/invoke-waiting-mode.sh enter \
-  --task-id "${TASK_ID}" \
-  --agent-id "${AGENT_ID}" \
-  --context "iteration-1-complete"
-
-# Exit with original command's exit status
-exit ${exit_status}

package/.claude/skills/web-portal/DESIGN.md

@@ -1,117 +0,0 @@
-# Web Portal Skills Wrapper: Design Specification
-
-## Architecture Overview
-
-### WebSocket Coordination Patterns
-- Core Implementation: Redis pub/sub with Socket.IO
-- Event Types: 
-  * agent_update
-  * metrics_update
-  * event_stream
-  * connection_status
-
-### API Endpoints
-1. Authentication
-   - `/api/auth/login`
-   - `/api/auth/logout`
-   - `/api/auth/refresh`
-
-2. Metrics
-   - `/api/metrics/current`
-   - `/api/metrics/historical`
-
-3. Agents
-   - `/api/agents/status`
-   - `/api/agents/hierarchy`
-
-4. Events
-   - `/api/events/stream`
-   - `/api/events/timeline`
-
-## Skill Wrapper Interface Scripts
-
-### 1. `invoke-portal-start.sh`
-- Lifecycle management for web portal server
-- Redis-coordinated startup sequence
-- Health check integration
-
-### 2. `invoke-portal-metrics.sh`
-- Retrieve current and historical metrics
-- Aggregate metrics from multiple sources
-- Store metrics in SQLite memory with project-level ACL
-
-### 3. `invoke-portal-dashboard.sh`
-- Fetch dashboard data
-- WebSocket coordination for real-time updates
-- Implement filtering and data transformation
-
-### 4. `invoke-portal-agents.sh`
-- Agent status retrieval
-- Hierarchical agent state management
-- Confidence and performance tracking
-
-### 5. `invoke-portal-events.sh`
-- Event timeline generation
-- Filter and aggregate events
-- Support for historical and real-time event streams
-
-### 6. `invoke-portal-stop.sh`
-- Graceful server shutdown
-- Clear WebSocket connections
-- Store final metrics and state
-
-## Security Considerations
-- Use project-level SQLite memory ACL
-- Implement rate limiting
-- WebSocket authentication
-- Secure event filtering
-- Payload size validation
-
-## Performance Optimizations
-- Compression for large payloads
-- Efficient Redis pub/sub patterns
-- Minimal API call overhead
-- Caching strategies for frequently accessed data
-
-## Test Suite Structure
-- 8 comprehensive test scripts
-- Cover each invoke script
-- Validate coordination mechanisms
-- Performance and security testing
-
-## Redis Coordination Channels
-- `web-portal:metrics`
-- `web-portal:agents`
-- `web-portal:events`
-- `web-portal:lifecycle`
-
-## Confidence Scoring Mechanism
-\`\`\`typescript
-interface PortalSkillConfidence {
-  overall: number;  // 0.0 - 1.0
-  metrics: number;
-  agents: number;
-  events: number;
-  performance: number;
-}
-\`\`\`
-
-## Metrics Collection Strategy
-- 5-minute rolling window
-- Per-agent and aggregate metrics
-- Confidence-based data validation
-
-## Error Handling
-- Graceful degradation
-- Retry mechanisms
-- Detailed error logging
-- Fallback data strategies
-
-## Integrations
-- Slash command `/launch-web-dashboard`
-- CFN Loop validation hooks
-- Swarm coordination primitives
-
----
-
-Confidence Score: 0.87