Skip to content

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 (wrap offers to publish by default), v0.25.0 (fitness formula correction), v0.25.1 (cloud commands work out of the box), v0.26.0 (Gene TestSuite and T1 publish gate), v0.26.1 (least-privilege CI credentials and Rust dependency advisories), v0.26.2 (agent run asks before running installed genes unsandboxed), v0.26.3 (sandbox engine and P2P security fixes), v0.27.0 (content-derived gene IDs and frozen P2P wire format), v0.28.0 (genome export and import), v0.29.0 (Genome Blueprint format 1 and stricter imports), v0.30.0 (season-relative Arena scoring and declared gene permissions), v0.30.1 (MCP server 0.19.4 in the plugin and Skills), v0.30.2 (telemetry off stops every report; seasons roll over again), v0.30.3 (the first-run command works again; honest vg grades; MCP server 0.19.5 in the plugin), v0.31.0 (live web search with your own key; Arena scores by the tier that ran), v0.32.1 (F(g) on a 0–1 scale; stricter Hybrid network access), v0.33.0 (agent memory on your machine; run checks the schema), v0.33.1 (clearer errors when Rotifer Cloud can’t be reached), v0.34.0 (P2P gene search and withdrawal; LAN discovery), v0.35.0 (templates tell you what’s missing; steadier P2P connections), v0.36.0 (node certificates from the CLI; safer login), v0.36.1 (starter genes declared as Wrapped; clearer compile errors), v0.37.0 (global fetch held to the network declaration; T1 awaits async genes), v0.38.0 (current public release — external genes kept off unsandboxed Node.js; credentials need your OK). Detailed changelog for each version below.

v0.38.0 (2026-11-17) — Current (External Genes Kept Off Unsandboxed Node.js; Credentials Need Your OK)

Section titled “v0.38.0 (2026-11-17) — Current (External Genes Kept Off Unsandboxed Node.js; Credentials Need Your OK)”
  • Breaking — external genes need a compiled artifact or --trust-unsigned: a gene installed from Cloud or wrapped from ClawHub no longer runs from its source on Node.js in rotifer hello, test or publish, as run and agent run already required; compile it first (rotifer compile <gene>) or pass --trust-unsigned to hello or publish.
  • What each command does with such a gene: hello runs it in the sandbox when it is compiled and refuses it otherwise, test fails its T1 suite with a compile hint, and publish blocks it at the T1 gate (details); genes you wrote in this workspace are unchanged.
  • hello prints an external gene’s output as JSON: without --trust-unsigned, hello no longer loads an external last gene to call its display(), because loading it would run its code unsandboxed.
  • External genes ask before using your credentials in the sandbox: when a compiled external gene declares a credential from your environment, run, agent run, test and hello ask once at a terminal (default no) or otherwise exit 1 with credentials_not_granted, and --allow-credentials KEY@host grants it for that one command, sent only to that host; arena submit takes the same flag, but it scores Hybrid genes (the only kind that can declare a credential) without running them, so it has nothing to ask yet; a gene you let run on Node.js with --trust-unsigned is not asked about and can read every environment variable you have.

v0.37.0 (2026-11-16) — Global fetch Held to the Network Declaration; T1 Awaits Async Genes

Section titled “v0.37.0 (2026-11-16) — Global fetch Held to the Network Declaration; T1 Awaits Async Genes”
  • Global fetch held to the gene’s network declaration: under Node.js (rotifer test, run, agent run, hello and the T1 check in publish), a gene’s global fetch now gets the same checks, timeout and rate limit as ctx.gatewayFetch, and a gene with no network block is refused (details).
  • WebSocket and EventSource refused: a gene that opens one gets an error, though the Node.js path is still not a sandbox and node:http or a child process is not covered.
  • Breaking — T1 awaits an async express: T1 (rotifer test and the gate in rotifer publish) now judges the value an async express resolves to instead of the Promise, so a suite’s result can change either way; no built-in gene with a testsuite.json changes.
  • Gene calls that never finish fail: a gene whose Promise never settles now makes rotifer test, rotifer run and rotifer agent run exit with code 1, where they used to stop partway with code 0.
  • rotifer test --json prints JSON: it now prints the T1 results as JSON, where it used to print none.
  • Also in this release: ClawHub bundle and example fixes for the root plugin, a stricter certificate check in node attestation, and a build fix for newer Rust compilers.

