The Ruflo Nightly Dream Cycle cloud routine (trig_01HpEqAcEP7wzrxy3TzakrQ2)
was updated to v2: parallel research via the Task tool, claude-sonnet-5,
expanded toolset (TodoWrite/Skill/MultiEdit/BashOutput/KillBash), and a new
STEP 3.5 that attempts a real Flywheel evaluation (metaharness bench/evolve)
for harness-shaped findings instead of always stopping at a docs-only PR.
This file is the durable cross-night memory the new STEP 1 reads before
touching gh at all -- a fresh cloud checkout otherwise has zero continuity
beyond a gh issue list grep, which is what v1 relied on for 80 nights.
Backfilled from the full issue history: 4 shipped (5%), 1 rejected, 75
(94%) never touched, some >2.5 months stale. v2 uses this to bias toward
attempting evaluation over another research-only proposal when the
trailing merge rate is 0.
* fix(migrate,mcp): unresolvable remediation command + false-success HTTP server exit
Two independently-reported, freshly-filed defects:
- #2985: `ruflo migrate status`'s ADR-128 removed-agent remediation
(shipped today via #2973/ADR-382 Part B) printed a command that cannot
succeed twice over: `ruflo plugins install <plugin>` requires -n/--name
(not a positional) AND targets the npm-package plugin system, while the
gap detector's own registry check (installed_plugins.json) is for the
Claude Code marketplace system entirely. Fixed to print the correct
`/plugin install <plugin>@ruflo` slash-command flow, with a one-time
"run /plugin marketplace add ruvnet/ruflo first" hint. Also corrects
three adjacent doc-drift items the reporter found while verifying:
README/USERGUIDE's `claude mcp add ruflo` examples (should be the
canonical `claude-flow` key per #2206 — the exact stray-key duplicate
#2612's healing logic exists to clean up), README's blanket "MCP server
registered: No" claim for the plugin path (ruflo-core ships its own
.mcp.json and does register one), and a stale comment in executor.ts
conflating the CLI-track's mcp__claude-flow__* tool refs with the
marketplace plugin binding (mcp__plugin_<plugin>_<server>__*).
- #2984: `ruflo mcp start -t http` printed a full "Status: Running"
success table — PID, health/RPC URLs — then exited 0 within seconds,
never actually leaving the port bound. Root cause: bin/cli.js's
"normal CLI mode" branch (which any explicit non-stdio --transport
always takes) unconditionally exits once the dispatched command's
action() promise resolves (#1552's "one-shot command" assumption).
mcp.ts's `start` action returned immediately after printing the table,
so the freshly-bound http.Server was torn down within milliseconds of
the printed success claim. Fixed by blocking in the foreground after a
successful start (SIGINT/SIGTERM-driven graceful shutdown), matching
daemon.ts's established `--foreground` pattern — `daemonize` isn't
currently wired to fork/detach anywhere in MCPServerManager, so every
successful start via this path is a foreground server regardless of
the -d flag.
Tests: migrate-agent-detection.test.ts updated for the corrected command
string; new mcp-http-foreground-2984.test.ts spawns the built CLI exactly
like the bug report and asserts the port actually accepts connections
after the success table prints (not just that it printed), then confirms
SIGTERM still produces a clean exit. Both verified via git-stash A/B:
fail against the pre-fix code, pass against the fix.
Full suite otherwise unaffected — same 9 pre-existing sandbox-environment
failures (ruvector/wasm bindings, embedder model downloads) reproduced
identically before this change.
Closes#2985. Closes#2984.
Co-Authored-By: RuFlo <ruv@ruv.net>
* revert: drop migrate-agent-detection changes, superseded by PR #2986
An external contributor (pacphi) independently opened #2986 fixing the
same #2985 with the identical installCommand correction plus a real
`migrate fix --agents` restore command — strictly more complete than
this branch's minimal fix. Dropping the overlapping files here to avoid
a duplicate/conflicting PR; reviewed #2986 and recommended it for merge.
Remaining on this branch: the #2984 mcp start -t http fix and the
doc-drift items #2986 explicitly scoped out (README/USERGUIDE mcp-add
key, executor.ts comment).
Co-Authored-By: RuFlo <ruv@ruv.net>
The dream-cycle bot has opened a research proposal draft PR nightly since
2026-05-29. None had ever been merged (tracked in #2324), so each night's
run guessed ADR numbers against a stale view of main and collided
repeatedly — ADR-147 alone was independently claimed by 4 different
proposals (#2304, #2310, #2317, plus a README-only PR #2278), and ADR-179
by another 4 (#2617, #2624, #2631, #2656, plus README-only #2642).
This consolidates the SOTA research reports and ADR proposal text from
all 49 open dream-cycle drafts into a single reviewable change:
- 43 ADR proposals renumbered sequentially into ADR-334 through ADR-376
(first-opened-first-numbered), with self-referencing ADR-N mentions
inside each file updated to match
- 4 branches that contained only a SOTA report with no ADR proposal
(#2368, #2382, #2430, #2607) carried over as-is
- 2 branches that only added a README index row for an ADR file they
didn't otherwise include (#2278 for ADR-147, #2642 for ADR-179) are
superseded by the real ADR-147/179 claimants above and dropped
- v3/docs/adr/README.md gets one clean set of index rows instead of 43
individually conflicting ones
All ADRs land as Proposed — none of this is an implementation decision,
just clearing 2 months of unreviewed nightly research out of PR limbo so
it can actually be read. The original 49 PRs are closed with a pointer
to this commit.
Closes#2224, #2242, #2249, #2255, #2266, #2278, #2304, #2310, #2317, #2333, #2344, #2363, #2368, #2379, #2382, #2394, #2402, #2420, #2430, #2436, #2457, #2463, #2472, #2479, #2486, #2496, #2511, #2527, #2537, #2560, #2577, #2598, #2607, #2617, #2624, #2631, #2642, #2656, #2665, #2702, #2716, #2728, #2740, #2753, #2761, #2764, #2769, #2779, #2793
* feat(mcp): integrate agenticow@~0.2.3 — Copy-On-Write memory branching (4 MCP tools)
Adds 4 MCP tools wrapping agenticow's COW vector primitives:
- agenticow_branch fork a base .rvf at ~162 bytes regardless of size
- agenticow_checkpoint freeze a restore point on a memory file
- agenticow_rollback discard edits since most recent checkpoint
- agenticow_promote merge a branch's edits into a base
Architectural rule (mirrors ADR-150 metaharness pattern):
agenticow is in optionalDependencies — never a hard runtime dep.
Missing package → `{success: true, degraded: true, reason: 'agenticow-not-found'}`.
Motivating use case: the v3.14.4 release uncovered a 3.3 GB tarball-bloat
regression where Darwin loops' git-worktree-per-agent pattern accumulated
full-copy snapshots. Measured agenticow branches are exactly 162 bytes
regardless of base size — the structural fix.
Verified perf vs published claims (docs/agenticow/findings.md):
✅ 162-byte branches — confirmed exact at N=1k, 10k, 50k
✅ 3,200×–180,000× smaller than full-copy across N
❌ "0.5ms branch" — measured ~10ms (fixed cost, not size-proportional)
❌ "83× faster" — crossover ≈ N=30k; below that, full-copy wins
Tests: 7/7 in __tests__/agenticow-tools.test.ts
Smoke: 8/8 in scripts/smoke-agenticow.sh (registration + end-to-end cycle)
Co-Authored-By: RuFlo <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_01WbBa4nccx5aGhXphoHxcni
* fix(mcp): comply with ADR-112 tool-discoverability lint on agenticow tools
The audit-tool-descriptions.mjs regex only captures the first quoted string
in a `'foo ' + 'bar'` concat, so my multi-line descriptions hid the "Use when"
guidance from the linter. Collapsed all 4 agenticow tool descriptions to single
string literals; ADR-112 audit now reports 345/345 pass.
No behavior change — descriptions are byte-identical at runtime.
Co-Authored-By: RuFlo <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_01WbBa4nccx5aGhXphoHxcni
skill-distillation breakthrough: AND→OR predicate relax took the metric from
0.4286 → 0.8571 (+100% rel), exceeding the SKILL-DISCO arXiv 2026 +22% target
by 4.5x on the synthetic ADR-155 bench. 6/7 successful traces now promoted
vs the original 3/7.
causal-graph: EXISTS-probe early-exit on missing seed → 115ms → 0ms for the
absent-seed case. Test 5e in graph-query smoke now exits in O(1) vs O(N).
21/21 smoke tests still pass.
reasoning-bank: tried bm25=0.15 (up from 0.05 tick 2 champion), regressed
-0.0062. Confirms bm25=0.05 is the LOCAL OPTIMUM on this axis.
sona-adapt: still at-target.
hnsw-search + moe-gate: still bench-timeout (benchmark-intelligence.mjs has
issues at small N. Tick 4 should investigate the script directly).
Added scifact-specific RRF weights {dense:1.0, bm25:0.4} to DATASET_RRF_WEIGHTS,
mirroring the nfcorpus pure-dense strategy. Clinical fact verification benefits
from dense semantic matching over lexical noise. Benchmarked on 300 queries,
rank 10/11 on published leaderboard (0.5971 vs SOTA 0.722).
Co-Authored-By: RuFlo <ruv@ruv.net>
rUv