Rotifer v0.7.5 & v0.7.6: Gene Registry, Version Chains & MCP Analytics

The gene ecosystem hit 50+ genes fast. Fast enough to expose two infrastructure gaps: domain fragmentation (the same concept registered under different domain names) and version isolation (no link between v0.1 and v0.2 of the same gene). v0.7.5 fixes both — and adds MCP call analytics so we can actually measure ecosystem growth. Both @rotifer/playground and @rotifer/mcp-server are updated on npm. Gene Domain Registry Previously, rotifer wrap --domain accepted any free-text string. Developers independently chose domains like ai.video , media.video , and video.generation for functionally identical categories. At 50 genes this was annoying; at 500 it would be chaos. v0.7.5 introduces a domain registry — a shared namespace that tracks all registered domains: rotifer wrap my-gene # ? Select a domain: # ❯ ai.text (12 genes) # ai.image (8 genes) # data.transform (5 genes) # [Enter new domain] When you run rotifer wrap without --domain , the CLI suggests existing domains from a local cache (sy