The user may run the resolved query. Meaningful only when resolvable is true.
OptionalcategoryCanonical full category path of the RESOLVED query (e.g. '/MJ/AI/Agents/'; '' when uncategorized).
OptionaldefinitionThe definition the provider would execute on a miss. Set by providers that execute queries themselves; a slot written under another definition is then a miss. Undefined where the provider cannot compute one (a client, whose slots the server validates instead).
OptionalqueryResolved query ID. With queryName, the identity the RunQuery fingerprint is built from, so
a request by ID, by name, or by both reaches the same slot.
OptionalqueryResolved query name — for log messages when the request was by ID only.
Metadata could resolve the request (by ID, or by name [+ stated category]).
Result of
ProviderBase.ResolveQueryCacheAuthorization— the single pre-fingerprint resolution + authorization computation the RunQuery TTL cache gate relies on (B45/B46). See the method JSDoc for the full contract.