isLongLived with configuredWith and async await

Suppose I start a request using the new async await with isLongLived set true:

let config = CKOperation.Configuration()
config.isLongLived = true

let results =  try await database.configuredWith(configuration: config) { db in
    try await db.modifyRecordZones(saving: [...], deleting: [...])
}
try await processResults(results)

— then assuming my application exits and the requests is continued through by the system: would these operations eventually end up in the container's allLongLivedOperationIDs() like a classic CKOperation?

And a follow up question, assuming that the answer above is true: to "finish" these operations, we should we take the fetched long-lived operations, essentially insert our post-async await code into that completion block, and then add it to the database?

I think that all makes sense, and I am going to test it out, but figured it'd be worth asking