Description the bug

When viewing a Recipe in the Goose Desktop UI, the recipe details show the globally-selected provider/model instead of the provider/model specified inside the recipe's YAML. In other words, even though the recipe YAML explicitly sets a different provider/model, the Recipe details page displays (and therefore appears to indicate) the global LLM selection, which is misleading and makes it hard to confirm which model the recipe will run with.

To Reproduce
Steps to reproduce the behavior:

• In Goose Desktop Settings → Provider / Models, set a global provider & model (for example: "OpenAI — gpt-4o").
• Create a recipe YAML that explicitly specifies a different provider/model. Example

version: 1.0.0
title: Example recipe that targets a different model
description: Demo
goose_provider: anthropic
goose_model: claude-sonnet-4

• Open the Recipes view in the Goose UI and either Import the recipe or open the recipe file from the UI.
• Inspect the recipe details / metadata /footer pane (where it displays Provider & Model).
  See the error: the UI shows the global provider/model ("OpenAI — gpt-4o" in the example) instead of the recipe's specified provider/model ("anthropic / claude-sonnet-4").

Expected behavior

• The recipe page should show the provider & model declared in the recipe YAML (if present).
• If the UI must show the global model somewhere, it should be clearly separated from the recipe's model so users cannot mistake the global model for the recipe's configured model.

Screenshots

OS & Arch: macOS (Tahoe - 26.1, Mac Mini - M.2)
Interface: UI (Desktop)
Version: Goose Desktop version v1.20.0
Provider & Model: OpenAI gpt-5-mini