[muscariello]

Fixes #12

Changes

• New SlimHelper overloads:

  • createServer(Name local, IdentityProviderConfig, IdentityVerifierConfig, ClientConfig)
  • createChannel(Name local, Name remote, IdentityProviderConfig, IdentityVerifierConfig, ClientConfig)

  These let callers use JWT (e.g. EdDSA did:key with a JWKS allowlist), static JWT or SPIRE identities, and TLS/mTLS plus basic or JWT auth to the node.

• The existing secret/serverAddr overloads are unchanged and now delegate to the new ones. They use the new sharedSecretProvider / sharedSecretVerifier factories, which build the same configs as createAppWithSecret.

• JUnit 5 tests. Surefire now passes --enable-preview --enable-native-access=ALL-UNNAMED so tests can load the native bindings.

• README section with a JWT identity + TLS/bearer-token client config example.

Caller identity in SlimA2AHandler

I left this unchanged. In slim-bindings-java 2.0.0 the SlimRPC Context exposes only sessionId, metadata and the deadline. It has no source name and no verified peer identity, so handlers still see an anonymous user. Filling ServerCallContext from peer_subject/peer_issuer should come after the bindings bump to 3.3.

Testing

• mvn verify (Temurin 21): 5 tests pass.
• Manual e2e against a SLIM 2.0.0 node:
  • The echo example (shared-secret path) runs all demos.
  • A server and client using the new overloads with EdDSA JWT + JWKS complete GetExtendedAgentCard.
  • A client signing with a key that isn't in the JWKS is rejected (identity verification failed: token invalid).