After switching from automatic-init-only to supporting explicit init()/close() cycles, SentryOptions retained its legacy singleton model. The singleton is created once at extension load and never recreated, so calling SentrySDK.close() followed by SentrySDK.init() causes old state to leak into the next session — callbacks, modified options, and event processors all persist.

Other Sentry SDKs create fresh options on each init() call.

A secondary issue: project settings values are loaded into the options in constructor, polluting default values visible to Godot's class reference XML doc generation.