chore(persona): take trust-tasks 0.17.1, where a resolved entry is a projection

`@openvtc/trust-tasks` 0.16.11 -> 0.17.1, and `task-surface.json` resynced to
vta-sdk 0.33.0.

The change that reaches a caller is `persona/profile/get`'s `resolved` array,
retyped from the pool `Attribute` to `ResolvedClaim` (dtgwg-trust-tasks-tf#370).
`attributeId`, `version` and `updatedAt` are OPTIONAL on a resolved entry, and
their absence is the whole distinction: it says the value is `inline`, held in
one profile with no pool record behind it. Under the old type all three were
required, so a conforming agent could not describe such a profile at all — it
had to choose between synthesising an `attributeId`, a false claim about where
a value lives, and omitting the entry, which returns a profile that appears to
present less than it does.

No source change was needed. `personaProfileGet` returns the generated response
type, and the console's `ResolvedProfile` was already written against the
corrected shape — it renders "held only here" on `claim.attributeId ===
undefined`, a branch the old type made unreachable by construction.

So the test keys on the generated schema, not on this library's behaviour: it
asserts `resolved.items` is `#/$defs/ResolvedClaim` and that the three pool
members are absent from its `required`. Checked against 0.16.11, where both
assertions fail. Asserting the console's rendering instead would have passed
against either version, which is the shape VTI#1258 got wrong.

The surface itself did not move: the same 226 URIs at vta-sdk 0.33.0 as at
0.32.3, 24 of them `persona/*`, all 24 implemented here. VTI's breaking ACL
change in that window (#1279) narrows what an entry may do without adding a
task or a schema member — capabilities travel in `ext` as
`org.openvtc.capabilities`, which this library does not yet set, and which the
surface check cannot see.

Author: stormer78

package-lock.json

@@ -28,6 +28,6 @@
     "esbuild": "^0.28.1"
   },
   "dependencies": {
-    "@openvtc/trust-tasks": "^0.16.8"
+    "@openvtc/trust-tasks": "^0.17.1"
   }
 }

package.json

@@ -8,6 +8,29 @@ For history before this file, see `git log` on `packages/core`.
 
 ## [Unreleased]
 
