Bug: no details when securitySchemes.*.name changes

Description

When a change is introduced solely to the name property of an apiKey securitySchemes object in an OpenAPI 3.1 specification, openapi‑diff merely reports that a change occurred without providing any line‑level detail (path, field changed, old and new values).In addition, there appears to be no way to disable this rule via the usual options. (incompatible.security.scheme.scheme.change:false)

old.json
new.json

==========================================================================
==                            API CHANGE LOG                            ==
==========================================================================
                             **** Restful API
--------------------------------------------------------------------------
--                            What's Changed                            --
--------------------------------------------------------------------------
- GET    /rest/v1/info
--------------------------------------------------------------------------
--                                Result                                --
--------------------------------------------------------------------------
                   API changes are backward compatible
--------------------------------------------------------------------------

Thanks for your help!

まず添付された old.json と new.json の仕様を比較し、次に securitySchemes apiKey の名前変更処理と incompatible.security.scheme.scheme.change オプションを追跡してください。修正では、変更されたパス、フィールド、古い値と新しい値を報告しつつ、そのルールを無効化できるようにする必要があります。API の変更ログにこれらの詳細が反映されていることを確認してください。