Firestore gRPC Listen: Missing Deletion Events After Resuming Listener

I am calling the firestore.googleapis.com gRPC Listen API using Postman while manually modifying Firestore via the web UI (https://console.firebase.google.com/) to test for document changes.

When I add a new document, I receive the expected document_change event. However, after I delete a document, no document_change, document_delete, or document_remove event is returned, even though the count in the filter response decreases accordingly.

Here is my procedure:

1. Invoke Listen
2. Send ListenRequest
3. Inspect responses: retrieve the count from the filter response for my targetId and get the resume token from the target_change response (with CURRENT for my targetId).
4. End streaming.
5. Delete a document using the web UI.
6. Invoke Listen again.
7. Send ListenRequest using the count and resumeToken from step 3.
8. Inspect responses: the filter count is lower, but no deletion event is received.

I update the resumeToken after each request using the value from the CURRENT response for my targetId, and I use a bearer token for authentication. While new document additions trigger a proper event, deletions do not result in any document change events being sent.

An example of my ListenRequest message:

PROTOBUFCopied
Metadata: google-cloud-resource-prefix = projects/project1/databases/database1

{
    "database": "projects/project1/databases/database1",
    "add_target": {
        "target_id": 1,
        "resume_token": "CgkIzoO/uauyiwM=",
        "expected_count": {"value": 6},
        "query": {
            "parent": "projects/project1/databases/database1/documents",
            "structured_query": {
                "from": [
                    {
                        "collection_id": "TestCollection1",
                        "all_descendants": false
                    }
                ]
            }
        }
    },
    "once": false
}

Is my structured query correct? How can I adjust the query or procedure to capture all document changes, including deletions, or is this behavior a limitation/bug with Firestore?