fix: use Hextra-compatible callout shortcodes and update CHANGELOG

- Replace Book theme `{{< hint >}}` with Hextra `{{< callout >}}` shortcodes
- Fix Hugo build failure in GitHub Pages deployment
- Add comprehensive v0.11.0 CHANGELOG entry with V2 vault format details

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: arimxyer

CHANGELOG.md

@@ -7,6 +7,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.11.0] - 2025-12-05
+
+### Added
+- **V2 Vault Format**: New key wrapping architecture with Data Encryption Key (DEK) and dual Key Encryption Keys (KEKs)
+  - Password-derived KEK for normal vault access
+  - Recovery-derived KEK for recovery phrase unlock
+  - Both KEKs wrap the same DEK, enabling secure recovery without password knowledge
+- **Vault Migration Command**: `pass-cli vault migrate` to upgrade V1 vaults to V2 format
+  - Preserves all existing credentials
+  - Generates new recovery phrase with proper key wrapping
+  - Interactive verification of new recovery phrase backup
+  - Optional BIP-39 passphrase protection ("25th word")
+- **Recovery Key Integration**: BIP-39 recovery phrases now fully functional for V2 vaults
+  - 6-word challenge recovery (73.8 quintillion combinations)
+  - Argon2id key derivation for recovery KEK
+  - Recovery-wrapped DEK stored in vault metadata
+- **New Vault Metadata Fields**: `wrapped_dek`, `wrapped_dek_nonce`, `recovery_wrapped_dek`, `recovery_wrapped_dek_nonce`, `recovery_salt`
+
+### Fixed
+- **Critical**: V1 vaults had a bug where recovery phrases could not unlock the vault - V2 format resolves this
+- Recovery tests updated for V2 key wrapping format
+- Stale keychain state handling in vault tests
+- JSON unmarshal error return value checking
+
+### Changed
+- Vault initialization now uses V2 format by default with `InitializeWithRecovery`
+- Recovery unlock path uses `RecoverWithMnemonic` with proper DEK unwrapping
+- Documentation updated with V2 architecture details, migration guide, and recovery workflows
+
+### Security
+- AES-256-GCM encryption for DEK wrapping with unique nonces
+- Argon2id (memory-hard) for recovery phrase key derivation
+- PBKDF2-SHA256 (600,000 iterations) for password key derivation
+- Separate salts for password and recovery derivation paths
+
 ## [0.10.0] - 2025-11-12
 
 ### Added

docs/02-guides/recovery-phrase.md

@@ -18,9 +18,9 @@ Pass-CLI's BIP39 recovery feature generates a 24-word recovery phrase when you c
 - [OK] **Fast**: Recover in under 30 seconds
 - [OK] **Optional**: Can skip with `--no-recovery` flag if you use keychain integration
 
-{{< hint warning >}}
+{{< callout type="warning" >}}
 **V1 Vault Users**: If you created your vault before v0.2.0, your recovery phrase will NOT work. V1 vaults have a bug where recovery phrases cannot unlock the vault. You must migrate to V2 format first. See [Migrating to V2 Format](#migrating-to-v2-format) below.
-{{< /hint >}}
+{{< /callout >}}
 
 ## Setting Up Recovery
 
@@ -86,9 +86,9 @@ pass-cli init --no-recovery
 
 V1 vaults (created before pass-cli v0.2.0) have a critical bug: recovery phrases cannot actually unlock the vault. V2 vaults fix this by implementing proper key wrapping, making recovery phrases fully functional.
 
-{{< hint info >}}
+{{< callout type="info" >}}
 **Check Your Vault Version**: Run `pass-cli doctor` to see if your vault is v1 or v2. If it shows "Vault Format: v1", you need to migrate.
-{{< /hint >}}
+{{< /callout >}}
 
 ### Migration Steps
 
@@ -162,9 +162,9 @@ Write down these 24 words in order:
    • Your old recovery phrase (if any) is now invalid
 ```
 
-{{< hint danger >}}
+{{< callout type="error" >}}
 **Important**: Your OLD recovery phrase no longer works. The new recovery phrase shown here is what you must use to recover your vault.
-{{< /hint >}}
+{{< /callout >}}
 
 #### Step 5: Verify Your Backup
 
@@ -233,9 +233,9 @@ Use recovery if:
 - [OK] You have your 24-word recovery phrase
 - [OK] Your vault is V2 format (or migrated to V2)
 
-{{< hint warning >}}
+{{< callout type="warning" >}}
 **V1 Vaults Cannot Use Recovery**: If you haven't migrated to V2 format yet, recovery will not work. See [Migrating to V2 Format](#migrating-to-v2-format) above.
-{{< /hint >}}
+{{< /callout >}}
 
 **Note**: If keychain is enabled and accessible, you don't need recovery. Your master password is stored securely in your OS keychain.