@ai-matrx/vault 0.1.52 → 0.1.53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +8 -2
- package/dist/index.cjs +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,9 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.53
|
|
4
|
+
|
|
5
|
+
- Added the shared Password health view, durable scan recovery, explicit unchecked breach lookup, current-result accounting and existing editor remediation. Consumer action: adopt the compatible generated API with health stream types and runtime follower before this Vault package, and verify server support. Breach checks require explicit selection; unknown coverage remains visible. Installed and native acceptance remain separate.
|
|
6
|
+
- Web workspace lifecycle now retires account/context caches and pending findings while same-user token refresh preserves in-place confirmation. Durable runtime notes restore progress counts. Consumer action: retire the complete host workspace on actor/context changes without keying it to ordinary bearer refresh.
|
|
7
|
+
|
|
3
8
|
## 0.1.52
|
|
4
9
|
|
|
5
|
-
|
|
6
|
-
|
|
10
|
+
- Added Password health with confirmed scans, address-backed recovery, count-only progress, current-result validation and links into the existing item editor. Breach lookup starts unchecked and requires explicit selection. The optional `VaultPort.health` supplies scan, resume, read, identify and follow operations; older custom ports show the view as unavailable.
|
|
11
|
+
|
|
12
|
+
Consumer action: upgrade `@ai-matrx/api` to the current latest before adopting this package, including the account health endpoints, health stream types and runtime-operation follower, and verify that the server supports them. API-backed hosts receive the health port automatically. Custom hosts enabling it must supply the optional port and preserve `healthRequestId` and `healthExecutionId` through their location round trip. Keep the existing confirmation flow and explicit breach selection.
|
|
7
13
|
|
|
8
14
|
## 0.1.51
|
|
9
15
|
|
package/dist/index.cjs
CHANGED
|
@@ -9683,7 +9683,7 @@ var import_account = require("@ai-matrx/api/account");
|
|
|
9683
9683
|
var import_architecture = require("@ai-matrx/api/architecture");
|
|
9684
9684
|
function createHealthPort(api) {
|
|
9685
9685
|
return {
|
|
9686
|
-
start: (requestId, signal,
|
|
9686
|
+
start: (requestId, signal, options) => (0, import_account.startPasswordHealthScan)(api, { body: options.check_breaches ? { check_breaches: true } : {} }, { requestId, signal, totalTimeoutMs: null }),
|
|
9687
9687
|
resume: (executionId, requestId, signal) => (0, import_account.resumePasswordHealthScan)(api, { path: { execution_id: executionId } }, { requestId, signal, totalTimeoutMs: null }),
|
|
9688
9688
|
read: (executionId, signal) => (0, import_account.getPasswordHealthScan)(api, { path: { execution_id: executionId } }, { signal }),
|
|
9689
9689
|
identify: (requestId, signal) => (0, import_architecture.operationStatus)(api, { path: { request_id: requestId } }, { signal }),
|