feat(dc-api): use aptitude matcher for openid4vp

[Wicpar]

Summary

• Replaces the OpenID4VP DC-API registry with the Aptitude matcher package.
• Registers mdoc and SD-JWT credentials in the matcher format, including DCQL options, VCT chains, and credentials hard-coded with no transaction-data types.
• Uses the Aptitude package defaults for OpenID4VP support config, including signed requests, dc_api.jwt, DCQL, and transaction_data support declarations.
• Applies Aptitude credential selections back into the existing Paradym OpenID4VP resolution/share path using the new selection.slots contract, mapping DCQL query IDs separately from wallet record IDs.
• Re-registers DC-API credentials after wallet unlock so a clean install/rebuild repopulates the native registry.
• Fixes the DC-API overlay unlock flow so PIN unlock waits for the SDK unlock state before resolving/responding.

Notes

• The Aptitude matcher package is added as a local tarball until it is published.
• The matcher tarball was updated to the latest local version (20260430150021) with the current TS12 matching constraints and new selection-slot response shape.
• Metro now treats .wasm files as assets so the Aptitude matcher package can load its WASM matcher.
• Commit history is cleaned into one feature commit on top of main.

Validation

• pnpm install --frozen-lockfile
• pnpm types:check
• pnpm style:check
• pnpm --filter @paradym/wallet-sdk build
• git diff --check
• pnpm prebuild
• pnpm android on Pixel_9_Pro_XL
• Manual DC-API OpenID4VP test on Pixel confirmed working with a fresh request

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typescript@​5.9.3

View full report