@openvtc/trust-tasks 0.28.3 → 0.28.5

package/CHANGELOG.md

@@ -11,6 +11,91 @@ 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.28.5 — 2026-11-01
+
+
+### Added
+
+- **vtc/elections/ballot-boxes/list**: 0.1 reads the community's trusted ballot boxes (#998)
+
+A manifest must name one of the community's trusted voting services in
+  ballotBox (VTI-VOT-082), or vtc/elections/create refuses it with
+  ballotBoxNotTrusted, but nothing let an administrator read that list: they
+  had to ask whoever operates the community's host. VTI's console manifest
+  builder could offer only a free-text DID field.
+
+  vtc/elections/ballot-boxes/list/0.1 answers a holder of
+  vtc.elections.manage with every trusted ballot box: its DID exactly as
+  ballotBox must name it, and the operator and sameOperator members are shown
+  for an election naming it (VTI-VOT-090), so the administrator choosing one
+  sees what their members will. Read-only; the list stays host configuration,
+  changed by no task.
+
+  Rust, TS, Go and Dart bindings regenerated.
+
+## 0.28.4 — 2026-10-30
+
+
+### Added
+
+- **vta/webvh/dids/update**: 1.1 lists or removes an existing log's did:scid alias (#992)
+
+* feat(vta/webvh/dids/update): 1.1 lists or removes an existing log's did:scid alias
+
+  Every did:webvh log is also a did:scid:vh:1 identity, but the two are distinct
+  subjects until the did:webvh document lists the did:scid DID URL in
+  alsoKnownAs (VTI-KEY-164). create/1.2 lists it in the first entry by default;
+  a log created before it, or without it, had no way to get it but sending a
+  whole replacement document with a hand-built DID URL — and the src encoding
+  (`%3A` for a port, `/` for each `:`) is exactly what a client gets wrong.
+
+  1.1 adds `scidAlsoKnownAs` (boolean): true lists the DID URL for the log's
+  current location (replacing one left from before a move), false removes
+  every did:scid entry naming this SCID. The agent derives the DID URL; the
+  caller never writes it. The response reports `scidAlsoKnownAs` and
+  `scidDidUrl`. New codes: `scidAliasRequired` (removing the alias of an
+  identity the agent presents as did:scid, VTI-KEY-166) and `noChange` (an
+  entry identical to the latest is not published, so the update key is not
+  rotated for nothing).
+
+  This is the pre-key-role path: vta/dids/update refuses every identity created
+  before key roles (notKeyRoleIdentity), which is every did:webvh DID that
+  exists today. Only adds, so 1.1 extends 1.0. All four bindings regenerated.
+
+- **peer-check**: Peer-check/ask 0.1 — a signed yes or no from a peer's own device (#973)
+
+* feat(peer-check): peer-check/ask 0.1 — a signed yes or no from a peer's own device
+
+  One party asks another a short question, such as "did you just ask me
+  for this?", over a channel they already share. The responder's device
+  prompts its user and returns a signed answer that echoes the challenge
+  and carries the task digest of the request, so the asker can verify it
+  against the responder's DID and it cannot be replayed against another
+  ask.
+
+  Draft. Specification, schema, negative examples and the regenerated Rust,
+  TypeScript, Go and Dart bindings.
+
+- **rooms/keys/act**: 0.9 completes rooms/records/put/0.4 (#990)
+
+rooms/records/put/0.4 (#987) lets a record on an open room carry a file,
+  its description and random file key in cleartext.file. 0.8's table is
+  closed (Recipient item 1) and names records/put at 0.1–0.3 only, so a
+  conforming key holder refuses 0.4 with typeNotActable: a member whose keys
+  their key holder holds could upload an open room's blob (upload/begin/0.2
+  is in the table) but never write the record that names it, and the blob
+  would sit unreferenced until collected.
+
+  0.9 adds rooms/records/put/0.4 to the put row, write, presentation
+  inserted, completed exactly as 0.3. The key holder neither mints nor checks
+  the file key: the producer mints it (put 0.4 Producer item 7), the host
+  checks the record (Host item 12), and the key holder signs what it was
+  handed unaltered (Recipient item 6).
+
+  Schemas are 0.8's and no error code is added; the table only widens, so
+  0.9 declares extends: "0.8" and every spec naming 0.8 stays current. All
+  four bindings regenerated.
+
 ## 0.28.3 — 2026-10-30
 
 

package/dist/_extends.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"_extends.d.ts","sourceRoot":"","sources":["../src/_extends.ts"],"names":[],"mappings":"AAAA,wEAAwE;AAExE;;;;;GAKG;AACH,eAAO,MAAM,mBAAmB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAM/D,CAAC"}
+{"version":3,"file":"_extends.d.ts","sourceRoot":"","sources":["../src/_extends.ts"],"names":[],"mappings":"AAAA,wEAAwE;AAExE;;;;;GAKG;AACH,eAAO,MAAM,mBAAmB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAQ/D,CAAC"}

package/dist/_extends.js

