chore: clean up generated mobile artifacts

[pwltr]

Summary

• Stop tracking generated iOS XCFramework artifacts in git
• Stop tracking generated Android Kotlin bindings, native libraries, and debug symbols in git
• Move generated iOS release artifacts to dist/ios
• Keep bindings/ios focused on SwiftPM source/interface files
• Update Swift package support to iOS 17 only
• Remove Python bindings and Python build entrypoints
• Update README, agent docs, ignore rules, and CI paths for the iOS/Android-only build flow

Details

This cleans up the package layout so generated binary artifacts are no longer committed to the repository.

The iOS build now writes generated release artifacts to:

• dist/ios/VssRustClientFfi.xcframework
• dist/ios/VssRustClientFfi.xcframework.zip

bindings/ios now only contains the Swift wrapper source and C interface files consumed by Package.swift.

The Android build continues to generate its Kotlin binding, JNI libraries, and debug symbols under bindings/android, but those generated outputs are ignored by git and produced by ./build_android.sh or CI.

The Swift package now requires iOS 17+, matching Bitkit iOS’s minimum deployment target and the iOS artifact build configuration.

Python binding support has been removed from the build surface, including build_python.sh, bindings/python, and related README/agent instructions. ./build.sh all now builds iOS and Android only.

Testing

• Ran ./build_ios.sh successfully and verified the XCFramework is generated under dist/ios
• Ran shell syntax checks:
  • bash -n build.sh
  • bash -n build_ios.sh
  • bash -n build_android.sh
• Validated SwiftPM manifest after the iOS 17/tools-version update
• Updated CI validation paths so iOS bindgen checks dist/ios and validation no longer references removed Python scripts

[pwltr]

@ovitrif Any reason you closed these PRs?

[ovitrif]

@ovitrif Any reason you closed these PRs?

By mistake I reckon, sorry for that.

[pwltr]

Note: release automation for iOS artifacts is intentionally deferred. See the Phase 2 decision here: #22 (comment)

[ovitrif]

Approved because generated mobile artifacts are no longer tracked, iOS release outputs go to dist/ios, and Python binding entrypoints are removed.