Add a model configuration shortcut or guidance below missing API key errors #405

What happened

During first-time setup, FlyBot prompted me to choose a model. I selected one of the offered models, but the run failed with 本轮运行失败 and this error:

llm-deepseek: no API key for provider route "deepseek-official"; store DEEPSEEK_API_KEY through the credentials service (the web Models page writes it), or export DEEPSEEK_API_KEY in the launching environment

I initially could not find where to configure the model/API key in the UI. I later discovered that clicking the Chief avatar at the top exposes the model configuration entry. The configuration is available, but that route was not apparent from the error or the initial model selection flow.

Steps to reproduce

1. Start a fresh FlyBot Web installation without a configured DeepSeek API key.
2. Open Chief and select a model using the initial model picker (the observed error identifies the deepseek-official route).
3. Attempt a conversation/run.
4. See the missing-key error, without a nearby action or instructions that lead to model configuration.

Suggested behavior

Show a Configure model / API key action directly beneath the missing-credentials error, opening the relevant existing configuration UI. Alternatively, show clear instructions explaining that users can click the Chief avatar at the top to reach model configuration.

The error should give a new user an actionable next step within the UI, rather than requiring them to infer how the credentials service or launching environment relates to the page they are using. Ideally, the initial model picker should also make it clear when a model still needs credentials.

Environment and evidence

• FlyBot core: 0.2.0, checkout 9e6e2a0.
• DeepSeek Harness: 0.2.0-rc.2.
• Local Web deployment on Linux, Node.js 22.22.1.
• Observed and reported by the user during first use; the reporting agent has not independently reproduced the browser interaction.
• No screenshot attached. The exact error text and the subsequently discovered configuration entry are included above.

This report contains no API keys, authentication tokens, or personal data.