v0.36.1 (2026-11-10) — Starter Genes Declared as Wrapped; Clearer Compile Errors

Section titled “v0.36.1 (2026-11-10) — Starter Genes Declared as Wrapped; Clearer Compile Errors”
  • gene-health-scanner and security-scanner are declared Wrapped: these starter genes read your local disk with Node built-in modules, so they could never compile to WASM, but they were declared Native. They are now Wrapped (version 0.2.1), so the agent that rotifer hello --template quality-advisor creates can be exported with rotifer genome export. Arena already scored them as Wrapped, so their scores do not change.
  • rotifer compile names the real problem: a gene whose source imports Node built-in modules now stops with E0026, which names the modules and says the gene cannot be compiled to Native and stays as declared. Before, it showed a bundler error and advice to install a toolchain that was already installed. phenotype.json is not touched.

v0.36.0 (2026-11-10) — Node Certificates from the CLI; Safer Login

Section titled “v0.36.0 (2026-11-10) — Node Certificates from the CLI; Safer Login”
  • rotifer network attest gets your P2P node a certificate: enable | status | renew | disable ask Rotifer Cloud for a proof-of-registration certificate for your node, and a running daemon renews it when under 48 hours remain. It is off by default: when run interactively, enable asks first; otherwise it needs --accept-public-pseudonym. The issuing service is not open yet, so enable currently says so and turns nothing on. See Network Commands.
  • rotifer login accepts only a PKCE code on its local callback port: another page open in your browser can no longer finish the login as someone else. The command also checks the format of the Cloud endpoint before opening the browser.
  • rotifer login finishes sooner: it usually exits within seconds of the login finishing, instead of always waiting two minutes.
  • Styled login pages: the browser shows styled pages for completed, canceled and failed logins.
  • The browser opens without a shell on Windows: and only a plain http(s) address is opened, on every platform.
  • Wrapped genes pass the WASM sandbox: genes made with rotifer wrap now run in rotifer test, rotifer arena submit and rotifer run. On 0.35 every wrapped gene failed there, so the wrap → compile → arena submit walk-through was refused.
  • rotifer wrap --from-clawhub treats the package as someone else’s upload: a package with a symbolic link, a .. segment or an absolute path is refused with E0013, and files the CLI writes itself (such as phenotype.json) are no longer taken from the package. A gene wrapped from ClawHub, including one wrapped before this version, is refused on the unsandboxed Node.js path unless you pass --trust-unsigned, as Cloud-installed genes already were.
  • Bundled SQLite updated: the native addon now bundles SQLite 3.54.1, which fixes security advisory RUSTSEC-2026-0459.
  • There is still no public bootstrap node or relay, and the P2P node stays off unless you start it.

v0.35.0 (2026-11-09) — Templates Tell You What’s Missing; Steadier P2P Connections

Section titled “v0.35.0 (2026-11-09) — Templates Tell You What’s Missing; Steadier P2P Connections”
  • rotifer hello says what to do about missing genes: for a template that can’t run, rotifer hello --template <id> goes gene by gene and prints the rotifer install @rotifer-protocol/<gene> command to copy, or says why the gene can’t be installed. It asks Rotifer Cloud read-only, for at most 5 seconds, and if Cloud can’t be reached it says so. hello never installs anything itself.
  • A run that did nothing no longer reports success: a template that has nothing to run now exits 1. If a gene refuses its input, hello reports the refusal instead of printing success, and --dir on a directory with none of the template’s files says which files to provide.
  • rotifer hello --list-templates shows what can run here: templates ready in this workspace are listed apart from those that need genes first. It makes no network call.
  • Which templates run: quality-advisor comes with rotifer init. uiux-diagnosis, content-analysis and web3-toolkit run once their genes are installed from Rotifer Cloud. code-security and doc-qa are not available yet.
  • rotifer hello --json: stdout now carries one JSON document, the output or {ok:false,code,…} on any failure, and everything else goes to stderr.
  • WASM-only genes run under hello: a gene installed from the Registry with only WASM code no longer counts as missing.
  • P2P keeps its own connections: the node tries to keep 8 outbound connections to peers it chose itself, so it relies less on whoever connects to it.
  • P2P reconnects more carefully: when no bootstrap node is connected it redials one right away, backing off after failures. A restart dials back only peers it had actually reached, not every address it heard about.
  • Many peers on one IP address keep their penalty: when more than 10 peers share an IP address, they keep their score penalty after one of their connections closes. The penalty lowers their score but does not by itself get them disconnected.
  • There is no public bootstrap node or relay yet, and the P2P node stays off unless you start it.

