Docs example says products are auto-included transitively, but they aren't extracted with `products: []`

[tobiaswatzek]

Question

Thefiltering guide has this example under "Transitive Dependency Behavior":

apis:
  - petstore-api

And petstore-api is assigned to:

• Product starter → auto-included
• Tag production → auto-included

The extract output includes all of these, even though only apiNames was specified in the filter.

I set up a filter based on the "How To: Extract Just One API" section on the same page, which lists only version sets, backends, named values, policy fragments, and tags as auto-included when their keys are set to [], and does not mention products:

apis:
  - my-api-1
  - my-api-2
backends: []
namedValues: []
products: []
tags: []
versionSets: []
loggers: []
diagnostics: []
groups: []
policyFragments: []
gateways: []
schemas: []
subscriptions: []
policies: []
policyRestrictions: []
documentations: []
workspaces: []

After running apiops extract with this filter, the products folder is empty. I confirmed directly against the APIM instance that both APIs are still assigned to their respective products, so the association exists and just isn't showing up in the extract output.

Did I misunderstand something about how the filter or --filter/transitive resolution is supposed to work here, or is the "Products containing the API" line in the Transitive Dependency Behavior example not accurate for the current release?

Context

@azure-tools/apiops-cli version 1.0.1. Filter file only sets apis: with two explicit API names and products: [], no --no-transitive flag passed to apiops extract.