Changelog

This page documents the complete version history and release log of the Rotifer Protocol reference implementation (@rotifer/playground).

Version overview: Rotifer has 7 historical version series with 30+ releases. Full version list: v0.1.0 (initial), v0.2.0 (Arena), v0.3.0 (WASM compilation), v0.4.0 (cloud), v0.5.x (P2P + reputation), v0.7.x (stabilization), v0.7.9 (trust shield), v0.8.0 (Iron Shell), v0.8.6 (CLI runtime bugfix), v0.9.0 (Open Mesh + Economy Foundation), v0.10.0 (P2P reliability), v0.10.1 (release pipeline fix), v0.10.2 (async gene guard), v0.11.0 (rollback & uninstall), v0.12.0 (invocation telemetry), v0.13.0 (plugin least privilege), v0.13.1 (telemetry excludes test runs), v0.14.0 (DeepSeek Harness support), v0.14.1 (install command fix), v0.15.0 (score provenance), v0.16.0 (Arena audit tooling), v0.17.0 (Arena invalidation applied), v0.18.0 (leaderboard evaluation tiers), v0.19.1 (official Gene ownership recovery), v0.19.2 (unpublish fix and full L0 gate coverage), v0.20.0 (public Skill sources), v0.21.0 (init and L0 provenance fixes), v0.21.1 (test infrastructure fix), v0.22.0 (fuel ladder + hybrid host-function preview), v0.22.1 (Arena watch and assistant reliability fixes), v0.23.0 (anonymous usage heartbeat + invocation channel field), v0.23.1 (fix: heartbeat wasn’t actually being sent), v0.23.2 (heartbeat timeout recalibration), v0.24.0 (current public release — wrap offers to publish by default). Detailed changelog for each version below.

v0.24.0 (2026-08-31) — Current (Wrap Offers to Publish by Default)

• rotifer wrap now offers to publish: after wrapping a gene, it asks “Publish ‘<gene>’ to Rotifer Cloud? [Y/n]” (Enter means yes), across all three completion paths — plain, --from-skill, --from-clawhub. The prompt is skipped, with a note explaining why, when there’s no one to answer it: no TTY or JSON output, not signed in, a Native gene that hasn’t been compiled yet, or a Hybrid gene with no network.allowedDomains configured.

v0.23.2 (2026-08-31) — Heartbeat Timeout Recalibration

The heartbeat request gave up after 2 seconds, shorter than a real network’s typical TLS handshake alone — cutting off reports that would have succeeded. Raised to 8 seconds, based on 10 real-request measurements.

v0.23.1 (2026-08-31) — Fix: Anonymous Heartbeat Wasn’t Actually Being Sent

On a successful exit, rotifer run and rotifer agent run cut off the pending heartbeat report mid-flight — the database stayed empty for the first stretch after v0.23.0 shipped. Both commands now wait for the report to settle (or time out) before exiting. The same fix closes a related risk: an unresponsive reporting endpoint could hang the command indefinitely.

v0.23.0 (2026-08-30) — Anonymous Usage Heartbeat + Invocation Channel Field

• Anonymous usage heartbeat: signed-out runs now report a heartbeat with no identity attached (just whether this machine was active, and through which channel), on by default, disabled with ROTIFER_TELEMETRY=0; shown once on first run.
• Invocation ledger gains a channel field: signed-in invocation records now distinguish CLI from each MCP host (Cursor, Claude Code, DSH, etc.) — previously all recorded with no source at all.

v0.22.1 (2026-08-29) — Arena Watch and Assistant Reliability Fixes

• rotifer arena watch now reads the tiered leaderboard: the old path it used didn’t recognize invalidated scores, so a rank kept scrolling by after being struck.
• rotifer.dev AI assistant: fixed occasional truncated answers caused by caching an incomplete generation, and a roughly two-hour outage caused by a missing configuration setting.

v0.22.0 (2026-08-29) — Fuel Ladder and Hybrid Host-Function Preview