v0.34.0 (2026-11-04) — P2P Gene Search and Withdrawal; LAN Discovery

Section titled “v0.34.0 (2026-11-04) — P2P Gene Search and Withdrawal; LAN Discovery”
  • Breaking — the DHT changed: nodes on 0.27–0.33 still connect and gossip with this version, but no longer share its DHT. Upgrade your bootstrap node, or keep a remembered upgraded peer.
  • rotifer network search <query>: keywords match announcements this node has heard from other nodes, and a Rotifer Cloud search runs alongside; the two are shown as separate lists. A v2 gene ID (v2:<64 hex>) is looked up in the DHT. The DHT is never searched by keyword.
  • announce writes the DHT: rotifer network announce now also stores the gene’s record in the DHT and republishes it every 12 hours, and the list of announced genes survives a daemon restart. Publishing to the DHT makes this node’s network addresses visible to anyone who looks up that gene ID.
  • rotifer network withdraw <gene>: stops republishing a gene, and this node stops serving it. Other nodes are not told to delete it: copies they stored expire on their own, and a node that heard the announcement on gossip can still list it for up to 48 hours.
  • LAN discovery: nodes started with --host 0.0.0.0 find each other on the local network by mDNS, without --bootstrap; rotifer network start --no-mdns turns it off (use it on untrusted Wi-Fi).
  • Relay and hole punching: the node is on libp2p 0.57, can connect through a relay or by hole punching, and enforces connection and memory limits. There is no public bootstrap node or relay yet.
  • Records from other nodes are checked before they are stored, with per-publisher and total limits; a peer that keeps breaking them is blocked for a while. Peers join this node’s DHT only when they show they speak Rotifer’s DHT.
  • Proof of registration in heartbeats: node heartbeats can carry a proof of registration issued by Rotifer Cloud, which peers check and use when scoring each other. The Cloud side that issues it is in the repository but not deployed.
  • Fixes: gossip on topics without a registered validator is ignored, and the node refuses to publish on topics it has not registered.
  • The P2P node stays off unless you start it.

v0.33.1 (2026-11-01) — Clearer Errors When Rotifer Cloud Can’t Be Reached

Section titled “v0.33.1 (2026-11-01) — Clearer Errors When Rotifer Cloud Can’t Be Reached”
  • The real cause, not fetch failed: when Rotifer Cloud can’t be reached, registry commands such as search, versions and reputation name the cause, for example connection refused (ECONNREFUSED).
  • Gene-name hint only for missing genes: info, stats, compare, install, reputation and versions suggest checking the gene name only when the registry says the gene does not exist; a network failure gets a reachability hint instead.
  • Linux installs: the package no longer lists rolldown’s Linux native binding as one of its own optional dependencies.

v0.33.0 (2026-11-01) — Agent Memory on Your Machine; run Checks the Schema

