Implement native swift EHBP client instead of using gomobile

[sachaservan]

Summary by cubic

Implemented a native Swift EHBP client and test suite, replacing gomobile bindings and updating CI and release workflows.

• New Features

  • SwiftPM package “EHBP” using swift-crypto, with request and streaming APIs.
  • Added unit tests for nonce computation, key derivation, request encryption/decryption, Go interop, and security (MitM resistance).
  • Added streaming tests for buffer management, fragmented chunk handling, and multi-chunk decryption.
  • CI job on macOS to build and run Swift tests.

• Refactors

  • Removed gomobile bindings and XCFramework build steps from release workflow.
  • Updated Go module: bumped to Go 1.25.1, upgraded testify, and removed gomobile/tools dependencies.

^{Written for commit 671e296. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 11 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="swift/Tests/EHBPTests/DeriveTests.swift">

<violation number="1" location="swift/Tests/EHBPTests/DeriveTests.swift:339">
P2: The `expectedKeyHex` value is parsed but never actually compared against the derived key. This makes the Go interoperability test incomplete - it only verifies `nonceBase` matches the Go implementation, not the key itself. Consider extracting the key bytes and comparing them, or at minimum remove the unused `expectedKeyHex` variable to avoid confusion.</violation>
</file>

<file name="swift/Tests/EHBPTests/SecurityTests.swift">

<violation number="1" location="swift/Tests/EHBPTests/SecurityTests.swift:33">
P2: The return value of `SecRandomCopyBytes` is discarded. If random number generation fails, the test would continue with zero-filled data, potentially giving false confidence in security properties. Consider checking the return value and failing the test on error.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[sachaservan]

@cubic-dev-ai review

[cubic-dev-ai]

@cubic-dev-ai review

@sachaservan I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 17 files