• Compute-heavy genes no longer fail evaluation on a fixed fuel budget: a run that dies of fuel alone automatically retries at a higher budget — wall clock and memory limits stay fixed, and the fuel actually burned still counts against the efficiency term. The public evaluation ledger records why a failed run failed (fuel-exhausted, memory-exceeded, timeout, crash), so an evaluation-resource ceiling reads differently from a gene defect, and rotifer test uses the same ladder as Arena admission. The evolve-life genes, blocked by the old constant, pass admission and are republished at 0.3.0.
• Hybrid host-function preview: Hybrid genes can declare rotifer.net / rotifer.kv / rotifer.env capability modules — a nonstandard preview, deny-by-default: nothing is linked unless the deployer grants it and the phenotype declares it, and a Native gene importing any of them is refused.

v0.21.1 (2026-08-24) — Test Infrastructure Fix

Maintenance release with no change to how you use Rotifer: repairs the project’s mutation-testing setup, which had been failing to start since v0.19.2, so that quality gate runs again on every release.

v0.21.0 (2026-08-23) — Init and L0 Provenance Fixes

• rotifer init ships the recommended template’s gene: gene-health-scanner, required by the recommended first command (rotifer hello --template quality-advisor), is now copied into new workspaces alongside the five Genesis genes; previously that command failed on every fresh workspace. The README demo block now matches the real command output.
• L0 gate judges provenance by install channel: when the gate cannot run, a Gene is treated as external only if its cloud manifest was written by install; a publish receipt (the record of your own upload) runs with a warning. Previously any manifest caused refusal, which blocked the bundled Genesis genes on machines without the prebuilt native addon. Unreadable or ambiguous manifests are still refused, and run, test and hello share one rule.
• Steward’s note translations: a developer profile’s steward note can carry translations, each pinned to the exact source text it translates; editing the note disables stale translations and the page falls back to the original. Chinese is served on the zh pages today.
• Node requirement corrected to >= 22.18: genes are TypeScript and the CLI imports them from source, which requires Node’s built-in type stripping; the previously stated >= 20 never worked for that path. Support for older Nodes is tracked in #270.

v0.20.0 (2026-08-22) — Public Skill Sources

• Skill sources published: rotifer-guide, rotifer-agent and rotifer-arena now live under skills/ with CI and publish by tag; previously their source was not publicly readable. Added rotifer-gene, the Gene development manual (express function, phenotype schema, pre-publish security audit, fidelity migration).
• README Status line tracks the released version: it had sat at v0.10.1 while the registry served 0.19.2; the check now runs in the release pipeline.
• Consistent plugin name: Cursor now uses the same rotifer name as every other host.

v0.19.2 (2026-08-21) — Unpublish Fix and Full L0 Gate Coverage

• rotifer unpublish works: every call since v0.16.0 had failed with “Published gene version is immutable” — a database guard blocked updating the one column the command exists to change. Unpublish and republish are now authorised operations that check ownership and record who acted.
• L0 gate covers every execution path: the gate previously ran only for compiled Genes with the sandbox on; uncompiled Genes, --no-sandbox, and a silently failed native addon all bypassed it.
• Unavailable gate no longer means refusal of everything: when the gate cannot run, externally installed Genes stay refused and local Genes run with a warning (judgement refined further in v0.21.0).
• Plugin listing names corrected: the bundled evolve Skill and the CodeBuddy listing no longer reuse names that belong to other components.

v0.19.1 (2026-08-20) — Official Gene Ownership Recovery

v0.19.0 carried the same changes but never reached npm (the release pipeline failed after tagging); v0.19.1 is the first installable version.

• The 59 official Genes are manageable again: the rotifer-protocol profile was backed by a banned GitLab account, leaving 32% of the registry impossible to republish, unpublish or edit. Ownership moved to an account that can sign in; the public name and /developers/rotifer-protocol are unchanged, and the old profile is renamed and retained for the record. Profiles gained a steward’s note stating who operates the identity.
• Reputation recompute covers emptied creators: a creator who no longer owns any Gene previously kept their last score indefinitely (seen as a ghost duplicate on the creators leaderboard).
• Transitional scores marked estimated: while two fitness inputs remain constants, submissions are recorded as estimates rather than measurements.

v0.18.0 (2026-08-20) — Leaderboard Evaluation Tiers