Section titled “v0.33.0 (2026-11-01) — Agent Memory on Your Machine; run Checks the Schema”
  • Agent memory (spec §38): an agent now has a memory its genes read and write between runs; it belongs to the agent, so replacing or updating a gene keeps it. Entries are PREFERENCE, PATTERN, CONTEXT or CACHE, stored in your project’s .rotifer/playground.db; the Memory API page has the details.
  • Cloud memory is not live yet: memory stays on your machine for now; Rotifer Cloud does not store it in this release.
  • Memory quota: rotifer agent create --memory-quota <size> sets an agent’s quota (default 10 MB). When it is full, the oldest CACHE, then PATTERN, then CONTEXT entries are cleared; PREFERENCE entries never are, and a write that still does not fit fails with MEMORY_QUOTA_EXCEEDED.
  • Access scopes: each entry says which genes may read and change it. The default is genes in the creator’s domain (SAME_DOMAIN); a call that is not allowed fails with MEMORY_ACCESS_DENIED and is recorded in .rotifer/audit.jsonl.
  • Retention: an entry’s maxRetentionDays is enforced; autoDeleteOnTermination is stored but has no effect yet.
  • rotifer agent memory list / delete: list an agent’s entries without their values, and delete one key or a whole category.
  • Which genes get memory: TypeScript genes that run on Node.js get it as ctx.memory; genes with their own WASM call the rotifer memory host functions. TypeScript compiled to WASM cannot use memory yet.
  • rotifer test gives a gene a throwaway memory for the length of the test, so your agents’ memory is not touched.
  • rotifer compile prints Gene ID (v2), the id memory records as an entry’s creator, and labels the content hash as not an identity.
  • rotifer run checks the schema: the input is checked against inputSchema before the gene runs and the output against outputSchema after. Input that does not match used to run and now exits 1; --no-validate turns both checks off.
  • Fixes: wrapped genes compile again; test --compliance no longer crashes on a gene’s irHash; a Par, Cond or Try agent that cannot run as written stops and says why instead of quietly running as Seq; a gene stopped by its time limit is reported as a timeout; hello gives a Hybrid gene its network gateway; the code-security template no longer reports a failed read as a finished scan; a malformed rotifer.json gives a one-line error instead of a crash; rotifer run works on Windows.
  • wrap --from-clawhub reports ClawHub’s real error (status and reason) and retries server errors and timeouts up to three times.
  • τ is paused in the CLI too: arena submit no longer shows τ = 0.3 as a gate; V(g) still gates.
  • Security: wasmtime 48.0.8 for the 2026-10-29 RustSec advisories.

v0.32.1 (2026-10-28) — F(g) on a 0–1 Scale; Stricter Hybrid Network Access

Section titled “v0.32.1 (2026-10-28) — F(g) on a 0–1 Scale; Stricter Hybrid Network Access”

v0.32.0 was tagged but not published to npm; 0.32.1 is the first release with these changes.

  • F(g) on a 0–1 scale (ADR-346): the score is five factors, each between 0 and 1, multiplied together, so a perfect gene scores exactly 1.
  • Old scores are not converted: a score computed by 0.31 or earlier is 2·ln 2 ≈ 1.386 times the new scale, including the ones cached on your machine. Re-run rotifer arena submit to rescore a gene.
  • The registry records the formula version: each score uploaded with arena submit --cloud is labelled with the formula that produced it; a score from an older CLI is left unlabelled.
  • Cloud Arena accepts the tier that ran: a gene declared Native that ran outside the sandbox is uploaded at the Wrapped discount instead of being refused.
  • Stricter Hybrid network access: gatewayFetch allows https only, refuses IP addresses, and checks every redirect hop against allowedDomains (at most 5). A gene that still calls an http:// endpoint now fails with INVALID_REQUEST.
  • A network failure says what it was: when a Hybrid gene’s request fails with code -5, the error ends with the cause and the host, e.g. (last network failure: TLS error (api.example.com)). Nothing from the request (path, query, headers, keys, body) is included.
  • T1 retries a network failure once: during the publish gate’s property test, an iteration of a Hybrid gene that fails only on the network (-4, -5 or -7) runs once more before it counts as a failure.
  • Keys stay with their host: a key the host fills in from declared credentials is not sent on when a response redirects to another host; on a redirect to another origin the gateway drops the request headers.

v0.31.0 (2026-10-27) — Live Web Search with Your Own Key; Arena Scores by the Tier That Ran

