admin/ruflo

0 Fork 0

mirror of https://github.com/ruvnet/ruflo.git synced 2026-10-23 03:47:00 +09:00

Files

T

RuFlo 06756fbf70 review(plugins): group C — fix claims that do not match the real CLI/MCP/tools, harden unsafe flows

Verified every CLI flag, MCP tool parameter and neural-trader flag these plugins
tell the model to use against @claude-flow/cli 3.56.5 (--help and MCP schemas) and
neural-trader 2.8.11 (run offline), and fixed what was false:

- intelligence: neural_train needs modelType (no patternType/--pattern-type; CLI
  flag is --pattern), hooks_model-outcome/trajectory-end/pretrain/build-agents/
  explain parameters, mcp tool call -> mcp exec, microlora has no consolidate;
  intelligence-transfer rewritten (hooks_transfer only copies from a local
  project; marketplace is hooks transfer store ..., PINATA_API_KEY/SECRET, PII
  scan + confirmation before publish).
- loop-workers: CronCreate takes {cron,prompt,recurring} and is session-scoped
  (7-day expiry), ScheduleWakeup needs prompt, 270s heartbeat qualified by TTL.
- market-data: candles were routed to the ~11-pattern ruvllm_hnsw router;
  untrusted-feed rules; no order placement.
- neural-trader: many documented flags answer "Unknown command" in 2.8.11; several
  handlers return demo output; backtests/signals use synthetic bars without
  --live; backtest signing now refuses non-live data; live/broker path and
  circuit-breaker claims corrected; signal TTL used a non-existent expiresAt.
- iot-cognitum: pin the fleet CLI instead of @latest; confirmation gates for
  firmware deploy/advance/rollback and fleet delete.
- migrations: confirmation/dry-run/validate gates before migrate up/down.
- music: bearer token only sent to music.cognitum.one; pin cogmusic@0.1.1; token
  never enters the transcript.
- jujutsu: analyze_diff* take a ref, not diff text; gate PR merge/close/create.
- knowledge-graph: align relation weights with kg-extract.
- Removed the invalid post-task --train-neural flag everywhere in these plugins.

Plugin versions bumped (marketplace users only receive changes after a bump):
intelligence 0.4.3, loop-workers 0.3.4, market-data 0.3.4, neural-trader 0.3.5,
iot-cognitum 0.3.3, jujutsu 0.3.4, knowledge-graph 0.3.4, migrations 0.3.4,
music 0.2.4. metaharness reviewed, no change needed.

Co-Authored-By: RuFlo <ruv@ruv.net>

2026-10-11 11:33:03 -04:00

5.8 KiB

Raw Permalink Blame History

ruflo-loop-workers

Cache-aware /loop workers and CronCreate background automation. Substrate plugin for every recurring task in the ruflo family.

Install

/plugin marketplace add ruvnet/ruflo
/plugin install ruflo-loop-workers@ruflo

What's Included

Loop Workers: Recurring tasks via /loop with ScheduleWakeup (delay <270s for prompt cache hits)
CronCreate: Session-scoped cron jobs for audit, optimization, and monitoring (they end with the session and expire after 7 days; use /schedule or an OS scheduler to outlive it)
12 Background Workers: ultralearn, optimize, consolidate, predict, audit, map, preload, deepdive, document, refactor, benchmark, testgaps
Daemon Management: Start, stop, status, trigger, and enable workers
ADR-091 Integration: Native Claude Code capabilities preferred over daemon polling

Requires

ruflo-core plugin (provides MCP server)

Compatibility

CLI: pinned to @claude-flow/cli v3.6 major+minor.
Verification: bash plugins/ruflo-loop-workers/scripts/smoke.sh is the contract.

MCP surface (5 tools)

All defined at v3/@claude-flow/cli/src/mcp-tools/hooks-tools.ts:

Tool	Purpose
`hooks_worker-list`	List available workers and their triggers
`hooks_worker-dispatch`	Dispatch a worker run with `--trigger <worker-name>` and optional `--scope`
`hooks_worker-status`	Inspect a running worker
`hooks_worker-detect`	Detect which workers should fire based on context
`hooks_worker-cancel`	Cancel a running worker