• Evaluation tiers on the leaderboard: every row is verified (measured by a sandbox or binding runtime and used by enough distinct callers), under_evaluation (measured, usage evidence still thin; ranked within its tier), or not_evaluated (nothing measured, disqualified, or estimated). not_evaluated rows carry no rank and print no score.
• R(g) filters invalidated scores: reputation had read the latest Arena row unfiltered (at 0.70 weight), so disqualified scores re-entered through reputation, developer totals and arena-win counts. The board and R(g) now share one predicate, pinned to each other by a test.

v0.17.0 (2026-08-19) — Arena Invalidation Applied

• 59 of 104 Arena rows disqualified: 30 carry artifacts the runtime refuses to execute, 27 have no published artifact, 2 are test data. Rows are retained with the criterion and timestamp recorded, not deleted; artifact scans record the SHA-256 of the bytes read, and all 33 hashes checkable against publish-time records matched.
• Legacy score provenance classified: all 104 rows written before the provenance column existed were classified by the numeric fingerprint of their write path (publish placeholder, hash estimator, sandbox run, manual entry) — 104 of 104 matched.
• Fidelity discount applied: F(g) = base_fitness × discount (native 1.00 / hybrid 0.85 / wrapped 0.70), required by spec v2.11 but never wired in; entries store base_fitness and the discount so rows stay reconstructible when the parameter changes.
• Hybrid Genes compile as Hybrid: compile validates them without forcing the WASM toolchain (Hybrids run under Node with the network gateway); the Wrapped-to-Native rewrite remains, and is now announced.

v0.16.0 (2026-08-19) — Arena Audit Tooling

• rotifer arena audit: runs the score-invalidation criteria directly; every input it reads is public and credential-free, so third parties reproduce the same verdicts. Read-only — applying an invalidation is a separately authorised step.
• rotifer unpublish command added: wiring it up also fixed a silent-success defect — under row-level security an update matching zero rows is not an error, so unpublishing a Gene you do not own reported success. The changed row is now read back, and an empty result is an error that says why.
• Double-count probe published: lists consecutive invocations of the same Gene by the same caller inside the dedup window; empty behind a working guard, and it shares the window constant with the guard.
• Bundled Genes compile again: 38 of 50 now build (previously 17). Causes: decorative async entry points and stale enum values from a phenotype split. The remaining 12 are itemised, and a regression test pins the exemption list so it can shrink but never grow.

v0.15.0 (2026-08-18) — Score Provenance

• Arena entries record how they were measured: write paths declare the measurement method, the server attests what it can verify, per-run evidence is published alongside the score, and entries gained provenance and invalidation columns.
• Idempotent invocation reporting: a retried invocation no longer counts twice (five-second window).
• Test suite isolated from real credentials: HOME is redirected to a throwaway directory for every test file; previously, running the suite while signed in deleted your own login via a logout test.
• DeepSeek Harness rows renamed: mcp-rotifer became rotifer-mcp, so both rows are found by one search.

v0.14.1 (2026-08-18) — Install Command Fix

• DeepSeek Harness installs from the repository: the previous instruction referenced an npm package that intentionally does not exist (rotifer on npm is an anti-impersonation pointer package); the README and generated configuration state the reason.

v0.14.0 (2026-08-18) — DeepSeek Harness Support

• Fifth plugin host: the plugin that already serves Cursor, CodeBuddy, OpenClaw and Claude Code now installs into DeepSeek Harness from the same source and version. It only declares configuration that mounts the harness’s own skill provider and MCP bridge — no runtime code of ours — and ships the same pinned ten-tool evolve set.

v0.13.1 (2026-08-18) — Telemetry Excludes Test Runs

• Test-runner invocations are not reported: the reporter recognises VITEST, JEST_WORKER_ID and NODE_ENV=test (including in spawned child processes) and stays silent. CI deliberately still counts — a Gene invoked from a pipeline is real usage.
• Dependency advisory patched: the bundled HTTP/2 crate moved past RUSTSEC-2026-0258.
• ClawHub display name lives in the manifest: “Rotifer” no longer depends on a publish-time flag; a test guards both the id and the display name.

v0.13.0 (2026-08-18) — Plugin Least Privilege