Section titled “v0.31.0 (2026-10-27) — Live Web Search with Your Own Key; Arena Scores by the Tier That Ran”
  • Live web search: rotifer install tavily-web-search gets a gene that searches the web through the Tavily API with your own key in TAVILY_API_KEY (Tavily’s free tier is 1,000 searches a month with no card). Same input and output as genesis-web-search.
  • API keys for Hybrid genes (nonstandard preview, ADR-327): a Hybrid gene names the environment variables it needs in externalDependencies[].credentials. The CLI reads only those, only for a gene that gets network access, and stops before running if one is missing. The gene writes ${env:NAME} into a request header and the host fills in the value as the request leaves the sandbox, so the gene never sees the key and it does not appear in output or logs.
  • Arena scores by the tier that ran: a gene declared Native that did not run in the sandbox is now discounted as Wrapped, and the output says so. Earlier entries are not rescored.
  • Same source, same bytes: compiling a gene twice gives an identical module, so its v2: ID no longer changes between compiles.
  • vg names what it could not scan: files in a language it has no rules for (Rust, for now) are listed as not scanned instead of the gene being called pure config.
  • Fixes: rotifer test and the publish gate read a gene’s input refusal from the sandbox as a refusal, not a crash; the wasmtime compile cache, unused, is dropped and with it a dependency with four security advisories.

v0.30.3 (2026-10-26) — First-Run Fix, Honest vg Grades, MCP Server 0.19.5

Section titled “v0.30.3 (2026-10-26) — First-Run Fix, Honest vg Grades, MCP Server 0.19.5”
  • The recommended first command works again: rotifer hello --template quality-advisor failed on 0.30.2 and earlier with “Missing primary genes: gene-health-scanner” because the package left that gene out. It ships now, and CI installs the packed package and runs this command before every release.
  • vg grades what it reads: it scans a gene’s root index.ts (bundled TypeScript genes no longer show grade ?), reports “not graded” instead of grade A when it finds no files, and flags Python subprocess and open(). The hint after rotifer wrap now passes a path, which is what vg takes.
  • Bundled search genes say they are demos: genesis-web-search and genesis-web-search-lite return simulated example.com results; their descriptions and every result title now say so.
  • Plugin and Skills pin @rotifer/mcp-server 0.19.5: rotifer telemetry off now also stops the MCP server’s reports.

v0.30.2 (2026-10-26) — telemetry off Stops Every Report; Seasons Roll Over Again

Section titled “v0.30.2 (2026-10-26) — telemetry off Stops Every Report; Seasons Roll Over Again”
  • rotifer telemetry off now stops the signed-in invocation report too: before, the stored choice stopped only the anonymous heartbeat, while DO_NOT_TRACK / ROTIFER_TELEMETRY=0 stopped both. The environment variable still wins in either direction; otherwise the choice in ~/.rotifer/telemetry.json applies. MCP server 0.19.5, released the same day, reads the same file; the plugin and Skills still pin 0.19.4 until the next CLI release.
  • Server side (Rotifer Cloud): the nightly season job had failed since 2026-08-17, so season 1 never ended; it now closes an overdue season and opened season 2 on 2026-10-26. A daily check opens a GitHub issue whenever a scheduled database job fails or stops running.

v0.30.1 (2026-10-24) — MCP Server 0.19.4 in the Plugin and Skills

Section titled “v0.30.1 (2026-10-24) — MCP Server 0.19.4 in the Plugin and Skills”

Upgrading to 0.30.1 is how plugin users get MCP server 0.19.4.

  • Plugin and Skills pin @rotifer/mcp-server 0.19.4: usage reports are sent with your sign-in, an expired token is renewed automatically, and if renewal fails the server says so once instead of going quiet. serve now listens on 127.0.0.1 by default and caps request bodies at 256 KiB; the default stdio mode the plugin uses is unaffected.
  • Dependency security fixes: zod and fast-uri upgraded in the lockfile.
  • Server side (Rotifer Cloud): an invocation report is recorded under the account that sent it, and a client can no longer delete a gene that carries evidence. Closing an account keeps its genes and their evidence, and a leftover token from a closed account can no longer write. Gene authors see download counts, no longer who downloaded or when. An MCP call is counted under the signed-in account that reported it; reports without a sign-in, including those from MCP server versions before 0.19.4, are no longer counted.

v0.30.0 (2026-10-21) — Season-Relative Arena Scoring and Declared Gene Permissions

