SFB-070: Block invalid configured models in portal

[jmrpineda]

Discovery date: 2026-05-27
Detected in version: 0.1.5.664
Reported by: repository user
Severity: high
Environment: SpecForge.AI portal and configuration flows in local development
Scope / affected surface: portal startup, configuration validation, linked model and agent configuration
Evidence: user requirement raised on 2026-05-27; configuration currently allows entering the portal even when a model or agent that is actively used is not fully configured

Summary

The portal should treat incomplete configuration for actively used models or agents as a blocking condition. When the runtime depends on a linked model or agent that is defined but not fully configured, the portal must not continue as if the installation were valid.

Expected behavior

The application should evaluate a central validity check similar to IsValidConfiguration() before allowing normal portal usage. If any model or agent that is actually referenced by the current configuration is incomplete, the portal should navigate directly to configuration and clearly require the missing setup.

Current behavior

The current behavior does not enforce a blocking validation gate for model configuration completeness. A model or agent can be present in configuration, be referenced by active links, and still be insufficiently configured without forcing the operator into the configuration flow.

Reproduction steps

1. Define or link a model or agent that is used by the active runtime configuration.
2. Leave that referenced model or agent partially configured or otherwise invalid.
3. Open the portal with that configuration.
4. Observe that the portal is not blocked and does not force the operator into the configuration screen to complete the missing setup.

Environment details

• Surface: portal and configuration flow
• Relevant rule: only referenced models or agents are blocking
• Non-blocking case: models or agents that exist but are not used by any active link can remain incomplete without affecting portal startup
• Validation need: linked models must be completely configured before continuing

Notes

• The validation should be centralized rather than scattered across individual screens.
• A typical IsValidConfiguration() style entry point is the expected shape.
• The validation must distinguish between merely defined resources and resources that are actually used.
• When the validation fails, the operator should land directly on the configuration flow instead of discovering the problem later through runtime failures.