• Pinned MCP server with the ten-tool set: the plugin no longer launches a floating @rotifer/mcp-server with all 31 tools reachable (publish_gene, login and the sandbox escapes among them). The bundled Skill now states that installs wait for approval and documents which tools it reaches, what it sends and how to undo an upgrade. The plugin is also published to ClawHub.
• MCP registration fixed on OpenClaw: the configuration fields sat where the host never reads them; they now live in package.json#openclaw and the validator reports no warnings.
• Failed runs are recorded too: process.exit(1) no longer kills the invocation report mid-flight, so failures count alongside successes.

v0.12.0 (2026-08-17) — Invocation Telemetry

• The CLI reports gene executions: rotifer run and rotifer agent run record each execution of a Cloud-installed gene — the input to the protocol’s usage and anti-manipulation metrics. Locally authored genes are never reported, reporting happens only while signed in, and ROTIFER_TELEMETRY=0 (or false / off) disables it entirely.
• An empty result no longer passes the Arena: success now also requires the output to satisfy the gene’s declared outputSchema; contract-breaking runs are reported separately with the reason.

v0.11.0 (2026-08-17) — Rollback and Uninstall

• rotifer rollback and rotifer uninstall: return a gene to a previous version, or remove it from your workspace.
• Gene call counter fixed: a server-side type mismatch made every count attempt fail silently, so counts never moved; fixed with a regression test that checks the counter actually increments.

v0.10.2 (2026-08-14) — Async Gene Guard

• The runtime rejects an async express() up front: the WASM sandbox has no event loop, so an async gene returned an empty object while every signal reported success, and the Arena scored such runs as passes. The sandbox now rejects the artifact before execution and lists the ways out: recompile with a synchronous express(), run under Node with --no-sandbox, or publish as a Hybrid gene. The compiler has rejected this shape since the E0025 guard; if an older artifact starts reporting this error, it never produced real output — recompile it synchronously.

v0.10.1 (2026-08-11) — Release Pipeline Fix

Maintenance release with no change to how you use Rotifer: package-lock.json was not re-pointed at freshly published platform packages, which broke npm ci for anyone working from the repository. Installing or upgrading the CLI was unaffected.

v0.10.0 (2026-08-11) — P2P Reliability

• Nodes remember known peers: a restarted node re-dials peers it has met; a bootstrap address is only needed on first run.
• No silent bootstrap failure: the default bootstrap address pointed at a nonexistent host and failed without any error; nodes now ship with no default peer, and you pass one explicitly with rotifer network start -b <multiaddr>. There is no public Rotifer network yet — see the P2P LAN demo.
• Peer identification and connection limits: nodes exchange Identify and enforce inbound connection and memory limits.

P2P remains off by default (enabled: false): the CLI never joins a network unless you ask it to.

v0.9.0 (2026-06-22) — Open Mesh + Economy Foundation

A large release: the CLI now speaks P2P, and the v0.9 economic foundation lands.

• P2P gene propagation (experimental) — the CLI can now run a real libp2p node. rotifer network start / announce / received lets nodes on the same LAN discover each other and propagate gene announcements. This is the first runnable step of the P2P stack; automatic discovery and reaching nodes across the internet are later milestones.
• rotifer doctor — a toolchain health check that flags missing or misconfigured dependencies before you build.
• Hybrid Fidelity genes — genes can now declare external dependencies, degradation behaviour, and a simulation spec, describing how they behave when their environment is unavailable.
• Auto safety badge on publish — rotifer publish now uploads the gene’s V(g) safety-scan badge automatically (opt out with --skip-vg).
• Economy + season system — reputation dynamics, automated season reset, and fitness/weight display land the v0.9 economic foundation.
• Login fix — the CLI login callback now binds reliably to the allow-listed local port, fixing the timeout some users hit.

v0.8.6 (2026-04-21) — CLI Runtime Bugfix + Native Addon Distribution

Four CLI runtime bugs fixed, plus the first release shipping prebuilt native binaries across all major platforms.

