@openvtc/trust-tasks 0.26.16 → 0.26.17

package/CHANGELOG.md

@@ -11,6 +11,41 @@ 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.26.17 — 2026-10-18
+
+
+### Added
+
+- **vtc/rooms/memberships**: List — every surface shows a member the same rooms, and finishes an acceptance any other began (#813)
+
+A member reaches their community from several surfaces (member portal via
+  the wallet, a terminal client, a phone). Each could see only the offers
+  open now or accepted within the repeat window, so a room taken up in one
+  was missing from the others after it; and an acceptance one surface began
+  could be finished by no other, because every other minted a different
+  KeyPackage and was answered alreadyAccepted.
+
+  - vtc/rooms/memberships/list 0.1 (new): the community's own record of the
+    caller's admissions to rooms it owns — offered, admitted or removed — for
+    as long as it keeps the record, with no credentials. repeatAcceptUntil
+    says while the Welcome is kept. Defines how a surface combines it with
+    rooms/keys/list (custody) so every surface derives the same state, and
+    forbids a surface keeping its own record of acceptance.
+  - rooms/keys/key-package 0.2: returns the outstanding KeyPackage for the
+    same room, member and invitation (alreadyMinted: true, original
+    expiresAt) instead of minting another; invitation and expiresAt
+    required. Mint, accept and Welcome now each answer a repeat with their
+    first answer.
+  - rooms/keys/act 0.5: adds vtc/rooms/memberships/list/0.1 to the table
+    beside the offer types (act 0.4, #810), on their terms, as "the
+    community types"; widens the type pattern to vtc/rooms/memberships/;
+    KeyPackages from key-package 0.1 or 0.2. A new version, not an edit to
+    0.4: the closed table admits a type 0.4 refuses.
+  - vtc/_shared/0.1/community-room: RoomMembership.
+  - vtc/rooms/offers/list 0.2, offers/accept 0.1: informative cross-links.
+
+  Bindings regenerated (Rust, TS, Go, Dart); additive modules only.
+
 ## 0.26.16 — 2026-10-17
 
 

package/dist/_shared/components.d.ts

@@ -8134,6 +8134,41 @@ export interface RoomMember {
     admittedAt?: string;
     removedAt?: string;
 }
+/**
+ * What vtc/rooms/memberships/list/0.1 returns: one room the community owns, and where the caller's admission to it stands in the community's own record. Unlike `OfferV2` it carries no credentials — those are collected with vtc/rooms/offers/list while an offer is open — and it is listed in every state, for as long as the community keeps the record, not only while an accept can be repeated. `label` and `description` are the room's as they stand when the record is read.
+ */
+export interface RoomMembership {
+    roomId: string;
+    /**
+     * The room's host: this community.
+     */
+    host: string;
+    label: RoomLabel;
+    /**
+     * Absent when the room has none.
+     */
+    description?: RoomDescription;
+    visibility: Visibility;
+    actions: MemberActions;
+    /**
+     * When the member's authority credential expires.
+     */
+    validUntil: string;
+    state: MemberState;
+    offeredAt: string;
+    /**
+     * When the community recorded the admission. Present when `state` is `admitted`, and kept when it becomes `removed`.
+     */
+    admittedAt?: string;
+    /**
+     * Present exactly when `state` is `removed`.
+     */
+    removedAt?: string;
+    /**
+     * On an `attributed` or `private` room in state `admitted`: until when the community keeps the Welcome, so that a repeated vtc/rooms/offers/accept carrying the same KeyPackage is answered with it. Absent on an `open` room, in any other state, and once the community no longer keeps it. A surface finding the member admitted but the room absent from its key holder's rooms/keys/list finishes the acceptance before this time, and asks an administrator to re-admit the member after it.
+     */
+    repeatAcceptUntil?: string;
+}
 /**
  * What a room says about itself to its own members: a name and, optionally, a description, short tags and an emoji, so that a member's wallet, portal or CLI can show what each room is rather than a DID.
  *