LYNX SDK — language bindings (shims)

Idiomatic bindings for the LYNX SDK: Python, Swift, Kotlin, Java (JVM), Node, React Native. These are thin marshalling layers over the LYNX C core — all recognition logic lives in the core; the bindings only marshal calls and results.

The C core lives in a separate repo: Syneticai/LYNX-SDK. It builds + obfuscates the core, runs the harness, and publishes the obfuscated C SDK (lynx.h + per-platform libs) as a GitHub Release (build.yml → s8_publish_core). This repo consumes that Release artifact to build the wrappers/wheels.

Layout

• lynx/ — the Python package (_api.py, cli.py, …) + per-language bindings (python/, swift/, kotlin/, jvm/, node/, react-native/).
• setup.py / pyproject.toml — Python wheel build.
• Package.swift — Swift package.
• .github/workflows/ — mobile/android/perf/qa workflows.
• .github/build-stages.yml.saved — the wrap/wheel/verify/publish JOBS lifted from the C repo's build.yml; these become this repo's primary build (rewire their needs: to download the C SDK Release instead of building the core in-tree).

Status — pending wiring

Initial snapshot, split from the C repo. Not yet buildable standalone: setup.py still expects lynx/core (source or LYNX_PREBUILT_CORE). The migration step is to point the build at the published C SDK artifact:

1. C repo s8_publish_core publishes lynx.h + libs as a versioned Release.
2. Here: build downloads + unpacks that Release, sets LYNX_PREBUILT_CORE (and the include path to the shipped lynx.h), then builds the wheels/wraps.
3. Turn build-stages.yml.saved into .github/workflows/build.yml, rewired to (1).