mirror of
https://github.com/ruvnet/RuView
synced 2026-08-01 19:01:42 +00:00
ruv
739d3219e6
- .claude/commands/route.md and flywheel.md -- the two CLI subcommands added alongside darwin/router/flywheel wiring never got matching guidance files (unlike doctor/review-diff), so they weren't fully wired into the harness's own MCP tool listing. Added, following the existing pattern. - CLAUDE.md: note the crate + harness are both published now (crates.io v0.3.1, npm v0.1.0). - New ADR-286 documenting the harness's MetaHarness scaffold + the darwin/router/flywheel wiring decision, following the ADR-182/ADR-285 precedent (every harness in this repo gets one). - docs/adr/README.md: index rows for ADR-286 and the crate's ADR (287 -- see the next commit for the renumbering-from-283 story).
wifi-densepose-sar-harness
Harness for wifi-densepose-sar
Advanced Coding — Architect → implement → review → test, with a code-index MCP and push-guarded git perms.
Generated with
create-agent-harness. Multi-host scaffolding with a kernel that resolves native → wasm → js (js backend in the published beta; seeharness doctor).
Install
npm install -g wifi-densepose-sar-harness
wifi-densepose-sar-harness init
wifi-densepose-sar-harness doctor
Agents
| Agent | Role |
|---|---|
architect |
Designs the change before code is written. |
implementer |
Writes code that matches the surrounding style. |
reviewer |
Hunts correctness bugs in the diff. |
test-writer |
Adds the missing tests for the change. |
This harness ships with the claude-code adapter.
Darwin, router, flywheel
npm run evolve/evolve:dry— Darwin Mode self-mutation of the harness's own config (@metaharness/darwin).npm run route -- <e0> <e1> <e2> <e3>(afternpm run build) — cost-optimal model routing via@metaharness/router.npm run flywheel:dry— the SYNTHETIC@metaharness/flywheelself-improvement demo (propose → evaluate → gate → promote, signed + independently replayable).
See CLAUDE.md's "Darwin, router, flywheel" section and the comments at the top of src/router.ts / src/flywheel.ts for what's real wiring vs. illustrative/synthetic data.
Known gaps
.harness/manifest.json/manifest.sha256reflect the initialmetaharness analyze --scaffoldoutput and were not regenerated after addingsrc/router.ts,src/flywheel.ts, and their tests — this scaffold has nomanifest:updatescript (unlikeharness/homecore/). Treat the manifest as historical provenance for the scaffold step, not a current file-integrity check.
License
MIT