getSpaceCredential probes the host of the attested client_id for /.well-known/atproto-did and falls back to a stub when it publishes no DID. The probe went through resolve_handle_http, whose #[instrument(err)] logs every failure at ERROR, so a consumer that serves only client metadata (hub.highport.space, in production) raised an ERROR and a WARN on every credential, on a flow that then worked.
atproto-identity gains resolve::fetch_well_known_did: the same validated fetch without the error-level event, which resolve_handle_http now delegates to. The PDS recipient probe uses it and logs its miss at DEBUG as before. The "recipient resolved via stub" line drops to INFO when the stub carries an endpoint; a stub without one still warns at registration.
Adds a test for a recipient whose client_id host is not an identity: the probe is attempted, the stub is returned, and nothing logs at WARN or above. It fails against the old probe with an ERROR event.
Kata: atproto-crates#xm3z