1.2.2

Reverted

• Rolled back M5 (declarative settings API from v1.2.0). In Obsidian 1.13+,
  overriding PluginSettingTab.getSettingDefinitions() causes the framework
  to render the declarative UI in place of our display() implementation,
  not alongside it as we had assumed. That regressed several UX affordances:
  API-key password masking (values shown as plaintext), the reveal toggle,
  the per-provider Healthcheck buttons, the "Open migration helper" and
  "발급 페이지 열기" action buttons — all vanished from the settings tab.
  The current SettingControl union has no secret/password variant and
  no idiomatic way to embed the healthcheck action affordances we rely on,
  so a partial declarative footprint can't preserve the tab. The v1.0.1
  community-plugin reviewer's warning about getSettingDefinitions() will
  come back — accepting that in exchange for correct UX and no plaintext
  key exposure. Deleted src/ui/settings-definitions.ts.