Skip to content

armgit / ruflo

Public Imported from GitHub
0

🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

Merge PR #3517 (mmrRerank) into release/3.55.0

ruv57a7e34b596b
diff --cc docs/dream-cycle/LEDGER.md
index 410d9af1a1,98b6474543..75a2e124b5
--- a/docs/dream-cycle/LEDGER.md
+++ b/docs/dream-cycle/LEDGER.md
@@@ -216,9 -216,6 +216,13 @@@ as a first-class, high-priority candida
| 2026-09-20 | performance | `UnifiedSwarmCoordinator.waitForTaskCompletion()`/`waitForQueuedTask()` busy-polled `state.tasks` via `setInterval(...,100)` despite the coordinator already extending `EventEmitter` and already firing `task.completed`/`task.failed` at every terminal task-status transition (`handleTaskComplete`, `handleTaskFail`'s non-retry branch, `cancelTask`) — the exact candidate 2026-09-15 scored 4.45/5 but deferred; tonight's independent research re-scored it 4.75/5 and selected it | #3377 | #3378 | yes | ACCEPT | 4 new discriminating tests, baseline-fails-3-of-4/candidate-passes-4-of-4 via stash isolation; real wall-clock benchmark 100.359ms→0.206ms mean (~487x, N=20); 234/234 full-suite both ways (230 pre-existing + 4 new), `tsc` clean; independent adversarial critique CONFIRMED-WITH-CAVEATS→fixed (missing `setMaxListeners` would have spammed `MaxListenersExceededWarning` at >10 concurrent waiters; fixed same session, re-verified) | 12f7a08e... | 09-15..09-19 (5 nights) all open/draft, none stale; pre-09-14 backlog (18 PRs) fully cleared 2026-09-14 |
+**Note (2026-09-30):** GitHub-verified fates for the trailing 6 nights before tonight's own row (via `pull_request_read`, `gh` CLI unavailable this session — same MCP-tools fallback used since 09-17): #3385 (09-21, security) **MERGED** 2026-09-26; #3395 (09-22, intelligence) **MERGED** 2026-09-26; #3412 (09-24, off-cycle `github-safe.js` disclosure fix for issue #3411) **MERGED** 2026-09-26; #3476 (09-27, intelligence) OPEN/draft, 3d, no reviewer engagement yet; #3517 (09-28, memory) OPEN/draft, 2d; #3539 (09-29, swarm) OPEN/draft, 1d — none stale (<14d). Confirmed no-run gaps at 09-23, 09-25, 09-26 (no `dream/*` branches) via `git ls-remote --heads origin "dream/*"`. Could not score the 09-29 gist (STEP 1.2) — never committed to `docs/dream-cycle/` and no gist-publishing tool was available this session to fetch it from a published URL either; noted rather than fabricated. **Gist publishing itself was unavailable tonight** (no `gh` CLI binary, no MCP gist-creation tool, `WebFetch` 403s on the unauthenticated GitHub API) — the full SOTA report is embedded verbatim in issue #3562 instead of a `gist.github.com` URL; future nights should flag this as a standing environment gap, not re-attempt and silently give up each time.
+
+| 2026-09-30 | performance | `MessageBus.processQueues()` dispatched via an unconditional `setInterval(processingIntervalMs, default 10ms)` regardless of queue occupancy — both production callers (`UnifiedSwarmCoordinator`, `SwarmHub`) configure 10ms, so every active swarm's message bus woke up 100x/sec at zero traffic; sibling of the 09-20 UnifiedSwarmCoordinator busy-poll fix, same coordinator, different still-unfixed component. Wired event-driven dispatch (`scheduleProcessing()` triggered from `enqueue()`/retry-requeue/`subscribe()`), backstop interval floored at 250ms, `processQueues()` self-reschedules under backlog | #3562 | #3563 | yes | ACCEPT-scoped (post-review) | 7 new discriminating tests, baseline-fails/candidate-passes via stash isolation; real wall-clock benchmark: idle-window `processQueues()` calls 196→7/2s (96.5% reduction), single-message latency 10.157ms→0.083ms mean, saturated throughput (2000 msgs) 985→87,896 msg/s; full `@claude-flow/swarm` suite 237/243 (baseline, 6 new tests fail)→244/244 (candidate); `tsc --noEmit` clean both; independent adversarial critique CONFIRMED-WITH-CAVEATS→2 caveats (subscribe-gap latency, shutdown-timer guard) both fixed same session, re-verified; an earlier candidate version had a real saturated-throughput regression (collapsed to ~200 msg/s) caught by the candidate's own perf test before review, fixed via self-rescheduling on backlog | 72521458... | 09-21..09-24 (3 nights) MERGED 2026-09-26; 09-27..09-29 (3 nights) open/draft, none stale |
+**Note (2026-09-29):** a large batch-merge landed 2026-09-26 clearing the 09-17..09-22 backlog (#3350/#3352/#3357/#3385/#3395 all MERGED; #3378 closed-not-merged but landed via #3443 and shipped to npm via #3452 — effectively merged). Three more nights ran since and aren't yet reflected as rows here (still open drafts, verified via `git branch -r`/PR lookup, not a pipeline failure): 09-24 (`github-safe-artifact-parity`, #3412, closed-not-merged), 09-27 (intelligence, #3476, open), 09-28 (memory, #3517, open). 09-16 (security, #3339) remains open/draft awaiting final review on its round-2 hive-mind auth hardening, not stale.
+
+| 2026-09-29 | swarm | `UnifiedSwarmCoordinator.spawnAgent()`'s auto-domain branch (no `domain`/`agentNumber` given) registered the agent but never called `pool.add()`, unlike the other two branches — `assignTaskToDomain()` routes exclusively via `pool.acquire()`, so the agent was invisible to it: a task either scale-up-created a *different* orphaned agent or queued forever, while the originally spawned agent sat idle and permanently unused | #3538 | #3539 | yes | ACCEPT-scoped | 4 new discriminating tests, baseline-fails-2-of-3/candidate-passes-3-of-3 via stash isolation, independently reproduced byte-identical by an adversarial critic; full `@claude-flow/swarm` suite 237/237→241/241 (+4 new), 0 regressions, `tsc --noEmit` clean; independent adversarial critique CONFIRMED-WITH-CAVEATS→fixed (round-1 fix's new `pool.add()` call threw once a small domain pool, e.g. `queen` cap 1, was at capacity — a regression vs. baseline's silent-but-buggy success; wrapped in try/catch + new `agent.domain_pool_full` event, re-verified) | 7fca8c14... | 09-24 (closed-not-merged), 09-27/09-28 (open drafts, not stale); 09-17..09-22 backlog MERGED 2026-09-26; 09-16 still open/draft (round 2), not stale |
++
+ **Note (2026-09-28):** verified via GitHub MCP tools (`gh` CLI unavailable this session, same FALLBACK-for-gist-only condition since 2026-09-17): a second bulk human-review pass landed 2026-09-26, closing most of the 09-15..09-22 backlog (spot-verified 2/2 as genuinely `merged:true` via `pull_request_read`, not trusting `search_pull_requests`'s own unreliable `merged` field per the 2026-09-21 note) — #3395 (09-22, intelligence) and several others now MERGED. Still OPEN/draft: #3339 (09-16, security, round-2 hive-mind auth, 811 lines — larger scope, human review pending) and #3476 (09-27, intelligence, `CLAUDE_FLOW_FISHER_DECAY` env override). Also observed: #3412 (`dream/2026-09-24-github-safe-artifact-parity`, MERGED 2026-09-26) — a real security fix for issue #3411, not a standard Dream Cycle DEEP/SCAN rotation, so not given its own ledger row. No branch/PR found for 2026-09-23, 2026-09-25, or 2026-09-26 — consistent with the recurring no-run-gap pattern (08-20..23, 09-13/14).
+
+ | 2026-09-28 | memory | `mmrRerank()`'s embedding-cosine path (`smart-retrieval.ts`) recomputed max-similarity-to-selected against the *entire* selected set on every outer-loop pass (≈O(candidates×selected²)), even after #3169/#3266 already made the Jaccard-fallback tokenization lazy — flagged grade-A by 2026-09-27's own memory scan (still-open #3476) and acted on directly tonight; replaced with a running per-candidate max-similarity cache (one new comparison per candidate per round, folded via `Math.max`, algebraically identical to recomputing the max from scratch) | #3516 | #3517 | yes | ACCEPT | byte-identical selection order across 5 scenarios (all/none/half-embedded, lambda extremes, a dedicated negative-cosine zero-floor case); wall-clock 686.5ms→<343.3ms (>2x, N=200/limit=100), stash-isolated baseline-fails/candidate-passes on this exact assertion; frozen-copy call-count comparison used instead of `vi.spyOn` after a debug test showed Vitest's ESM spy can't intercept same-module internal calls (flagged as a likely latent issue in the sibling 09-10 `tokenize()` call-count test, not fixed retroactively); 564/565 full `@claude-flow/memory` suite both ways (1 pre-existing environmental failure, unchanged), `tsc --noEmit` 0 errors both ways | 85e464a6... | 09-16 (#3339) still open/draft; 09-27 (#3476) still open/draft; 09-15..09-22 backlog mostly MERGED in a 2026-09-26 bulk review batch; no-run gap 09-23/09-25/09-26 |