How can I prevent generic pagination from overwriting other query parameters in my node?

I’m developing a declarative-style community node that integrates with an API using pagination. The API accepts a query parameter for the page number and returns a meta object with the current page and total pages, for example:

JSONCopied
{
  assets: [...],
  meta: { page: 1, total_pages: 5 }
}```

My issue is that when I use the generic pagination logic to set the page query string parameter, it appears to override other query string parameters (such as filters like Customer ID). If I remove the pagination logic, these additional fields are set correctly. I’ve included a simplified version of my code below for context:
```typescript
import type { INodeProperties } from 'n8n-workflow';

export const assetsOperations: INodeProperties[] = [
  {
    displayName: 'Operation',
    name: 'operation',
    type: 'options',
    noDataExpression: true,
    displayOptions: {
      show: {
        resource: ['assets']
      }
    },
    options: [
      {
        name: 'Get Many',
        value: 'getAll',
        description: 'Retrieve a list of assets',
        action: 'Retrieve a list of assets',
        routing: {
          request: {
            method: 'GET',
            url: '/customer_assets',
          },
          operations: {
            pagination: {
              type: 'generic',
              properties: {
                continue: '={{ $response.body["meta"].page < $response.body["meta"].total_pages }}',
                request: {
                  qs: {
                    page: '={{ $response.body["meta"].page ? $response.body["meta"].page + 1 : 1 }}'
                }
              }
            }
          },
          send: {
            paginate: true
          },
          output: {
            postReceive: [
              {
                type: 'rootProperty',
                properties: {
                  property: 'assets'
                }
              }
            ]
          },
        }
      }
    ],
    default: 'getAll'
  }
];

export const assetsFields: INodeProperties[] = [
  {
    displayName: 'Filters',
    name: 'filters',
    type: 'collection',
    placeholder: 'Add Filter',
    default: {},
    displayOptions: {
      show: {
        resource: ['assets'],
        operation: ['getAll']
      }
    },
    // This query string property doesn't get set unless I comment out
    // all the pagination logic above in the `getAll` operation.
    options: [
      {
        displayName: 'Customer ID',
        name: 'customerId',
        type: 'number',
        default: undefined,
        description: 'Filter assets by Customer ID',
        routing: {
          send: {
            type: 'query',
            property: 'customer_id'
          }
        }
      },
    ]
  }
];

n8n Version: 1.79.3
Database: sqlite
Running via Docker on Windows

How can I adjust my pagination or routing setup so that additional query parameters (like filters) are not overwritten by the pagination logic?