@@ -6,10 +6,12 @@
  * `extendsChain` follows them transitively.
  */
 export const EXTENDS_BY_TYPE_URI = Object.freeze({
+    "https://trusttasks.org/spec/rooms/keys/act/0.9": "0.8",
     "https://trusttasks.org/spec/rooms/records/put/0.4": "0.3",
     "https://trusttasks.org/spec/vta/did-templates/create/3.2": "3.1",
     "https://trusttasks.org/spec/vta/did-templates/get/3.2": "3.1",
     "https://trusttasks.org/spec/vta/did-templates/list/3.2": "3.1",
     "https://trusttasks.org/spec/vta/did-templates/update/3.2": "3.1",
+    "https://trusttasks.org/spec/vta/webvh/dids/update/1.1": "1.0",
 });
 //# sourceMappingURL=_extends.js.map

package/dist/_extends.js.map

@@ -1 +1 @@
-{"version":3,"file":"_extends.js","sourceRoot":"","sources":["../src/_extends.ts"],"names":[],"mappings":"AAAA,wEAAwE;AAExE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAqC,MAAM,CAAC,MAAM,CAAC;IACjF,mDAAmD,EAAE,KAAK;IAC1D,0DAA0D,EAAE,KAAK;IACjE,uDAAuD,EAAE,KAAK;IAC9D,wDAAwD,EAAE,KAAK;IAC/D,0DAA0D,EAAE,KAAK;CAClE,CAAC,CAAC"}
+{"version":3,"file":"_extends.js","sourceRoot":"","sources":["../src/_extends.ts"],"names":[],"mappings":"AAAA,wEAAwE;AAExE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAqC,MAAM,CAAC,MAAM,CAAC;IACjF,gDAAgD,EAAE,KAAK;IACvD,mDAAmD,EAAE,KAAK;IAC1D,0DAA0D,EAAE,KAAK;IACjE,uDAAuD,EAAE,KAAK;IAC9D,wDAAwD,EAAE,KAAK;IAC/D,0DAA0D,EAAE,KAAK;IACjE,uDAAuD,EAAE,KAAK;CAC/D,CAAC,CAAC"}

package/dist/index.d.ts

@@ -1252,6 +1252,9 @@ export import MessagingQueueStatus_v0_1 = _MessagingQueueStatus_v0_1;
 import * as _MessagingStatsShow_v0_1 from "./messaging/stats/show/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import MessagingStatsShow_v0_1 = _MessagingStatsShow_v0_1;
+import * as _PeerCheckAsk_v0_1 from "./peer-check/ask/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import PeerCheckAsk_v0_1 = _PeerCheckAsk_v0_1;
 import * as _ContactAnnotationsShared_v0_1 from "./persona/_shared/0.1/contact-annotations.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import ContactAnnotationsShared_v0_1 = _ContactAnnotationsShared_v0_1;
@@ -1684,6 +1687,9 @@ export import RoomsKeysAct_v0_7 = _RoomsKeysAct_v0_7;
 import * as _RoomsKeysAct_v0_8 from "./rooms/keys/act/0.8/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import RoomsKeysAct_v0_8 = _RoomsKeysAct_v0_8;
+import * as _RoomsKeysAct_v0_9 from "./rooms/keys/act/0.9/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import RoomsKeysAct_v0_9 = _RoomsKeysAct_v0_9;
 import * as _RoomsKeysBackfill_v0_1 from "./rooms/keys/backfill/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import RoomsKeysBackfill_v0_1 = _RoomsKeysBackfill_v0_1;
@@ -2726,6 +2732,9 @@ export import VtaWebvhDidsRotateKeys_v2_0 = _VtaWebvhDidsRotateKeys_v2_0;
 import * as _VtaWebvhDidsUpdate_v1_0 from "./vta/webvh/dids/update/1.0/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtaWebvhDidsUpdate_v1_0 = _VtaWebvhDidsUpdate_v1_0;
+import * as _VtaWebvhDidsUpdate_v1_1 from "./vta/webvh/dids/update/1.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtaWebvhDidsUpdate_v1_1 = _VtaWebvhDidsUpdate_v1_1;
 import * as _VtaWebvhDidsUpdate_v2_0 from "./vta/webvh/dids/update/2.0/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtaWebvhDidsUpdate_v2_0 = _VtaWebvhDidsUpdate_v2_0;
@@ -3125,6 +3134,9 @@ export import VtcDirectoryNotesList_v0_2 = _VtcDirectoryNotesList_v0_2;
 import * as _VtcDirectoryQuery_v0_1 from "./vtc/directory/query/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtcDirectoryQuery_v0_1 = _VtcDirectoryQuery_v0_1;
+import * as _VtcElectionsBallotBoxesList_v0_1 from "./vtc/elections/ballot-boxes/list/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcElectionsBallotBoxesList_v0_1 = _VtcElectionsBallotBoxesList_v0_1;
 import * as _VtcElectionsCancel_v0_1 from "./vtc/elections/cancel/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtcElectionsCancel_v0_1 = _VtcElectionsCancel_v0_1;