Media generation, package installs, and ACP make the CLI more extensible

What changed

Roder adds first-party image generation providers, one-command package installation, and a stdio Agent Client Protocol adapter backed by the app-server runtime.

The release broadens what the CLI can host: media generation, extension bundles, slash commands, themes, skills, and ACP-compatible clients all get clearer entry points.

Why it matters

• The CLI can drive provider-neutral image generation through OpenAI and Google image providers, with generated media routed through the same artifact and app-server surfaces as the rest of Roder.
• Package installation gives users a single roder install path for bundles that include process extensions, skills, slash commands, and themes.
• Process extensions stay approval-gated before launch, so package installation does not bypass the runtime policy model.
• ACP compatibility makes Roder easier to embed into tools that already speak the Agent Client Protocol.

Installing packages

Use roder install npm:<package> for package bundles. The runtime keeps process extension launch behind explicit approval while making skills, commands, and themes available through one installation flow.