status

Reports the inference facts that are knowable up front: whether this build can execute local models and download them, which providers are compiled in, which of those have an API key and where it was found, and how many catalogued models are already on disk.

Released binaries ship the cloud providers and leave local model execution out, so `local_execution` is false in them and every catalogued local model is unavailable until `strata inference install-local` adds it; `local_remedy` says so. Knowing that from `status` is the point: previously the only way to find out was to run an operation and read the failure.

`key_source` names where a key was read from: the environment variable, or the config file's path when the key was set with `strata config set <provider>.api_key`. The runtime asks the environment first and the config file second, and reports the one that answered, so `key_source` is exactly what a `generate` or `embed` call would use. The key itself is never returned.

`base_url` is the endpoint a call to the provider would reach, and `base_url_source` names what redirected it: the provider's own environment variable (`base_url_env_var` - `OPENAI_BASE_URL`, `ANTHROPIC_BASE_URL`, `GOOGLE_GEMINI_BASE_URL`, with the same meaning as in each provider's SDK), or the config file's path when it was set with `strata config set <provider>.base_url`. The environment wins over the file, as for a key. When neither is set, `base_url` is the provider's public endpoint and `base_url_source` is absent. A provider that is not reached over HTTP reports none of the three.

`config_file` names the file those settings are read from and whether it can be used - `absent`, `readable`, `unreadable` or `malformed`. This is what separates a provider that was never configured from one whose stored key cannot be reached: every settings read folds a failure into "no value", so a key in a malformed file reports exactly like no key at all (`key_present: false`, `key_source: null`), and the remedy a caller would offer - set a key - is the wrong one, because a key is already there. The four words are the ones `strata doctor` prints for the same file. `config_file` is `null` when the runtime reads no file at all - an embedding application supplying its own settings, or a platform with no user config directory - which is a different answer from `absent`, a path with no file at it.

The model directory is shared by every database on the machine, so a model downloaded once is available to all of them.