claude-flow-novice 2.4.0 → 2.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Claude Flow Novice — AI Agent Orchestration
|
|
2
2
|
|
|
3
|
+
**🚀 Production Status:** Redis coordination system fully deployed (Phase 7 - 2025-10-17)
|
|
4
|
+
|
|
3
5
|
---
|
|
4
6
|
|
|
5
7
|
## 1) Critical Rules (Single Source of Truth)
|
|
@@ -11,12 +13,13 @@
|
|
|
11
13
|
* Agents communicate via Redis pub/sub with explicit dependencies (see `.claude/redis-agent-dependencies.md`)
|
|
12
14
|
|
|
13
15
|
**Core Principles:**
|
|
14
|
-
* Use agents for all non-trivial work (≥
|
|
16
|
+
* Use agents for all non-trivial work (≥3 steps or multi-file/research/testing/architecture/security)
|
|
15
17
|
* **PRIMARY COORDINATOR: Use coordinator-hybrid for all multi-agent coordination** (cost-optimized CLI spawning with typed agents)
|
|
16
18
|
* Initialize swarm before multi-agent work
|
|
17
19
|
* Batch operations: spawn ALL agents (coordinator + workers) in single message
|
|
18
20
|
* Run post-edit hook after every file edit
|
|
19
21
|
* **REQUIRED: All CLI agent spawning must use explicit --agents flag with typed agents**
|
|
22
|
+
* **Context continuity:** Redis/SQLite persistence enables unlimited continuation — never stop due to context/token concerns
|
|
20
23
|
|
|
21
24
|
**Prohibited Patterns:**
|
|
22
25
|
* Main chat orchestrating agents directly — spawn coordinator to handle orchestration
|
|
@@ -25,11 +28,12 @@
|
|
|
25
28
|
* Using generic "coordinator" fallback when coordinator-hybrid available
|
|
26
29
|
* Spawning agents without explicit --agents flag (must specify types from AVAILABLE-AGENTS.md)
|
|
27
30
|
* Agent coordination without Redis pub/sub messaging — ALL agents must use Redis
|
|
28
|
-
* Running tests inside agents —
|
|
31
|
+
* Running tests inside agents — coordinator runs tests ONCE; workers read cached results from test-results.json
|
|
29
32
|
* Concurrent test runs — terminate previous runs first
|
|
30
33
|
* **Saving to project root — check `.artifacts/logs/post-edit-pipeline.log` after writes; move files if ROOT_WARNING**
|
|
31
34
|
* Creating guides/summaries/reports unless explicitly asked
|
|
32
|
-
* Asking permission to retry/advance when criteria/iterations allow
|
|
35
|
+
* Asking permission to retry/advance when criteria/iterations allow — **relaunch agents immediately when consensus <threshold and iterations <max**
|
|
36
|
+
* Stopping work due to context/token concerns — Redis/SQLite persistence handles continuation automatically
|
|
33
37
|
|
|
34
38
|
**Communication:**
|
|
35
39
|
* Use spartan language
|
|
@@ -121,15 +125,28 @@ If file created in root, hook returns `status: "ROOT_WARNING"` with `rootWarning
|
|
|
121
125
|
|
|
122
126
|
### 3.3 Safe Test Execution
|
|
123
127
|
|
|
128
|
+
**Pattern: Coordinator runs tests ONCE before spawning workers**
|
|
129
|
+
|
|
124
130
|
```bash
|
|
125
|
-
#
|
|
131
|
+
# 1. Coordinator terminates any existing test runs
|
|
132
|
+
pkill -f vitest; pkill -f "npm test"
|
|
133
|
+
|
|
134
|
+
# 2. Coordinator runs tests once and caches results
|
|
126
135
|
npm test -- --run --reporter=json > test-results.json 2>&1
|
|
127
|
-
|
|
136
|
+
|
|
137
|
+
# 3. Workers read cached results only (no test execution)
|
|
128
138
|
cat test-results.json
|
|
129
|
-
|
|
139
|
+
|
|
140
|
+
# 4. Cleanup after all work complete
|
|
130
141
|
pkill -f vitest; pkill -f "npm test"
|
|
131
142
|
```
|
|
132
143
|
|
|
144
|
+
**Rules:**
|
|
145
|
+
* Coordinator executes tests before worker spawn
|
|
146
|
+
* Workers ONLY read test-results.json (never run tests)
|
|
147
|
+
* Single test execution prevents concurrent run conflicts
|
|
148
|
+
* Cache results in test-results.json for worker consumption
|
|
149
|
+
|
|
133
150
|
### 3.4 Batching (One message = all related ops)
|
|
134
151
|
|
|
135
152
|
* Spawn all agents with Task tool in one message
|
|
@@ -197,6 +214,47 @@ mv test.txt src/test.txt # Move to suggested location
|
|
|
197
214
|
|
|
198
215
|
**→ Pattern: `.claude/coordinator-feedback-pattern.md`**
|
|
199
216
|
|
|
217
|
+
### 6.3 Dashboard Integration (Phase 5)
|
|
218
|
+
|
|
219
|
+
**Real-time Dashboard:**
|
|
220
|
+
- URL: http://localhost:3001 (RealtimeServer)
|
|
221
|
+
- WebSocket: ws://localhost:3001/ws
|
|
222
|
+
- Components: RedisCoordinationMonitor.tsx
|
|
223
|
+
|
|
224
|
+
**REST API Endpoints:**
|
|
225
|
+
| Endpoint | Method | Description |
|
|
226
|
+
|----------|--------|-------------|
|
|
227
|
+
| /api/redis/feedback | GET | Recent feedback (limit=100) |
|
|
228
|
+
| /api/redis/metrics | GET | Current metrics snapshot |
|
|
229
|
+
| /api/swarm/status | GET | Current swarm coordination status |
|
|
230
|
+
|
|
231
|
+
**CLI Monitoring Commands:**
|
|
232
|
+
```bash
|
|
233
|
+
# Monitor feedback
|
|
234
|
+
./scripts/monitor-swarm-redis.sh feedback
|
|
235
|
+
|
|
236
|
+
# Monitor CFN Loop
|
|
237
|
+
./scripts/monitor-swarm-redis.sh coordination
|
|
238
|
+
|
|
239
|
+
# Realtime dashboard launch
|
|
240
|
+
npx claude-flow-novice dashboard --port 3001
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
**Post-Spawn Validation:**
|
|
244
|
+
```bash
|
|
245
|
+
# Validate CLI agent
|
|
246
|
+
node config/hooks/post-spawn-validation.js coder-1
|
|
247
|
+
|
|
248
|
+
# Validate Task agent
|
|
249
|
+
node config/hooks/post-spawn-validation.js task_abc123 --coordinator-id coordinator-cfn
|
|
250
|
+
```
|
|
251
|
+
|
|
252
|
+
**WebSocket Event Types:**
|
|
253
|
+
- `swarm:coordination`
|
|
254
|
+
- `agent:feedback`
|
|
255
|
+
- `system:metrics`
|
|
256
|
+
- `dashboard:status`
|
|
257
|
+
|
|
200
258
|
---
|
|
201
259
|
|
|
202
260
|
## 7) Commands & Setup
|