@ai-matrx/vault 0.1.56 → 0.1.58

package/CHANGELOG.md

@@ -1,8 +1,21 @@
 # Changelog
 
+## 0.1.58
+
+UNVERIFIED: this release has no Unreleased entry and the package-input comparison could not be made (git diff 1079de42b4..bc1fc5c3ce failed (commit not in this checkout)). Whether package inputs changed is unknown; consumer action is unknown.
+Check: `git diff 1079de42b4 bc1fc5c3ce -- apps/shared/vault`
+
+## 0.1.57
+
+- Authenticator inventory refreshes now ignore stale responses: a delayed older read cannot replace newer codes or conceal a newer failure. An active OTP seed missing from a complete inventory remains unavailable instead of appearing as an empty, setup-ready code list.
+- OTP setup rechecks the latest login state after confirmation. If the authenticator becomes unavailable or changes, enrollment stops and the typed key or uploaded QR stays available for retry.
+- If enrollment fails after creating a login, retry reuses that login instead of creating a duplicate. An acknowledged setup key is not enrolled twice; changing it requires fresh confirmation before the new key is enrolled. QR-image retries keep the selected file.
+
+Consumer action: none; the package's exported declarations and dependency/export metadata are unchanged.
+
 ## 0.1.56
 
-- No changes yet.
+- Authenticator inventory now preserves unavailable user, organization, and shared scopes so a partial failure is not shown as a confirmed empty code list. `VaultItem.authenticatorState` distinguishes `pending`, `known`, and `unavailable`; enrollment targets stay hidden until an item is known, and unavailable details offer Retry. Consumer action: custom authenticator-list providers must return `{ entries, unavailableScopes }`, and custom `VaultItem` producers must set `authenticatorState`; `createApiVaultPort` supplies these automatically.
 
 ## 0.1.55