+### Changed
+
+- **`@openvtc/trust-tasks` 0.16.11 -> 0.17.1.** Carries the persona family's
+  two projection fixes. The one that reaches a caller is
+  `persona/profile/get`'s `resolved` array, now typed `ResolvedClaim` rather
+  than the pool `Attribute` (dtgwg-trust-tasks-tf#370): `attributeId`,
+  `version` and `updatedAt` are OPTIONAL on a resolved entry, and their
+  absence is what says the value is `inline` — held in one profile with no
+  pool record behind it. Under the old type all three were required, so a
+  conforming agent could not describe such a profile at all, and the console's
+  "held only here" branch was unreachable by construction. No source change
+  was needed: `personaProfileGet` returns the generated response type, and the
+  console was already written against the corrected shape.
+  `tests/admin.persona.mjs` now pins it, keyed on the generated schema
+  rather than on this library's behaviour, so a downgrade fails rather than silently
+  restoring a branch nothing can reach.
+- **`task-surface.json` resynced to vta-sdk 0.33.0** (was 0.32.3). The surface
+  did not move — the same 226 task URIs, 24 of them `persona/*`, all 24
+  implemented here. VTI's breaking ACL change in that window
+  (verifiable-trust-infrastructure#1279) narrows what an entry may do without
+  adding a task or a schema member: an entry's capabilities travel in `ext` as
+  `org.openvtc.capabilities`, which this library does not yet set.
+
 ## [0.7.0] - 2026-09-03
 
 ### Migration

packages/core/CHANGELOG.md

@@ -124,7 +124,7 @@
   "dependencies": {
     "@cfworker/json-schema": "^4.1.1",
     "@noble/curves": "^2.4.0",
-    "@openvtc/trust-tasks": "^0.16.11",
+    "@openvtc/trust-tasks": "^0.17.1",
     "@openvtc/vti-didcomm-js": "^0.7.0",
     "@openvtc/vti-tsp-js": "^0.2.0",
     "@scure/base": "^2.2.0",

packages/core/package.json

@@ -2,7 +2,7 @@
   "$comment": "Generated by scripts/sync-task-surface.mjs from a vta-sdk checkout. Do not hand-edit: re-run the script. Checked by tests/task-surface.mjs.",
   "source": {
     "crate": "vta-sdk",
-    "version": "0.32.3",
+    "version": "0.33.0",
     "scanned": "vta-sdk/src/**/*.rs"
   },
   "tasks": [

packages/core/task-surface.json

@@ -270,3 +270,45 @@ test("resolve is opt-in on profile/get", async () => {
   await personaProfileGet(resolved, { ...PARTIES, profileId: "01P", resolve: true });
   assert.deepEqual(resolved.sent[0].envelope.payload, { profileId: "01P", resolve: true });
 });
+
+test("a resolved profile entry is typed as a projection, not as a pool record", async () => {
+  // Keys on the generated schema rather than on this library's behaviour.
+  //
+  // The distinction matters because the console renders an `inline` claim —
+  // "held only here" — by testing `claim.attributeId === undefined`, and until
+  // `@openvtc/trust-tasks` 0.17.0 the response typed `resolved` as the pool
+  // `Attribute`, whose `attributeId`, `version` and `updatedAt` are all
+  // REQUIRED. That branch was unreachable by construction: the schema said the
+  // member is always there, so a conforming agent could not describe a profile
+  // holding an inline value at all (dtgwg-trust-tasks-tf#370).
+  //
+  // A test asserting the console's own rendering would have passed against
+  // either version, which is the shape VTI#1258 got wrong — it asserted
+  // behaviour this side controls instead of the constraint it was waiting on.
+  // So this asserts the constraint: the three pool members are optional here,
+  // and a downgrade of the dependency fails rather than silently restoring a
+  // branch nothing can reach.
+  const { RESPONSE_PAYLOAD_SCHEMA } = await import(
+    "@openvtc/trust-tasks/persona/profile/get/1.0/payload"
+  );
+
+  const response = RESPONSE_PAYLOAD_SCHEMA.$defs.Response;
+  const items = response.properties.resolved.items;
+  assert.equal(
+    items.$ref,
+    "#/$defs/ResolvedClaim",
+    "`resolved` must project a ResolvedClaim; the pool Attribute cannot describe an inline entry",
+  );
+
+  const claim = RESPONSE_PAYLOAD_SCHEMA.$defs.ResolvedClaim;
+  for (const member of ["attributeId", "version", "updatedAt"]) {
+    assert.ok(
+      claim.properties[member],
+      `ResolvedClaim should still carry ${member} — its presence is what says the value is pooled`,
+    );
+    assert.ok(
+      !claim.required.includes(member),
+      `${member} must be OPTIONAL on ResolvedClaim: an inline value has no pool record to have one`,
+    );
+  }
+});

packages/core/tests/admin.persona.mjs

@@ -178,8 +178,15 @@ test("coverage against the agent's surface is recorded, not discovered", () => {
     [...REFERENCED.keys()].map(family).filter((f) => canonicalFamilies.has(f)),
   );
 
-  // 161 of 178 as of vta-sdk 0.32.3. It was 130 until the specced-but-
-  // unimplemented gap was closed in one pass: `trust-task-discovery/0.1`,
+  // 187 of 207 as of vta-sdk 0.33.0. The steps below are in the order they
+  // happened. The 0.32.3 -> 0.33.0 resync moved no task: the surface is the
+  // same 226 URIs, and VTI's breaking ACL change in that window
+  // (OpenVTC/verifiable-trust-infrastructure#1279) narrows what an entry may
+  // do without adding a task or a schema member — an entry's capabilities
+  // travel in `ext` as `org.openvtc.capabilities`, which this check cannot
+  // see and this library does not yet set.
+  //
+  // It was 130 until the specced-but-unimplemented gap was closed in one pass: `trust-task-discovery/0.1`,
   // `acl/update/0.1`, `vta/webvh/servers/retire-orphan/0.1`,
   // `vtc/members/removal-notice/0.1`, `vta/app-state/*` (6), `vta/services/*`
   // (8), `vta/credentials/{issue,revoke}/0.1`, and