Module registry 

Integration registry (RFC-041 Phase 2).

Declarative catalog of host integrations — each entry binds a CLI to detect (optional), install spec(s) (Phase 4), and a credential descriptor. The registry is loaded from share/default-integrations.toml and merged with user overrides in ~/.oxios/integrations.d/*.toml (whole-entry replace by id).

Credential model (H6): a single env_var cannot serve both CredentialStore::resolve (provider, 6-source) and resolve_secret (non-provider, 3-source). So the descriptor names the store key, the env var, and which resolver applies. The status endpoint must call the matching resolver — never poke one env var.

Structs

CredentialStatus

Where a resolved credential came from (mirrors CredentialSource for JSON).

Integration

A single registry entry.

IntegrationRegistry

Loaded integration catalog, keyed by id. Built by merging the shipped defaults with user overrides (whole-entry replace by id).

Enums

CredentialResolver

Which resolution path applies to a credential. Per D7 there is no Provider variant — LLM providers stay in engine_api and may only appear as read-only status cards via a separate UI path.