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

dream(performance): #3562 update ledger for tonight's MessageBus finding

Claude6ecb6acb7491
diff --git a/docs/dream-cycle/LEDGER.md b/docs/dream-cycle/LEDGER.md
index 16fc6f4567..cb9f7e4b11 100644
--- a/docs/dream-cycle/LEDGER.md
+++ b/docs/dream-cycle/LEDGER.md
@@ -215,3 +215,7 @@ as a first-class, high-priority candidate, not a background note.
**Note (2026-09-20):** the pre-09-14 backlog (#3086 through #3302, ~18 PRs) was fully cleared by human review on 2026-09-14 (confirmed via `search_pull_requests`: every one now shows `state: closed`) — the "0 of last 14 merged" bias condition from earlier nights no longer applies. Nights 09-15 (performance, #3330), 09-16 (security, #3339), 09-17 (intelligence, #3350), 09-18 (memory, #3352), and 09-19 (swarm, #3357) all ran and produced real branches/issues/draft PRs (verified via `git ls-remote`/`search_pull_requests`, not inferred) but aren't transcribed as rows here — same "ledger rows only reach `main` via PR merge" structural gap noted since 2026-08-19/09-03/09-05/09-09; none of the five is stale (>14d) as of tonight. Not backfilling their full rows here to avoid yet another copy stranded on yet another unmerged branch (per the 2026-09-03 note's own reasoning) — see their own PR bodies (#3330/#3339/#3350/#3352/#3357) for full detail.
| 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 |