We have seen a couple of situation (SERVER-54611 and SERVER-59420) where certain internal parameters/behaviours are incorrectly marked as "unstable". This could lead to users seeing an 'APIStrictError' in cases where users did not use any unstable commands or parameters. This is more relevant on the sharded clusters, where mongos could attach a parameter (like fromMongos, needsMerge) that could be treated as unstable on the shards. We should consider adding a passthrough suite to help use protect against such changes. This will help us have a baseline of features that work with Stable API.