feat(ruvocal): governed workspace, runtime integrations and UI refresh

[ruvnet]

The current chat UI hides much of Ruflo's operational capability behind chat and server management dialogs. This adds a workspace that makes mission drafting, tool discovery and runtime observations visible while preserving deliberate execution and existing conversations.

Changes:

• Refresh chat onboarding and add a responsive workspace, recent conversations, mission presets and command search.
• Explore actual discovered MCP schemas with separate selection, inventory and connection states.
• Add an administrator observation API for configured Ruflo and MetaHarness status, an Autogenous adapter seam, and ruOS rendezvous health.
• Add seven exact bridge operations behind MCP_GROUP_OPERATIONS=true. Fix private base-server discovery without exposing deployment credentials or accepting browser overrides.
• Bound status calls, nested responses, pagination and timeouts. Keep drafts out of URLs and require submission before execution.
• Add four ADRs, a pinned ecosystem gap analysis, a reproducible validation receipt and scoped CI.

Validation:

• 163 application tests and 6 bridge tests passed.
• Production build and 6 built HTTP checks passed with local fixtures.
• ESLint passed for all 24 new source and test files.
• Full type check retains the baseline's 199 errors and 14 warnings in 51 files. Diagnostic paths and messages are identical after excluding shifted line positions.
• Lazy command search reduced the shared layout's compressed JavaScript from 126,586 bytes in the initial candidate to 103,495 bytes. Baseline is 102,208 bytes. This is a bundle-size comparison, not a latency benchmark.

This is a draft because browser interaction/visual acceptance, live integrations, remote CI and the existing type debt remain release gates. The production deployment revision is unknown. No deployment, operational promotion, live Autogenous evolution, or MetaHarness evaluation was performed. The installed Ruflo CLI recorded coordination and memory, but its version lacks the current flywheel status subcommand; integration contracts were verified against pinned source and MCP SDK fixtures.

Gap analysis · Validation and release gates · Source-bound receipt

Acceptance: a fresh session can draft an objective and inspect discovered capabilities; unknown status remains explicit; unauthorized runtime requests make no upstream calls; a mission stays an editable draft until submitted.