• Javy async Gene fix — async express() genes no longer crash with “Pending jobs in the event queue”; the compile step now detects async usage and reports a clear error
• Compile cache fix — rotifer compile now detects source file changes and recompiles; previously a stale gene.wasm was reused silently even after editing index.ts
• irHash serde fix — genes with an irHash in phenotype.json no longer fail on the native (wasmtime) execution path; the hex-string/byte-array mismatch is resolved
• WASM sandbox fuel fix — default fuel raised from 1M to 500M, memory to 256 MiB, timeout to 60s; Javy/QuickJS genes no longer hit “fuel exhausted” on trivial workloads
• Native addon distribution — prebuilt .node binaries now ship via platform-specific packages (@rotifer/playground-darwin-arm64, -darwin-x64, -linux-x64-gnu, -win32-x64-msvc); npm install automatically picks the right binary — no local Rust toolchain required

v0.8.5 (2026-04-08) — Ecosystem Alignment

First release where CLI, MCP Server, VS Code extension, docs, and install snippets all present a single coherent version number to users.

• Unified install experience: npm install -g @rotifer/playground, npx @rotifer/mcp-server, and the VS Code extension all point to the same v0.8.5 surface — no more version mismatch between tools
• Skill→Gene migration path documented: the rotifer wrap --from-clawhub workflow and Skill migration guide are now part of the public docs
• CLI update notifications: the CLI now alerts users when a newer version is available
• IDE distribution cleanup: plugin families and marketplace metadata are consistently versioned across VS Code Marketplace and Open VSX

v0.8.0 (2026-02-17) — Iron Shell

Security hardening, P2P Protocol RFC, Epoch automation, AI documentation assistant, and 30+ deliverables.

• Supabase deep security audit: Full attack surface validation across Hybrid Gene gateway, WASM upload, Edge Functions, Reputation RPCs, Badge Worker, V(g) scanner, Gene Registry, MCP call stats
• WASM sandbox escape testing: 15+ security tests covering memory OOB, infinite loops, host function abuse, resource exhaustion, malformed IR
• P2P Protocol RFC: Complete design document — transport (QUIC/libp2p), discovery (mDNS + Kademlia DHT), GossipSub messaging, Sybil/Eclipse protection, Cloud binding collaboration
• Security Checklist mechanism: Reusable version-level security checklist template integrated into CI and release flow
• Epoch automation: pg_cron daily reputation computation + monthly decay with idempotent compute_all_reputations() RPC
• ContributionMetrics: Anti-manipulation ready contribution tracking (gene_invocation_log, gene_contribution_metrics)
• LLM-Native Gene standard: Prompt Gene + Guard Gene phenotype definitions (ADR-084)
• Evolution API Level 1.5: Gene recommendation + Arena observability REST endpoints
• AI documentation assistant: RAG-powered chat on rotifer.dev with rate limiting, content filtering, caching, and analytics
• WebMCP Phase 1: 10→14 Agent-ready marketplace tools with auth + confirm dialogs
• Infrastructure resilience: GitLab→GitHub CI migration, Forgejo migration preparation, Cloudflare Pages deployment pipeline

v0.7.10 (2026-03-24)

Security hardening, WebMCP expansion, and China market readiness.

• Schema Compatibility Check: Static type checking for Seq pipeline — validates output→input schema alignment with PASS / UNCHECKED / FAIL diagnostics
• Try Fallback Error Propagation: Try operator now passes structured {error, original_input} to fallback genes instead of bare input
• WebMCP Phase 1: 10→14 tools — 4 new write-enabled (L3) tools: set_gene_visibility, request_arena_evaluation, create_gene, update_gene_metadata with auth + confirm dialog
• Path Traversal Guard: rotifer init now rejects project names containing ../ sequences
• China Network Guide: Chinese getting-started docs with cnpm mirror install and Supabase latency notes
• CI Pipeline Hardening: Fixed deploy configs, Node 20 compatibility, resilient network-dependent tests

v0.7.9 (2026-03-20)

Major milestone in protocol maturity and trust infrastructure.

• Safety Badge Pipeline: Automated verification gate (V(g)) with visual safety badges for genes
• Cloud Arena: Global fitness rankings with real-time competition
• Agent Blueprint: Export/import full agent configurations (genome + arena state)
• MCP Server: @rotifer/mcp-server enables IDE integration (Cursor, VS Code, Windsurf, etc.)
• Network Commands: rotifer network announce, network discover, network pull for P2P gene sharing
• Reputation System: Phase-weighted trust ranking R(g) complementing fitness F(g) (time decay planned for v0.9)

