@openvtc/trust-tasks 0.28.19 → 0.28.21

package/CHANGELOG.md

@@ -11,6 +11,77 @@ 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.21 — 2026-11-08
+
+
+### Added
+
+- **vtc/badges**: Show answers the caller's own awards (myAwards), so a holder can share one (#1057)
+
+* feat(vtc/badges): show answers the caller's own awards (myAwards), so a holder can share one
+
+  vtc/badges/awards/share and unshare (#1054) name an award, but no read answered a holder their own accepted award identifiers for a community badge: mine/list carries badges, show only myCount. vtc/badges/show/0.1#response gains the optional myAwards - the caller's own accepted awards of the badge, newest first, each with its shared - and conformance item 4 says so. Additive, on a draft.
+
+- **auth/step-up**: Requests/show — the subject's wallet fetches a step-up refused to a delegated producer (auth/step-up/requests/show/0.1) (#1056)
+
+A relying party that refuses an operation until its subject steps up carries
+  the request inline in the refusal (approve-request/0.5, Inline delivery). That
+  only works when the producer of the operation can gather the evidence itself.
+  A process acting with a key the subject delegated to it — an assistant, an
+  automation — can redeem a recorded step-up but never make one. It cannot
+  forward the inline request to the subject's wallet either, because the inline
+  request carries no proof.
+
+  This adds a hand-off by reference. Beside the inline request, the relying
+  party MAY carry `details.stepUpHandoff` (`$defs.Handoff`): a single-use handle
+  of at least 128 bits, its expiry and this task's Type URI. The person's
+  approver agent sends the handle and receives two things:
+
+  - the relying party's own signed approve-request/0.5, addressed to the
+    subject, with the same challenge and binding as the inline request;
+  - the operation the step-up is bound to, exactly as received.
+
+  The agent verifies the proof and shows the operation itself. It recomputes the
+  binding where it knows the construction. It then answers with approve-response
+  0.7, signed by the subject's own DID, directly to the relying party. The
+  producer resends the identical operation, and the recorded step-up is redeemed.
+
+  A handle is answered at most once, atomically. Unknown, spent, expired and
+  settled handles all return `notFound`. Reading a handle is never part of an
+  approval, so a party that sees the handle can spend the read but cannot
+  approve.
+
+## 0.28.20 — 2026-11-07
+
+
+### Added
+
+- **vtc/badges**: Awards/share and awards/unshare — a holder shows an award outside the community (vtc/badges/awards/{share,unshare}/0.1) (#1054)
+
+* feat(vtc/badges): awards/share and awards/unshare — a holder shows an award outside the community (vtc/badges/awards/{share,unshare}/0.1)
+
+  The two tasks the VTC badges design note lists for showing a badge outside
+  the community (VTI-BDG-070 – 072), completing the vtc/badges/* 0.1 family.
+
+  - `vtc/badges/awards/share/0.1`: the holder of an accepted award of a badge
+    the community marked `shareableOutside` asks, and the community answers the
+    public locations it serves the award at — a verification location that
+    answers the credential exactly as issued with its status, and a baked image
+    where it serves one. Locations are the community's, unguessable (≥ 128
+    bits, never derived from the award), idempotent on a repeat, and disclose
+    no other holder nor a count (VTI-BDG-071). They stop serving on unshare,
+    take-back, retire and departure. Codes: badgesOff, notFound (unknown,
+    another member's, not accepted — alike), notShareable (insideOnly | kudos
+    | retired), publicLocationUnavailable.
+  - `vtc/badges/awards/unshare/0.1`: stops it; the locations answer as ones
+    that never existed; idempotent; not a revocation. Codes: badgesOff,
+    notFound.
+  - `_shared/0.1/badge.schema.json`: `AwardShare` and the optional
+    `Award.shared` (verificationUrl, bakedImageUrl?, since) — additive.
+
+  Both are acts of the member: a portal key the member authorized for
+  `vtc/badges` under auth/oob/grant/0.3 may sign them (VTI-BDG-095).
+
 ## 0.28.19 — 2026-11-06
 
 

package/dist/_shared/components.d.ts

@@ -5562,7 +5562,7 @@ export interface AutoGrantSweep {
     errors: number;
 }
 /**
- * One giving of a badge to one member. `givenBy` is the giver's directory entry, absent for an award a dynamic badge group's rule made. `note` is shown to the recipient, the giver, the badge's owners and administrators, never to other members. `credentialId` is present on an accepted award of a community badge: the badge credential that evidences it, renewed or re-issued as the badge's regime requires.
+ * One giving of a badge to one member. `givenBy` is the giver's directory entry, absent for an award a dynamic badge group's rule made. `note` is shown to the recipient, the giver, the badge's owners and administrators, never to other members. `credentialId` is present on an accepted award of a community badge: the badge credential that evidences it, renewed or re-issued as the badge's regime requires. `shared` is present on an accepted award of a badge its holders may show outside while its holder shares it (vtc/badges/awards/share).
  */
 export interface Award {
     awardId: AwardId;
@@ -5584,8 +5584,23 @@ export interface Award {
      */
     expiresAt?: string;
     credentialId?: GroupCredentialId;
+    shared?: AwardShare;
     ext?: Ext;
 }
+/**
+ * Where an accepted award is shown outside the community, by its holder's choice (VTI-BDG-070): the public location that answers a verification of exactly what the credential says, the baked image where the community serves one, and since when. Present only while the holder shares the award; absent once they stop, the award is taken back, the badge is retired or the holder departs. The locations are unguessable and name no other holder (VTI-BDG-071).
+ */
+export interface AwardShare {
+    /**
+     * The public location that answers the credential and a verification of it.
+     */
+    verificationUrl: string;
+    /**
+     * The badge's picture with the credential baked into it, for a website or an email signature. Absent where the community serves no baked image.
+     */
+    bakedImageUrl?: string;
+    since: string;
+}
 /**
  * Unencrypted metadata plus the encrypted payload. The KDF and cipher parameters travel in the clear so a reader can decrypt without knowing this specification's defaults.
  */