Section titled “v0.30.0 (2026-10-21) — Season-Relative Arena Scoring and Declared Gene Permissions”
  • F(g) scored against the season: rotifer arena submit compares a gene’s measured latency and cost with the season median of genes in the same domain and fidelity, and falls back to fixed constants, saying so in its output, when fewer than 5 such genes have measured runs. Scores stay estimated and outside the ranking.
  • Estimated submissions upload their measured runs too.
  • Submitting a gene again updates its Arena row instead of failing.
  • Genes run with the permissions their phenotype declares: on every CLI path (agent run, run, test, arena submit, the publish gate), only a Hybrid gene with a network block can reach the network, and only its allowed domains through rotifer.net; Native and Wrapped genes get none.
  • Outbound requests are checked before they are sent: each rotifer.net request is checked against the request count, host time and run deadline, and its cost is billed to resource_cost instead of the gene’s fuel.
  • Fixes: the genome snapshot after agent run counts a compiled Native gene as executable; genome import only suggests dropping --pinned when you passed it.
  • Server side (Rotifer Cloud): an Arena entry’s last_evaluated is now stamped by the server, re-submitting recomputes reputation, and a client-reported sandbox evaluation is recorded as estimated.

v0.29.0 (2026-10-21) — Genome Blueprint Format 1 and Stricter Imports

Section titled “v0.29.0 (2026-10-21) — Genome Blueprint Format 1 and Stricter Imports”

Four changes that may affect existing use. Two change a format: a TryCatch handler now receives {error: {geneId, errorCode, message, context}, original_input}, so a handler that reads error.code must read error.errorCode; and genomeId is now bp1: plus 64 hex characters covering only what is executed, so it is not comparable with 0.28.0 values. Two are stricter checks: a Blueprint’s Cond accepts only the forms agent run executes, and a gene’s rotifer.net request can no longer set client-managed headers such as Host.

  • Genome Blueprint format 1: rotifer genome import refuses a Blueprint without composition, with a required field missing, or whose schemas use a $ keyword other than $comment; rotifer genome export refuses to write any file that import’s format checks would reject.
  • Substitutes need exactly matching schemas: in capability mode a substitute gene is accepted only if its input and output schemas match the original’s exactly, ignoring descriptions, titles, examples and defaults.
  • Imports refuse what cannot be honoured exactly: non-finite numbers (1e400), integers JSON cannot hold exactly, duplicate keys, lone surrogates, and Cond forms agent run cannot execute (MATCHES, CONTAINS on a non-string, a field path) are rejected before anything is installed, and a role name can no longer resolve to a built-in object property.
  • TryCatch errors name the gene that failed: the handler’s error.geneId is the v2 ID of the gene that actually ran, and sandbox failures keep their own code (FUEL_EXHAUSTED, TIMEOUT, …) instead of a generic INTERNAL_ERROR.
  • Cond compares numbers by value: EQ and NEQ treat 1 and 1.0 as equal, inside objects and arrays too.
  • Gene network requests can no longer set client-managed headers: a rotifer.net request that sets Host, Content-Length, Transfer-Encoding, Expect or a hop-by-hop header is refused with -10 before any network traffic.
  • Sandbox HTTP client and TLS roots updated: the rotifer.net client moves to ureq 3, and rustls-webpki and webpki-roots are bumped for RUSTSEC-2026-0381 and 0382.

v0.28.0 (2026-10-20) — Genome Export and Import

Section titled “v0.28.0 (2026-10-20) — Genome Export and Import”
  • rotifer genome export <agent>: writes an agent’s genes, how they are composed and a capability query per role to a .rgenome file; every key and value is scanned for credentials first, and a hit aborts without printing the value. Wrapped genes export with a notice.
  • rotifer genome import <file>: rebuilds the agent from the Registry, installing Native and Hybrid genes by exact version (--pinned) or picking a substitute only when its Arena tier is verified and it clears the fitness and V(g) thresholds; when no substitute qualifies it installs the pinned gene and says why. --dry-run prints the plan and installs nothing. No Registry gene is verified yet, so today every import installs the pinned genes; Wrapped and never-published genes cannot be imported.
  • install checks content against the Registry: an installed gene’s phenotype is compared with the content_hash the Registry recorded, and a mismatch prints a warning without stopping the install.
  • Par, Cond and Try run on compiled genes: agent run no longer fails before executing these compositions on WASM genes, and no longer reports success when one of them fails.
  • Security scanner stops flagging eval inside strings and comments: rule S-01 ignores text inside string, template and regex literals and comments.
  • Duplicate content hashes go to whoever published first: the Registry stops recomputing content_hash and keeps the original publish time, so a later upload cannot claim an earlier author’s hash.
  • Leaderboard paging is stable: rows tied on score no longer repeat or go missing between pages.
  • Sandbox engine advisories cleared: wasmtime 48.0.6 → 48.0.7 (RUSTSEC-2026-0378 and 0379).

