Three small findings from the MongoDB test-bed belong in Filament, not in laravel-mongodb. Open issues (or comments on filamentphp/filament#20442) for:

1. Sort order shape assumption. CanSortRecords, PrepareCsvExport and RelationshipJoiner read $query->getQuery()->orders[...]['column']. laravel-mongodb stores orders as [column => 1|-1], so the checks never match. Harmless today (an extra _id sort is appended) but it will bite when the default key sort matters.
2. Column summaries break the whole table for unsupported drivers. CanSummarizeRecords wraps the table query as a derived table via toSql(), so any table with a summarizer renders a 500 on MongoDB instead of omitting the summary row.
3. Relationship joiner distinct()->select('table.').* In released Filament this runs unconditionally for BelongsToMany option lists and returns nothing on MongoDB (empty Select, CheckboxList, AttachAction options). PR #20442 scopes it to pivot joins; confirm that is intentional and covered by a test.

Filament features affected: default key sorting and export ordering; summaries; every BelongsToMany select, checkbox list and attach action.