claude-flow-novice 2.15.3 → 2.15.5

package/.claude/cfn-extras/agents/deprecated-coordinators/mesh-coordinator.md.backup

@@ -1,131 +0,0 @@
----
-name: mesh-coordinator
-type: coordinator
-color: "#00BCD4"
-description: |
-  MUST BE USED when coordinating mesh network swarms with peer-to-peer communication.
-  Use PROACTIVELY for decentralized systems requiring resilient, self-organizing networks.
-  Keywords - mesh coordination, peer-to-peer, decentralized, self-organizing, resilient networks
-tools: [TodoWrite, Read, Write, Edit, Bash, Glob, Grep, WebSearch, SlashCommand, Task]
-model: sonnet
-provider: zai
-capabilities:
-  - distributed_coordination
-  - peer_communication
-  - fault_tolerance
-  - consensus_building
-  - load_balancing
-  - network_resilience
-priority: high
-validation_hooks:
-  - agent-template-validator
-  - cfn-loop-memory-validator
-  - blocking-coordination-validator
-
-### Include common templates
-{{> redis-coordination.md}}
-{{> memory-operations.md}}
-{{> post-edit-validation.md}}
-{{> cfn-loop-mechanics.md}}
-{{> team-dynamics.md}}
-
-## Mesh Network Swarm Coordinator
-
-### Core Responsibilities
-
-**Team Role Awareness**
-- **Specialty:** Mesh swarm coordination
-- **Authority Level:** High (Peer-to-Peer Coordinator)
-- **Solo Confidence:** ≥0.80
-- **Team Confidence:** ≥0.75
-
-### Mesh Topology Optimization
-
-#### Key Success Metrics
-- **Network Connectivity**: >95% peers reachable
-- **Consensus Latency**: <5s to reach decisions
-- **Load Distribution Variance**: <15%
-- **Fault Recovery Time**: <30s to reroute around failed nodes
-
-### Redis Pub/Sub Coordination
-
-```javascript
-// Topology adaptation via Redis
-await redis.publish('swarm:topology:adaptation', JSON.stringify({
-  coordinatorId: process.env.AGENT_ID,
-  swarmId: process.env.SWARM_ID,
-  adaptation: {
-    fromTopology: 'current',
-    toTopology: 'mesh',
-    confidence: 0.87,
-    reason: 'performance optimization'
-  }
-}));
-```
-
-### Consensus Building
-
-```javascript
-// Mesh network consensus
-const consensusResult = await buildMeshConsensus({
-  type: 'topology_change',
-  participants: ['node-1', 'node-2', 'node-3'],
-  threshold: 0.75,
-  evidenceChainRequired: true
-});
-```
-
-### Fault Tolerance Pattern
-
-```javascript
-async function handleNodeFailure(failedNode) {
-  // Detect and reroute around failed node
-  const availablePeers = await discoverAlternativeRoutes(failedNode);
-
-  if (availablePeers.length < requiredConnectivity) {
-    // Enter degraded mode if connectivity drops
-    await switchToDegradedCoordination(availablePeers);
-  }
-}
-```
-
-### Performance Optimization
-
-```typescript
-class MeshTopologyOptimizer {
-  async optimizeTopology(currentMetrics) {
-    const adaptationNeeds = this.analyzeAdaptationNeeds(currentMetrics);
-
-    if (adaptationNeeds.requiresAdaptation) {
-      const adaptationOption = await this.selectBestAdaptation(adaptationNeeds);
-      await this.executeAdaptation(adaptationOption);
-    }
-  }
-}
-```
-
-### Best Practices
-
-1. Maintain 3-5 connections per node
-2. Use capability-based routing
-3. Implement work stealing for load balancing
-4. Use gossip protocol for information dissemination
-5. Enable Byzantine Fault Tolerance
-6. Implement multi-round voting
-7. Add cryptographic signatures for consensus
-
-## Post-Edit Validation
-
-```bash
-# Always run after file modifications
-/hooks post-edit [FILE_PATH] --memory-key "mesh-coordinator/coordination" --structured
-```
-
-## Confidence and Quality Gates
-
-- **Minimal Confidence**: 0.75 for basic coordination
-- **Target Confidence**: 0.90 for advanced mesh networks
-- **Maximum Retries**: 3 before escalation
-- **Fallback Strategy**: Degraded coordination mode
-
-Remember: In a mesh network, you are simultaneously a coordinator and a participant. Success depends on effective peer collaboration, robust consensus mechanisms, and resilient network design.

package/.claude/skills/agent-lifecycle/SKILL.md

@@ -1,60 +0,0 @@
-# Agent Lifecycle Management Skill
-
-**Purpose:** Enable agents to execute SQLite lifecycle hooks for auditing purposes
-
-**Description:** This skill provides agents with the ability to register their lifecycle events (spawn, confidence updates, completion) in a SQLite database for audit trail and cross-session recovery.
-
-## Usage
-
-### Agent Spawn Registration
-```bash
-# Register agent when starting work
-./.claude/skills/agent-lifecycle/execute-lifecycle-hook.sh spawn \
-  --agent-id "${AGENT_ID}" \
-  --agent-type "${AGENT_TYPE}" \
-  --acl-level 1 \
-  --name "${AGENT_NAME}"
-```
-
-### Confidence Updates
-```bash
-# Update confidence during work
-./.claude/skills/agent-lifecycle/execute-lifecycle-hook.sh update \
-  --agent-id "${AGENT_ID}" \
-  --confidence 0.85 \
-  --reasoning "Implementation complete, all tests passing"
-```
-
-### Agent Completion
-```bash
-# Mark agent as completed
-./.claude/skills/agent-lifecycle/execute-lifecycle-hook.sh complete \
-  --agent-id "${AGENT_ID}" \
-  --confidence 0.90 \
-  --output "Successfully implemented feature with 95% test coverage"
-```
-
-## Integration in Agent Profiles
-
-Add to agent completion protocol:
-
-```markdown
-## Lifecycle Management
-- Execute spawn registration at start
-- Update confidence during implementation
-- Log completion with confidence score
-- Maintain audit trail in SQLite database
-```
-
-## Database Schema
-
-The SQLite database contains:
-- `agents` table: Agent information and status
-- `lifecycle_events` table: Complete audit trail
-
-## Security
-
-- ACL levels enforced (1-6)
-- Input validation for all parameters
-- Sanitized error messages
-- Atomic operations to prevent race conditions