v0.27.0 (2026-10-19) — Content-Derived Gene IDs and Frozen P2P Wire Format

Section titled “v0.27.0 (2026-10-19) — Content-Derived Gene IDs and Frozen P2P Wire Format”
  • Content-derived gene IDs (v2): every gene now has an ID computed from its contract and its code — v2: plus a SHA-256 — so the same gene gets the same ID no matter who built it or when; rotifer wrap prints it, and a gene whose ID cannot be determined says why (spec).
  • P2P wire format frozen (v1): announcements are protobuf on /rotifer/p2p/1/announcements, validated before they are relayed, and carry no forgeable publisher field. Not compatible with 0.26.x P2P nodes — upgrade every machine in a P2P setup.
  • Bundled Wrapped genes declare their sources: clawhub-web-search, genesis-file-read and translator list their source files, so they now have gene IDs and can be announced.
  • Sandbox and TLS advisories cleared: wasmtime 48.0.5 → 48.0.6 (eleven advisories) and rustls 0.23.45 → 0.23.46 (four advisories).

v0.26.3 (2026-10-14) — Sandbox Engine and P2P Security Fixes

Section titled “v0.26.3 (2026-10-14) — Sandbox Engine and P2P Security Fixes”
  • Sandbox engine upgraded past ten new advisories: wasmtime moves from 47.0.4 to 48.0.5 and quinn-proto, the QUIC transport under P2P, from 0.11.15 to 0.11.19, clearing ten RustSec advisories published after 0.26.2 — including one rated critical in the sandbox engine. No source changes were needed.
  • P2P rejects forged, stale and future-dated announcements: an announcement must come from the node it names and fall inside the ±300 s freshness window; a re-injected signed message is no longer accepted again once GossipSub’s duplicate cache expires, and the inbound buffer is capped at 1024 entries.
Section titled “v0.26.2 (2026-10-13) — Consent for Installed Genes in Pipelines”
  • agent run asks before running an installed gene unsandboxed: a Cloud-installed gene that is not compiled to WASM no longer runs on the Node.js path inside a pipeline unless you pass --trust-unsigned, the same rule rotifer run already applied. In a TryPool the refused gene counts as a failure, so the pool fails over to the next one. The L0 gate still applies with the flag.
  • L0 gate runs before a pipeline step’s code is loaded: on the sequential path the gate used to run after the gene’s module was imported, so its top-level code had already executed; it now runs first.

v0.26.1 (2026-09-21) — Least-Privilege CI Credentials

Section titled “v0.26.1 (2026-09-21) — Least-Privilege CI Credentials”
  • Quality Observatory reporting drops its full-access key: CI’s test-report, security-scan and dependency-audit uploads used a service_role key with full project access; they now use a scoped ci_reporter role that can only insert into those three tables.
  • Anonymous read access removed from quality tables: four SELECT policies that made quality tables world-readable to anyone holding the project’s public anon key have been revoked, closing a data-exposure gap flagged in the 2026-09-02 security audit.
  • Rust dependency advisories cleared: rustls (TLS 1.3 handshake boundary issue), event-listener (unsound Send/Sync impl reached through libp2p-gossipsub), and a yanked gimli release all updated; cargo audit is clean again.

v0.26.0 (2026-09-09) — Gene TestSuite and T1 Publish Gate

