When Netclaw starts without a valid inference provider/model configuration,
the daemon now launches in degraded mode with a No-Op IChatClient instead
of failing host startup. Chat turns return a fixed banner beginning with
"No valid model configuration detected." plus recovery steps (netclaw
doctor, netclaw model, edit netclaw.json) so operators can discover and
fix the configuration problem.

Validation is now tri-state (Valid / NoProviderConfigured / Invalid):
malformed configuration (declared provider missing credentials, schema
violations, model points to an unconfigured provider) still fails startup
loudly — only the genuinely-not-configured case selects the No-Op fallback.
The previous silent local-ollama default in Program.cs is removed.

- IChatClientProvider.IsDegraded default interface method (false on real
  providers, true on NoOpChatClientProvider) so doctor and diagnostics can
  query the state without sniffing concrete types
- netclaw doctor: new Chat Client check reporting pass/warn/fail
- Init wizard: provider health check emits warn-level item (not fail) when
  no provider is configured; daemon still starts in degraded mode
- netclaw-operations skill, PRD-004, PRD-005 updated; skill version 2.9.0

Operator typo in Models:Main.Provider (e.g. "ollama-local1" vs configured
"ollama-local") previously crashed the daemon with a raw
ProviderPluginFactory stack trace because the validation classified the
mismatch as Invalid but the DI extension fell through to lazy factory
construction instead of pre-throwing.

Two fixes:

- ProviderRuntimeValidation: "model references unknown provider" now
  returns NoProviderConfigured. From the operator's standpoint this is
  the same remediation as genuinely-no-provider (fix the model section
  via `netclaw model` or edit netclaw.json); the No-Op banner's
  "Available providers:" line surfaces the configured names so the typo
  is obvious. The doctor check correspondingly reports warn instead of
  error for this case.

- DaemonProviderServiceExtensions: when validation does return Invalid
  (currently unreachable in practice, but a real path for future stricter
  validation), register an IChatClientProvider factory that throws
  immediately with the validation reason — no more raw factory stack
  traces deep in the DI graph.

Includes regression tests at the validation, DI-registration, and doctor
layers exercising the exact "ollama-local1" scenario from the user report.

…value

When the daemon is running in No-Op degraded mode, `ncl chat` previously
showed the stale/invalid model name from netclaw.json (e.g. "gemma4" even
though that model lives on an unconfigured provider). The CLI builds its
own ModelCapabilities locally from netclaw.json without consulting the
daemon's actual chat-client state, so the broken config leaked into the
status bar.

CLI's ModelCapabilities factory now runs ProviderRuntimeValidation against
the same config it just loaded; when the validation outcome is non-Valid
it substitutes a sentinel ModelId ('(no model — run \`netclaw model\`)')
and zeros the context-window probe — matching the daemon's No-Op selection
without a round-trip.

…ealth

ncl status previously reported overall=healthy and showed the configured
(broken) model values when the daemon was running with the No-Op chat
client — e.g. "model: gemma4 (provider: ollama-local1, ...)" — completely
hiding the degraded state from operators.

Wire-level: DaemonRuntimeStatus.Model gains Degraded + DegradedReason.
DaemonRuntimeStatusService populates them from the running
IChatClientProvider.IsDegraded and the ProviderRuntimeValidation singleton.
ResolveOverallStatus now flips to "degraded" whenever the chat client is
No-Op, regardless of other subsystem health (the daemon can't actually
serve model responses).

CLI formatter: when Degraded=true, the model section renders as
"model: (none — No-Op chat client active)" with the validation reason
and a recovery hint, instead of the stale ModelId/Provider line.

Status service constructor takes the new dependencies as optional
trailing parameters so the seven existing tests don't need touching.

Filter Ollama embedding-only models during provider discovery so init selects a chat-capable model.

…iew/pr-1214-explicit-unconfigured-model

…ured-model' into review/pr-1214-explicit-unconfigured-model

…cit-unconfigured-model