moflo 4.9.20 → 4.9.22

package/scripts/post-install-bootstrap.mjs

@@ -41,6 +41,7 @@ import {
   existsSync,
   mkdirSync,
   readdirSync,
+  readFileSync,
   statSync,
 } from 'node:fs';
 import { dirname, join, resolve } from 'node:path';
@@ -175,9 +176,27 @@ export async function runBootstrap({
   // The source repo's .claude/ IS the truth source — we'd be copying
   // the very files we just built ON TOP of themselves, which on Windows
   // hits the same file-lock issues we're trying to avoid.
+  //
+  // Two paths can hit this branch:
+  //   1. The source's own postinstall: mofloRoot === projectRoot (path equality).
+  //   2. The DEPENDENCY's postinstall on `npm ci` of the moflo source repo:
+  //      mofloRoot = <src>/node_modules/moflo/, projectRoot = <src>/. Path
+  //      equality fails — moflo-as-its-own-devDep would clobber the source
+  //      .claude/helpers/ with the OLDER published artifacts, breaking CI
+  //      against any in-flight fixes. Detect by reading projectRoot's
+  //      package.json name and bailing whenever it's "moflo".
   if (resolve(projectRoot) === resolve(mofloRoot)) {
     return { ran: false, reason: 'moflo-self-install' };
   }
+  try {
+    const projectPkgPath = resolve(projectRoot, 'package.json');
+    if (existsSync(projectPkgPath)) {
+      const projectPkg = JSON.parse(readFileSync(projectPkgPath, 'utf-8'));
+      if (projectPkg.name === 'moflo') {
+        return { ran: false, reason: 'moflo-self-dev-install' };
+      }
+    }
+  } catch { /* unparseable package.json — fall through, treat as consumer */ }
 
   const binDir = resolve(mofloRoot, 'bin');
   if (!existsSync(binDir)) {

package/src/cli/data/model-registry.json

@@ -58,7 +58,7 @@
         "trainedOn": "2026-01-15T00:00:00.000Z",
         "accuracy": 0.94,
         "totalUsage": 12400,
-        "sourceAgent": "security-architect"
+        "sourceAgent": "security-auditor"
       }
     },
     {
@@ -172,7 +172,7 @@
         "trainedOn": "2026-01-20T00:00:00.000Z",
         "accuracy": 0.89,
         "totalUsage": 11500,
-        "sourceAgent": "performance-engineer"
+        "sourceAgent": "reviewer"
       }
     },
     {

package/.claude/agents/consensus/byzantine-coordinator.md

@@ -1,63 +0,0 @@
----
-name: byzantine-coordinator
-type: coordinator
-color: "#9C27B0"
-description: Coordinates Byzantine fault-tolerant consensus protocols with malicious actor detection
-capabilities:
-  - pbft_consensus
-  - malicious_detection
-  - message_authentication
-  - view_management
-  - attack_mitigation
-priority: high
-hooks:
-  pre: |
-    echo "🛡️  Byzantine Coordinator initiating: $TASK"
-    # Verify network integrity before consensus
-    if [[ "$TASK" == *"consensus"* ]]; then
-      echo "🔍 Checking for malicious actors..."
-    fi
-  post: |
-    echo "✅ Byzantine consensus complete"
-    # Validate consensus results
-    echo "🔐 Verifying message signatures and ordering"
----
-
-# Byzantine Consensus Coordinator
-
-Coordinates Byzantine fault-tolerant consensus protocols ensuring system integrity and reliability in the presence of malicious actors.
-
-## Core Responsibilities
-
-1. **PBFT Protocol Management**: Execute three-phase practical Byzantine fault tolerance
-2. **Malicious Actor Detection**: Identify and isolate Byzantine behavior patterns
-3. **Message Authentication**: Cryptographic verification of all consensus messages
-4. **View Change Coordination**: Handle leader failures and protocol transitions
-5. **Attack Mitigation**: Defend against known Byzantine attack vectors
-
-## Implementation Approach
-
-### Byzantine Fault Tolerance
-- Deploy PBFT three-phase protocol for secure consensus
-- Maintain security with up to f < n/3 malicious nodes
-- Implement threshold signature schemes for message validation
-- Execute view changes for primary node failure recovery
-
-### Security Integration
-- Apply cryptographic signatures for message authenticity
-- Implement zero-knowledge proofs for vote verification
-- Deploy replay attack prevention with sequence numbers
-- Execute DoS protection through rate limiting
-
-### Network Resilience
-- Detect network partitions automatically
-- Reconcile conflicting states after partition healing
-- Adjust quorum size dynamically based on connectivity
-- Implement systematic recovery protocols
-
-## Collaboration
-
-- Coordinate with Security Manager for cryptographic validation
-- Interface with Quorum Manager for fault tolerance adjustments
-- Integrate with Performance Benchmarker for optimization metrics
-- Synchronize with CRDT Synchronizer for state consistency