chore(core): take adminScope from the registry binding, not a local copy

[stormer78]

Closes the loose end #187 left behind.

@openvtc/trust-tasks 0.17.4 is the first release whose generated provision/integration/0.3 binding declares adminScope and the context / adminScope summary members. #187 shipped ahead of it, so core/src/provision/send.ts declared all three by hand, with a comment promising they would go the moment the binding caught up. It has (trustoverip/dtgwg-trust-tasks-tf#385, released in #383), so they go.

What changes

• adminScope on the request body — deleted; ProvisionIntegrationPayload carries it.

• ProvisionIntegrationResponseBody — collapses from an Omit<…> & { summary: … & {…} } back to the generated response type.

• AdminScope — kept as an exported name, because a dozen wallet surfaces (store.ts, grant-command.ts, bridge-protocol.ts, onboard-view.tsx) name the concept without ever touching the payload type. But it is now derived:

  export type AdminScope = NonNullable<ProvisionIntegrationPayload["adminScope"]>;

  A hand-kept union is a second declaration of a registry-owned vocabulary and is free to drift from it silently. A derived one cannot — which is what CLAUDE.md's "match the spelling the registry declares today" is actually asking for.

And the floors, now that they are concrete

CLAUDE.md said "the registry release carrying adminScope". It can name versions now, and it records the part that is easy to get wrong:

trust-tasks-rs 0.18.3 is a correctness constraint on the VTA, not a preference, because its dispatch spine validates outgoing responses against the embedded schema — not just inbound payloads, which is all I had accounted for. Against 0.18.2 the new summary members are emitted and then refused by the agent's own guard, so a provisioning that fully succeeded returns 500 responseSchemaViolation. That is what OpenVTC/verifiable-trust-infrastructure#1303's delegated_consent_e2e failure was. Worth recording as something other than "a dormant feature until the bump", which is how I first described it.

Verification

No behaviour change — same wire members, same spellings, one source for them. npm run lint, npm test (914 pass) and npm run build clean.

The caret resolves to 0.17.5, which is current.