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.

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.

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