Section titled “v0.26.0 (2026-09-09) — Gene TestSuite and T1 Publish Gate”
  • rotifer publish enforces the spec §47.5 T1 gate: publishing a Gene now requires an author-written testsuite.json that runs clean — crashing on illegal input fails, refusing it passes, and returning output passes only against a declared expectedOutput or expectedSchema (ADR-333). The gate applies to Native and Wrapped genes alike, and every blocking message names the command that gets you past it.
  • TestSuite format and runner: rotifer test now reads and runs the author’s own cases in the spec §4.2 TestSuite shape, plus a seeded 10-iteration property test; --json prints the run as spec §47.2 TestResult objects.
  • rotifer test --scaffold: writes a starter suite with one positive case and negative cases for a missing field, a wrong-typed field and the empty object, each checked against the Gene’s own inputSchema before it is kept. It never overwrites an existing suite.
  • Genes can refuse input: returning an object whose only key is __rotifer_error is reported as INVALID_INPUT (not retryable), identically in the compiled and Node execution paths (ADR-334).
  • Native genes without a compiled artifact are no longer passed off as working: rotifer install now says the Gene is at fault instead of reporting success, and rotifer compile exits non-zero rather than validating a Gene that cannot run.
  • Security scanner S-02 stops flagging regex.exec(): the rule matched JavaScript’s regex iteration as system command execution and blocked publishing; six of its seven hits on this repo’s own genes were false positives.
  • Thirteen project-owned genes handle malformed input: fixes include design-tokens emitting hsl(NaN), genesis-web-search searching for the literal “undefined”, and six genes crashing on wrong-typed input; all thirteen were republished with suites that pass the gate.
  • rotifer.dev assistant: it no longer writes Gene invocation records for Genes it never runs, and changelog content now ranks correctly for queries in the reader’s language.
  • Dependency advisories cleared: seven npm audit findings (six moderate, one high) resolved.

v0.25.1 (2026-09-07) — Cloud Commands Work Out of the Box

Section titled “v0.25.1 (2026-09-07) — Cloud Commands Work Out of the Box”
  • Cloud commands work on a fresh install: rotifer search, rotifer reputation --leaderboard and every other cloud command failed with No API key found in request unless you had manually configured a key — which nothing told you to do. The CLI now ships the publishable key it needs. That key is public by design: it is served in the rotifer.ai page source, and access is enforced by row-level security, not by the key being secret.
  • Stale keys in ~/.rotifer/cloud.json no longer break the CLI: Rotifer Cloud retired its legacy JWT API keys on 2026-09-07. A key saved before then is now skipped rather than sent, so an upgrade fixes the machine without you having to find and delete a file you may not remember creating. Self-hosted endpoints configured with a current key are unaffected.

v0.25.0 (2026-09-06) — Fitness Formula Correction

Section titled “v0.25.0 (2026-09-06) — Fitness Formula Correction”
  • F(g) efficiency terms are multiplied, not divided: L_score and Cost_score are already inverted, so dividing by them turned the spec’s penalty into a reward — fitness rose with latency, and Arena ranking selected against performance. The min(1.0) cap is gone with it; it existed only because dividing made the value unbounded, and it had flattened six leaderboard genes into a tie at 1.000. Scores and rankings move as a result. The 1000ms / 10000-fuel scales remain provisional pending a season-median pipeline, so the tau gate stays suspended while fitness inputs are incomplete — V(g) still hard-gates.
  • WASM sandbox escape closed: wasmtime 47.0.4 fixes a high-severity filesystem sandbox escape (RUSTSEC-2026-0269) present in 47.0.3.
  • rotifer wrap --from-clawhub works again: ClawHub’s download endpoint now answers 307, which the redirect handler did not recognise — the redirect body was piped into unzip instead. 307 and 308 are handled, and the response body is drained before following, which had hung the process indefinitely.
  • rotifer self-update reaches @rotifer/mcp-server: it had compared that package against the CLI’s own version number, so every mcp-server release was judged already-current and silently skipped. Each package is now compared against its own installed version, and rollback records them separately.
  • Dependency advisories cleared: fast-uri resolves to 3.1.7, closing four high-severity SSRF and host-confusion advisories reached through ajv.

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

Section titled “v0.24.0 (2026-08-31) — 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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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.
  • 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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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

Section titled “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.
  • 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

Section titled “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.

  • 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

Section titled “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

Section titled “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

Section titled “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

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

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

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)

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
  • 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
  • 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
  • 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
  • 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

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

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.

Upcoming milestones (subject to change):

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