OrchestrUI v0.3.0 — Explainable candidate ranking

OrchestrUI 0.3.0 — Explainable candidate ranking

OrchestrUI now explains not only which UI ecosystem wins, but how every admissible candidate was ranked and why a hard compatibility gate rejected an option.

Highlights

• Multi-candidate routes consider policy order, installed-package evidence, current-plan reuse, dependency cost, bundle cost and role overlap.
• Supplied host versions are checked against bounded compatibility constraints before a candidate can win.
• recommend_stack returns candidate_rankings with factor-level scores and evidence.
• A candidate already present in the host can outrank an otherwise preferred addition when it remains compatible.
• Eight independently specified adversarial goldens run separately from the 50-case internal policy benchmark.
• All three executable fixtures now include installed dependency versions and captured ranking evidence.
• The npm archive excludes heavyweight promotional renders that are unnecessary at runtime.
• The orchestrui-mcp executable is normalized for current npm clients and checked against its built entrypoint.

Compatibility

• The MCP server remains read-only and keeps the existing six-tool surface.
• Existing text and partial-profile inputs remain supported; full HostProfile and TaskProfile input provides the strongest evidence.
• New response fields are additive. Existing selected/rejected and role-ownership fields remain available.
• Node.js 20 or newer is required.

Safety and licensing

• Ranking scores never override framework, version, ownership, conflict or asset-rights gates.
• No upstream component collection is mirrored or redistributed.
• Paid, Pro, authenticated and credentialed upstream content remains excluded.
• Rive runtime licensing remains separate from rights to individual .riv assets.

Documentation: README · Routing · MCP specification

Contact

For questions about OrchestrUI, integration, consulting, or collaboration:

   

OrchestrUI v0.2.1 — Registry alignment

OrchestrUI 0.2.1 — Registry alignment

This patch release corrects the case-sensitive MCP Registry namespace used for GitHub publisher authorization.

Fixed

• Changed the registry identity from io.github.ecd5a/orchestrui to io.github.ECD5A/orchestrui.
• Kept npm, plugin and MCP metadata on one exact 0.2.1 version.

All routing behavior, read-only safety boundaries and the seven-library catalog remain unchanged from 0.2.0. Use 0.2.1 for npm and MCP installation because it is the first version published under the final registry identity.

Install from npm · View the MCP Registry record · Read the versioned README

Contact

For questions about OrchestrUI, integration, consulting, or collaboration:

   

OrchestrUI v0.2.0 — Structured policy proof

OrchestrUI 0.2.0 — Structured policy proof

OrchestrUI is a deterministic UI policy, discovery and quality layer for coding agents composing modern frontend ecosystems.

Highlights

• Structured HostProfile and TaskProfile input replaces prompt-keyword routing as the primary decision path.
• A declarative policy matrix assigns one owner per UI role, preserves compatible host systems and records evidence for every selection and rejection.
• A committed benchmark verifies 50/50 structured routing scenarios across compatibility, ownership, conflicts and evidence invariants.
• Three executable project fixtures cover a Next.js/shadcn dashboard, an existing daisyUI admin and a marketing landing composition.
• Audit results separate pass, fail and pending; unverified rendered-host checks never raise the verified score.
• The fixture-backed Pages trace shows real routing results, rule IDs, owners and pending audit gates.
• The README preview uses a reproducible standards-compatible animation with an enforced 400 KB budget.
• Runtime version metadata has one source of truth, and CI verifies Node.js 20/22 plus Windows and macOS package smoke tests.

Safety and licensing

• MCP tools remain read-only: they do not execute install commands or write project files.
• Live registry access uses exact allowlists, public HTTPS destinations, response/time limits and normalized metadata.
• React Bits components and other upstream collections are not mirrored or redistributed.
• Paid, Pro, authenticated and credentialed upstream content is excluded.
• Rive runtime licensing remains separate from the rights to individual .riv assets.
• Upstream names and marks remain the property of their owners; no affiliation or endorsement is implied.

Requirements

• Node.js 20 or newer.
• Git for repository installation.
• Network access only for explicitly requested live public-registry lookup.

Documentation: README · Routing · MCP specification

Contact

For questions about OrchestrUI, integration, consulting, or collaboration:

   

OrchestrUI v0.1.0 — Initial public source

OrchestrUI 0.1.0

OrchestrUI is an agent-facing UI orchestration layer that helps coding agents choose and integrate the smallest coherent set of tools across seven frontend ecosystems.

Highlights

• Three reusable Agent Skills for routing, implementation and rendered-UI quality review.
• A read-only MCP server with six bounded tools for catalog lookup, stack recommendations, public component discovery, install guidance and plan auditing.
• Exactly seven supported ecosystems: Kokonut UI, React Bits, daisyUI, Bklit UI, Anime.js, Rive and Magic UI.
• Metadata-only public registry adapters with exact allowlists, response and timeout limits, normalization, short-lived caching and verified offline fallbacks.
• Codex plugin metadata, npm packaging metadata and MCP Registry metadata prepared for maintainer-controlled publication.
• Original OrchestrUI identity assets, README showcase and reproducible SVG-to-PNG rendering.
• CI, schema validation, typechecking, unit/protocol tests, optional live smoke tests and release packaging checks.

Safety and licensing

• MCP tools do not execute install commands or write to the filesystem.
• React Bits components and other upstream collections are not mirrored or redistributed.
• Paid, Pro, authenticated and credentialed upstream content is excluded.
• Rive runtime licensing is kept separate from the rights to individual .riv assets.
• All upstream names remain the property of their respective owners; no affiliation or endorsement is implied.

Requirements

• Node.js 20 or newer.
• Git for repository installation.
• Network access only when live public registry lookup is explicitly requested.

Documentation: README · Setup · Security model

Contact

For questions about OrchestrUI, integration, consulting, or collaboration: