Ruflo v3.32.31: Governed Flywheel Candidates and Explicit Autopilot Scope

Ruflo's self-improvement loop should explore useful candidates without relaxing its promotion guardrails, and Autopilot should never search a broader task surface than the operator requested. v3.32.31 fixes both contracts.

The Flywheel safety envelope now describes the complete retrieval policy that the built-in proposer actually emits. Valid candidates can reach evaluation again, while every tunable value remains bounded and promotion remains subject to signed receipts, policy authorization, and the atomic transaction gate.

Autopilot now treats explicitly configured task sources strictly. Misspelled, empty, or unsupported sources fail with a useful error instead of silently falling back to every default source. Recovery from absent or damaged legacy state remains backward compatible.

What this enables

Run the local Flywheel proposer without every full retrieval-policy snapshot being rejected as outside its own safety envelope.
Tune alpha, subjectWeight, mmrLambda, bodyWeight, and typePenaltyFactor inside explicit finite bounds.
Keep Darwin and local proposers subordinate to Ruflo's evaluation, receipt-verification, and promotion transaction.
Configure Autopilot task discovery with an exact, auditable source set.
Detect configuration mistakes before Autopilot state is persisted or task discovery begins.

Install or upgrade

bash

npm install --global [email protected]
ruflo doctor

Or run without a global installation:

bash

npx [email protected] --version

Configure Autopilot task sources

The supported sources are team-tasks, swarm-tasks, and file-checklist.

bash

ruflo autopilot config \
  --task-sources swarm-tasks,file-checklist

Unsupported input now exits unsuccessfully and leaves the stored configuration unchanged:

bash

ruflo autopilot config --task-sources issues

Evaluate Flywheel candidates

Inspect the current transaction and ledger state:

bash

ruflo metaharness flywheel status

Run one governed evaluation using the built-in proposer:

bash

ruflo metaharness flywheel run --proposer local

Evaluation still does not grant promotion authority. Promotion requires an accepted receipt, trusted signing key, current baseline, matching ledger head, policy authorization, and explicit confirmation.

Compatibility and migration

Existing valid Autopilot state continues to load unchanged.
Missing or corrupt persisted task-source state still recovers to the legacy defaults; only new explicit configuration is validated strictly.
The retrieval safety-envelope reference advances to v2. Old v1 receipts should be re-evaluated under the new envelope rather than promoted as if the governing bounds had not changed.
The release remains the standard three-package train: @claude-flow/cli, claude-flow, and ruflo.

Validation contract

Release acceptance requires:

full PR CI for both fixes;
combined Flywheel and Autopilot focused tests;
version-lockstep validation across all three public packages;
immutable tarball construction and bundled-runtime inspection;
fresh-install smoke tests for CLI, policy, daemon, Codex initialization, and wrapper commands;
registry integrity verification;
aligned latest, alpha, and v3alpha npm tags.