CyberGrid v0.7.0

CyberGrid v0.7.0 makes Rust the primary SDK and adds WebRTC → direct iroh → Cloudflare Quick Tunnel connections. WebRTC and iroh can also run in parallel: the first connection to complete endpoint authentication wins, the other attempt is cleaned up, and Quick Tunnel is used only after both direct paths fail. Deploy the matching coordinator and clients together. These changes are not in the existing v0.6.0 downloads.

The independently versioned components are Go SDK/CLI 0.4.0, Rust SDK 0.2.0, CyberGrid Lab 0.3.0, and the new JS/TypeScript SDK 0.1.0. Use the archives attached to this project release for the matching source and binaries; existing releases and the historical sdk/v0.4.0 tag remain unchanged. Go remains compatible with the existing two-stage transport. The CLI and Rust CLI example retain legacy Device Flow entry points for source compatibility, but do not implement first-time browser login against this coordinator. Use Lab or integrate an official Logto SDK in your host application.

• Lab uses system-browser sign-in with Device Flow disabled: official Logto Android SDK on Android and JavaScript SDK in the desktop Tauri frontend. Public test server and Native application settings are preset; account credentials are not bundled.
• Existing local authorization now has an explicit restore/revoke message instead of a generic browser-login failure and stale setup status.
• iroh relays and default address lookup are disabled. All SDK transports retain inner mTLS and current same-user/application device authentication. Direct connectivity across arbitrary NATs is not guaranteed. Lab exposes the parallel policy and the force-tunnel test policy.
• Native hosts can advertise, update or withdraw a business port's own Quick Tunnel URL. The read-only JS SDK integrates with the host's official Logto JS/React login to query devices and those declared URLs. It does not register devices, create transports or proxy business requests. Cross-origin frontends require an exact CYBERGRID_BROWSER_ORIGINS allowlist.
• Both platforms hand off the grant to the Rust credential owner for later refresh, resume, and revocation. Android ADB control adds web-login; login is an alias for the same browser flow. Public connection arguments are optional. Applications are managed only in Logto; their actual, case-sensitive Native client ID remains the application isolation boundary.
• Native macOS arm64 CLI and Tauri test app; Android arm64 API28+ CLI and debug-test APK with the explicit ADB control feature.
• Fixed, offline cloudflared resources. macOS uses the SDK-bundled provider; Android uses one OS-installed native-library resource. No runtime provider download.
• Source archives, built JS ESM/types, and dependency license/notice texts with pinned provenance; SHA256SUMS and release-manifest.json bind every asset to this Git commit and CI run. The notices explicitly document the standard Apache-2.0 text selected for enum-assoc, whose exact upstream source declares that license alternative but omits its text.
• The macOS app is not notarized. The APK uses an ephemeral CI debug signing key; an app signed with another key cannot be upgraded in place. Preserve or revoke existing credentials through their original app before choosing an uninstall/reinstall.
• These jobs perform real packaging builds. They do not rerun WAN/device/OAuth acceptance tests or claim additional runtime validation.

Original CyberGrid code retains all rights reserved. Publishing source does not grant an additional open-source license. Third-party licenses remain separately effective; full texts accompany the artifacts.