pub fn task_scope(tenant: Option<&TenantId>, project: &ProjectId) -> StringExpand description
The tenant/project scope a task belongs to, as one opaque key. Task-keyed state (receipt indexes, learning) is always looked up under this scope, so equal task ids in different projects never meet.