Ruflo 3.56.9 updates CLI behavior and carries forward RVF recovery fixes

What changed

Ruflo shipped two patch releases on October 12. Both publish @claude-flow/cli, claude-flow and ruflo together. This story covers both, because the second builds directly on the first.

Version 3.56.8 (17:40:51Z) moves the CLI from @claude-flow/shared 3.0.3 to 3.0.4. According to the release notes, the RVF event log in shared 3.0.4 now repairs an incomplete or damaged tail before it appends (PR #4031). A fresh install can also import the package's main, core and MCP entry points, because zod and express are now declared. The shared tarball we inspected contains rvf-event-log.js with that repair path, and no compiled tests.

The same release changes hooks coverage-gaps: files with no executable lines no longer count as 0%, and overall coverage is weighted by line. ruflo tui marks the AI page in its page bar when started with --view ai.

Version 3.56.9 (21:14:45Z) pins exact component versions: shared 3.0.5, cli-core 3.7.2, security 3.0.5 and codex 3.0.5. The release notes list a reviewed batch of CLI parser, retry, rate-limit, monitoring and config fixes (PR #4107), retry times that follow the rate window, structured network error codes, and an analyze diff output fix (PR #4102).

It also retires the opt-in codex backend that tried to launch @openai/codex mcp-server, a mode current Codex CLI no longer offers (PR #3522). The packaged ruflo bridge now marks that group unavailable and points to Codex dual-mode workers (codex exec) instead. Only that MCP backend is retired. Other Codex integration and the console's own AI page are not removed.

What the published packages contain

• npm lists @claude-flow/cli 3.56.9 at 21:07:25Z and ruflo 3.56.9 at 21:11:00Z, both tagged latest. Version 3.56.8 of each was published around 17:33Z to 17:38Z.
• The CLI 3.56.9 tarball we downloaded matches the registry's SHA-512 integrity value and holds 1,725 files. Its manifest pins shared 3.0.5, cli-core 3.7.2, security 3.0.5 and codex 3.0.5 exactly.
• The bundled console is at plugins/ruflo-console/dist/tui.mjs. In the 3.56.8 and 3.56.9 tarballs, that bundle includes the optional Orbital look, with Classic BBS as the default. The 3.56.7 story covers the separate console 0.43.0 release.
• The ruflo wrapper pins @claude-flow/cli 3.56.9 and requires Node 20 or later.

Some items in these release notes are not part of the npm packages. The ruflo-testgen, ruflo-sparc and ruflo-cost-tracker changes are marketplace plugins. The CI change, which runs every v3 root-suite test file, affects only the project's own pipeline.

Get started

Use Node 20 or later in a disposable project. The first command only asks the registry for the version and should print 3.56.9. The second uses options documented in the packaged tui help: it prints one plain terminal frame with the AI page off, so no AI requests are sent.

Documentation and artifact verified only. We inspected the published package files but did not install this release, run these commands or contact any provider.

npm view ruflo@3.56.9 version

npx ruflo@3.56.9 tui --plain --no-ai | head -40

No new MCP configuration is needed. If you had enabled the opt-in Codex MCP group, expect it to be reported as unavailable, and use Codex dual-mode workers instead.

Use it today

Input: a project whose Ruflo event log may have been cut off by a crash or a full disk. Workflow: upgrade to 3.56.9 so the CLI uses the shared package with tail repair, then keep working as usual. Output: per the release notes, new events are appended after the damaged tail is repaired, instead of after a partial record.

Experimental commentary — acceptance test

One idea is to use the repaired event log as a recovery checkpoint after unplanned shutdowns. Acceptance: in a disposable project, truncate the last RVF record partway, append a new event, and confirm that the log reads back with every complete earlier record plus the new one. Limitation: the newsroom has not run this test, and the release describes tail repair, not full log reconstruction.

Limits and verification

Draft history: originally prepared for the unpublished October 13 candidate and carried in the unpublished October 19 candidate; intended for first publication with the October 27 candidate. Source event and documentation verification dates are unchanged.

• Behavior is taken from the release notes, pinned package manifests and packaged code. Nothing was run.
• No performance or benchmark claim is made, and these fixes are not a general safety guarantee.
• The terminal console itself is described in the 3.56.7 story and is not repeated here.