MC-4445

Elmar clarified the target: Luci should not be boxed into MC ticket/chat runtime profiles. MC runtime profiles should remain for chats and scheduled tasks, but Luci as orchestrator needs native access to the underlying runtime/API/provider/model capabilities. Goal: - Create a native orchestrator runtime palette for Luci: callable capabilities for direct APIs, CLI workers, Hermes profile spawns, browser/visual QA, deterministic scripts, Larry/Mac remote lanes, review/council lanes. - Avoid duplicated config by deriving MC runtime profiles and native orchestrator capabilities from a shared runtime capability registry where practical. - Keep MC as ledger only when work is durable/user-facing/scheduled/audited. - Preserve MC runtime profiles for chats and scheduled tasks. Acceptance criteria: 1. Inventory current MC runtime profiles, scheduler profiles, Hermes profiles, CLI runtimes, API providers, and direct-script lanes. 2. Propose/implement a shared capability registry or adapter map. 3. Expose native orchestrator calls/runbooks so Luci can choose capabilities directly without forcing everything through MC ticket runtime sessions. 4. Ensure durable work records selected capability + evidence in MC. 5. Add tests/docs for chat profile use, scheduled task profile use, and orchestrator-native call selection. Expected check-in: 2026-05-30T09:24:35+00:00 (direct Control Room worker `cr-MC-4445-runtime-palette`; no legacy pickup).