@openvtc/trust-tasks 0.23.8 → 0.24.0

package/CHANGELOG.md

@@ -11,6 +11,60 @@ The package versions over **its own API** — what a consumer compiles against
 not over `SPEC.md`. Below 1.0 a breaking change bumps the leading non-zero
 component.
 
+## 0.24.0 — 2026-10-11
+
+
+### Specifications
+
+- **rooms**: An unauthorized room request is refused with the standard permissionDenied (#743)
+
+Thirteen rooms specifications (create, epoch/{commits,mint,prune},
+  keys/open, keys/present 0.1 and 0.2, owner/{claim,transfer},
+  records/{curate,get,list,put} 0.1) declared a task-specific
+  `<slug>:notAuthorized` for a failure the framework already names: an
+  authorization refusal is the standard `permissionDenied` (SPEC §7.2, §8.3).
+  The extended code shadowed it, so a consumer switching on
+  `permissionDenied` never matched it, and a party that did not recognise it
+  degraded it to `taskFailed` (§8.5), a worse signal than the code it
+  duplicated. The later rooms specifications (records/put 0.2 onward) already
+  use the standard code, as the reference room host does for every version.
+
+  Each withdrawn declaration's condition is kept as one sentence at the end of
+  the specification's Conformance section, naming `permissionDenied`. Same
+  correction as `vta/app-state:permissionDenied` in 0.11.3.
+
+  Breaking for trust-tasks-rs: the thirteen `error_codes::NOT_AUTHORIZED`
+  constants are removed from the generated rooms modules. A consumer emitting
+  one should emit `StandardCode::PermissionDenied` instead.
+
+## 0.23.9 — 2026-10-10
+
+
+### Added
+
+- **external**: VTA external accounts — management, credential issuance and Sui signing (#740)
+
+* feat(external): VTA external accounts — management, credential issuance and Sui signing
+
+  Adds the external/* family: external/accounts/{list,get,create,update,secret/set,bindings/grant,bindings/revoke,setup,probe,keys/rotate,suspend,resume,archive,restore,delete}/0.1, external/credentials/issue/0.1 and external/sign/0.1, with shared shapes and family conventions in external/_shared/0.1.
+
+  A key custodian holds an identity at a third party and never releases its key or secret. Integrations bound to the account get short-lived credentials the custodian obtained and downscoped itself, sealed to the caller, or signatures over Sui transactions the custodian decoded and checked against an allow-list. Every model pins the custodian's verification material at the provider, so none needs the custodian to be reachable from the internet; plain OIDC discovery federation is excluded for that reason.
+
+- **rooms**: Files in data rooms, and VTC room storage administration (#739)
+
+* spec(rooms): shared file and blob types
+
+- **auth/oob**: Add the auth/oob out-of-band sign-in Trust Task family (#738)
+
+* feat(auth/oob): add the auth/oob out-of-band sign-in family
+
+  Eight Trust Task specifications for out-of-band sign-in started by a
+  trigger link: request, claim, prove, identify, respond, grant, redeem
+  and cancel, with a shared auth/oob/_shared/0.1 component (closed
+  purpose and mode lists, handle, key, number, origin, requester), the
+  family conventions, and the binding note defining the sign-in trigger
+  link (VTI-LNK) in place of the trusttasks://oob scheme.
+
 ## 0.23.8 — 2026-10-05