[Bug]: configure provider ignores an explicit --router disabled on a fresh profile #1341

OpenSquilla version or commit

0.5.3

Area

CLI

Reproduction steps

1. Start with a fresh named profile.

2. Configure a keyless vLLM-compatible endpoint and explicitly disable the
   router in the same command:

   opensquilla --profile router-repro configure provider `
     --provider vllm `
     --model qa-model `
     --base-url http://127.0.0.1:18001/v1 `
     --router disabled

3. Inspect the saved state:

   opensquilla --profile router-repro onboard status --json

4. Optionally inspect the generated config.toml.

Expected behavior

The explicit --router disabled option should be authoritative. The status
payload should report sectionDetails.router.routerMode as disabled, and the
saved configuration should contain the disabled router state.
This is also what the command help promises:

--router STR  recommended | openrouter-mix | disabled

Actual behavior

The provider is saved successfully, but the explicit router option is ignored.
The status payload reports:

{
  "sectionDetails": {
    "router": {
      "status": "ok",
      "detail": "SquillaRouter default tier: c1",
      "routerMode": "recommended",
      "routerBinding": "follow_primary"
    }
  }
}

The generated config contains a synthesized c0 through c3 router ladder
and does not contain enabled = false.
Running the router edit as a separate command works:

opensquilla --profile router-repro configure router --router disabled

The problem reproduced twice with independent fresh profiles. It also
reproduced with a different provider configuration, so it is not specific to
the model endpoint.

Environment

Windows 11

Diagnostic bundle and error reference

No response