Bug: opensquilla doctor fails authentication with token-protected gateway

[arturop]

Environment

• OpenSquilla: 0.5.0rc4
• Docker
• Gateway auth mode: token
• Gateway is healthy and running

Problem

When the gateway uses token authentication, running:

opensquilla doctor --json \
  --config /var/lib/opensquilla/config.toml

returns:

Gateway unavailable
UNAUTHORIZED
Authentication failed

However, the gateway is healthy:

/healthz -> 200 OK
gateway status -> healthy

Calling the same doctor.status RPC with an authenticated GatewayClient returns:

{
  "status": "ready",
  "ready": true
}

Suspected cause

In src/opensquilla/cli/doctor_cmd.py, _fetch_report() connects with:

await client.connect(gateway_url)

It does not pass the configured gateway token.

Other CLI gateway RPC paths resolve authentication using default_gateway_token(config_path).

Verified fix

I tested the following change locally:

from opensquilla.cli.gateway_rpc import default_gateway_token

await client.connect(
    gateway_url,
    token=default_gateway_token(config_path),
)

I also propagated the --config path into _fetch_report() so token resolution uses the same config selected by doctor.

After rebuilding the Docker image, the normal command:

opensquilla doctor --json \
  --config /var/lib/opensquilla/config.toml

returns:

status: ready
ready: true
errors: 0
warnings: 0

The full doctor report then correctly shows the gateway, provider, memory, channels, sandbox, router, embeddings, and search provider as ready.

This appears to be a CLI authentication bug rather than a gateway availability issue.

I can prepare a small PR with the fix and a regression test if useful.