12 worker triggers → consumer plugins

Trigger	Consumer plugin	Purpose
`ultralearn`	`ruflo-intelligence`	Bootstrap learning corpus from a deep codebase scan
`optimize`	`ruflo-cost-tracker`, `ruflo-intelligence`	Performance + cost optimization recommendations
`consolidate`	`ruflo-intelligence`, `ruflo-agentdb`	EWC++ memory consolidation
`predict`	`ruflo-intelligence`	Predictive routing for upcoming tasks
`audit`	`ruflo-security-audit`, `ruflo-aidefence`	Security + compliance audit pass
`map`	`ruflo-knowledge-graph`	Build/refresh entity-relation knowledge graph
`preload`	`ruflo-core`, `ruflo-rag-memory`	Warm caches before high-frequency operations
`deepdive`	`ruflo-goals` (deep-research)	Multi-source investigation pass
`document`	`ruflo-docs`	Generate API docs + drift detection
`refactor`	`ruflo-jujutsu`	Diff-aware refactor recommendations
`benchmark`	`ruflo-cost-tracker`, `ruflo-iot-cognitum`	Perf benchmarks
`testgaps`	`ruflo-testgen`	Coverage gap detection + test generation

Invocation pattern (CLI + MCP):

# CLI
npx @claude-flow/cli@latest hooks worker dispatch --trigger document --context src/api

# MCP (trigger is required; context, priority and background are optional; there is no scope field)
npx @claude-flow/cli@latest mcp exec -t hooks_worker-dispatch -p '{"trigger": "document", "context": "src/api"}'

Cache-aware /loop integration

This plugin pairs with ruflo-autopilot ADR-0001 which owns the 270s cache-aware ScheduleWakeup heartbeat contract. Recommended fallback heartbeat is 270 seconds — under the 5-minute prompt-cache TTL so the next wake-up reads conversation context cached. Going past 300s pays a cache-miss; rounding to 5 minutes is the worst-of-both case. This only applies to sessions on the 5-minute TTL: where ScheduleWakeup documents a 1-hour TTL, idle polling at 1200–1800s is cheaper and 270s wakes buy nothing.

For event-driven loops, arm a Monitor and let the 270s wake be the safety net.

Namespace coordination

This plugin owns the worker-history AgentDB namespace (kebab-case, follows the convention from ruflo-agentdb ADR-0001 §"Namespace convention"). Reserved namespaces (pattern, claude-memories, default) MUST NOT be shadowed.

worker-history records dispatch events, durations, success/failure verdicts. Accessed via memory_* tools (namespace-routed).

Verification

bash plugins/ruflo-loop-workers/scripts/smoke.sh
# Expected: "12 passed, 0 failed"

Architecture Decisions

ADR-0001 — ruflo-loop-workers plugin contract (12-worker trigger map, autopilot 270s cross-reference, smoke as contract)

ruflo-autopilot — owns the 270s cache-aware /loop heartbeat contract
ruflo-docs, ruflo-security-audit, ruflo-testgen, ruflo-knowledge-graph, etc. — worker-trigger consumers per the table above
ruflo-agentdb — namespace convention owner; backing store for worker-history

As a mod

This plugin ships a function-hook mod (ADR-445, hooks/register.ts). It makes no network call, spawns no process and makes no model call.

Guard (tighten-only, on by default): Refuses hooks_worker-dispatch whose context holds a key, token or password (workers log their context), and any dispatch past the per-session cap, which catches a stuck loop that keeps dispatching. A refusal never echoes the secret.
/loop-mod: status, recent, tools (which of this plugin's tools are connected) and scan <text> (would the guard refuse it). Answered locally.
Status file: .claude-flow/loop-mod/status.json ({version: 1, updatedMs, guard, calls, total, blocked, recent}, counters only, never tool input), written at session start and after every call to this plugin's tools.

Options (userConfig): guard (on), maxDispatch (100, range 1 to 1000).

Test it: claude plugin validate plugins/ruflo-loop-workers, claude plugin test plugins/ruflo-loop-workers, bash plugins/ruflo-loop-workers/scripts/smoke.sh.

5.8 KiB Raw Permalink Blame History Unescape Escape