Files
dbx/.github/workflows
t8y2 d94a0fe312 fix(mcp): read the OS keychain key on native macOS/Windows package builds
Desktop enables os-keyring and provisions the data-encryption key in the
OS keychain during the data security upgrade, but dbx-mcp/dbx-cli package
builds compiled without any keyring backend (the feature became opt-in
for the Linux cross builds), so every desktop-migrated profile made the
MCP fail with DATA_MIGRATION_REQUIRED forever - the error even pointed
users back at a migration they had already completed.

- dbx-mcp gains an os-keyring forwarding feature; the native macOS and
  Windows MCP and CLI legs of the packages release build with it, Linux
  zigbuild legs keep the managed .dbx/secret.key fallback
- LocalBackend::open now separates 'key unreadable in this process'
  (SECRET_KEY_UNAVAILABLE with the DBX_SECRET_KEY_FILE/DBX_SECRET_KEY
  escape hatch) from genuinely pending legacy data, keeping the
  DATA_MIGRATION_REQUIRED contract for the latter (test covered)
2026-09-24 11:27:41 +08:00
..