v0.7.x (2026-03-19 → 2026-03-20)

Rapid iteration series focused on stability and developer experience.

• v0.7.0 → v0.7.9: Progressive improvements to CLI reliability, error messages, and documentation
• Cloud binding stabilization and endpoint configuration
• Arena ranking algorithm refinements

v0.5.x (2026-02-23 → 2026-02-24)

• Reputation Foundation: Introduction of R(g) reputation scoring
• P2P Foundation: GossipSub metadata announcement, Kademlia DHT discovery
• Horizontal Logic Transfer (HLT): Cross-agent gene sharing infrastructure
• Composition Operators: Seq, Par, Cond, Try, Transform for multi-gene pipelines

v0.4.0 (2026-02-23)

• Cloud Binding: Supabase-backed cloud registry for gene publishing and discovery
• rotifer login / rotifer publish / rotifer search / rotifer install
• Cloud Arena: rotifer arena submit --cloud for global competition
• GitHub OAuth authentication

v0.3.0 (2026-02-22)

• Auto TS→WASM Compilation: rotifer compile automatically compiles TypeScript genes to Native WASM via the built-in IR compiler — no separate Rust/WASM toolchain required
• Rotifer IR: Custom WASM sections (rotifer.version, rotifer.phenotype, rotifer.constraints, rotifer.metering)
• WASM sandbox with fuel metering and epoch interruption

v0.2.0 (2026-02-22)

• Local Arena: Fitness-based gene ranking system F(g)
• rotifer arena submit / rotifer arena list
• L0 Constitutional Constraints: Safety gate enforcement
• Gene admission testing pipeline

v0.1.0 (2026-02-20)

The inaugural release — core gene lifecycle.

• rotifer init — Agent workspace scaffolding with Genesis genes
• rotifer scan — function compatibility detection
• rotifer wrap — function-to-gene conversion with phenotype.json generation
• rotifer test — sandbox testing with schema validation
• rotifer compile — Rotifer IR compilation (manual WASM input)
• Five Genesis genes included: genesis-web-search, genesis-web-search-lite, genesis-file-read, genesis-code-format, genesis-l0-constraint

Versioning Policy

The Rotifer Protocol follows Semantic Versioning:

• Major (1.x): Breaking protocol changes
• Minor (0.x): New features, backward-compatible
• Patch (0.0.x): Bug fixes and improvements

Current status: Pre-1.0 — the protocol is under active development. APIs may change between minor versions.

Roadmap

Upcoming milestones (subject to change):

Version	Focus	Status
v0.22.0	Evaluation stops failing genes on its own fuel constant; Hybrid host-function preview	Current
v0.21.x	Fresh workspaces run their recommended first command; L0 gate judges provenance by install channel	Released
v0.20.0	The published Skills get a public source, and a fourth joins them	Released
v0.19.2	Taking a version down actually takes it down; the L0 gate reaches every execution path	Released
v0.19.1	The official Genes get an owner who can sign in; ghost reputation scores cleared	Released
v0.18.0	The verdicts reach the page: tiered leaderboard, and R(g) stops counting withheld scores	Released
v0.17.0	The criteria applied: 59 rows stop ranking, legacy rows get provenance, and F(g) carries the fidelity discount	Released
v0.16.0	Arena integrity — the invalidation criteria as runnable code, and a compilable bundled corpus	Released
v0.15.0	Score provenance — an Arena entry records how it was measured	Released
v0.10.1	Release-pipeline fix (package-lock sync)	Released
v0.10.0	P2P reliability — peers remembered across restarts, silent bootstrap failure removed	Released
v0.9.0	Open Mesh + economy foundation	Released
v0.8.6	CLI runtime bugfixes (Javy async, compile cache, irHash, fuel) + prebuilt native binaries on all platforms	Released
v0.8.5	Unified version surface across CLI, MCP Server, VS Code extension, and docs; Skill→Gene migration path	Released
v0.9.1	P2P discovery layer (mDNS, DHT, internet)	Planned
v1.0	Stable release — L0–L3 complete, ≥2 Bindings, ≥100 Genes, security audit	Planned