[PM-38808] Support optional encrypted Cipher.name

[shane-melton]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-38808

📔 Objective

The SDK is making the encrypted Cipher.name field optional (String → String?) as part of the blob encryption migration (sdk-internal#1122) — blob-encrypted ciphers carry the name inside the sealed data blob rather than as a top-level field.

Cipher.toFailureCipherListView() builds a CipherListView (whose name is non-null) directly from the encrypted Cipher, so the now-nullable name no longer compiles. This falls back to an empty string when the name is absent.

The decrypted CipherView / CipherListView name fields are unchanged, so all UI and sorting is unaffected.

Pairs with the SDK version bump.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed a single-line change in VaultSdkCipherExtensions.kt#toFailureCipherListView that swaps name = name for name = name.orEmpty() to accommodate the SDK's Cipher.name going from String to String? as part of the blob encryption migration. The function is only invoked on undecryptable ciphers (decryptCipherListResult.failures) where the encrypted name is opaque to the UI, so falling back to an empty string is appropriate and non-impactful to sort, filter, and grouping logic on decrypted ciphers. Existing unit tests in VaultSdkCipherExtensionsTest.kt continue to exercise the function across cipher types, and the PR is correctly scoped as a compile-time companion to the SDK version bump.

Code Review Details

No findings.

[david-livefront]

This has been addressed in this PR.