Image generation via A2A

The slides app's generate-image script has two paths:

1. A2A delegation to the Images app — preferred when IMAGES_A2A_URL (and ideally IMAGES_A2A_KEY or a shared A2A_SECRET) is configured. The Images app maintains brand libraries with reference images, palette, and style brief; every generation grounds in the user's chosen library.
2. Direct Gemini provider — fallback. Uses the slides app's generic DEFAULT_STYLE_REFERENCE_URLS and the user's GEMINI/OPENAI key. Works without the Images app, but generations are off-brand by default.

templates/slides/actions/generate-image.ts checks IMAGES_A2A_URL first; on success it returns the A2A reply verbatim. On any failure (network, timeout, blocked) it falls through to the direct provider — slides keeps working standalone.

When to use which path

You don't get to choose at the action layer — the script picks based on env. But you should know:

• Workspace deploys with both slides and images apps mounted should always have A2A configured. Nothing else is needed from the slides agent's side.
• Standalone slides deploys (no Images app) fall through automatically.

Calling explicitly from the agent

When generating images for slides, call: