CyberGrid v0.8.0

CyberGrid v0.8.0 pairs static product policy, finite registration admission and explicit host remote-access gates with the matching Rust and browser SDKs. A host fixes its real Logto Native/SPA clients and canonical product; a finite-v2 deployment requires matching clients and a separate Redis prefix. Existing v0.7.0 assets remain unchanged.

The independent component versions are Rust SDK 0.3.0, JS/TypeScript SDK 0.2.0, Lab 0.4.0, Node server 0.2.0, and the first RAM-only workspace sample 0.1.0. The historical Go SDK/CLI remains 0.4.0 and does not gain finite admission, remote gates or browser bridge APIs. Use matched archives from this project release; version metadata alone is not runtime acceptance.

• Rust retains WebRTC → direct-only iroh → Quick Tunnel with inner mTLS, and adds explicit remote enable/disable, context-aware fresh-token requests, owned cancellation and finite-admission recovery. Local application services remain independent of remote access.
• The JS SDK remains a read-only console identity: it does not register Native devices, publish or acquire generic TCP access. It adds bounded directory/watch, fresh-token context, layered snapshots and gated business adapters. Unknown, changed identity/descriptor/policy, expiry and cancellation close the business gate. No business write is automatically replayed.
• Lab uses the matching Rust SDK and explicit remote controls; Android debug-test builds support the matching ADB protocol. Official platform Logto owners retain grant ownership. The separate RAM-only sample uses official in-memory owners and local/remote entry isolation; its default public build has no external Gateway/Noise adapter and reports unavailable for that path.
• CyberGrid-0.8.0-source.tar.gz and cybergrid-source-manifest.json preserve the complete reviewed public repository, including server/SDK relative dependencies, the desktop/Web sample, locks, public configuration example and notices. Component source packages remain available; standalone Rust archives do not contain repository Node/Redis integration prerequisites.
• The browser ESM package contains exactly index, bridge, directory and endpoints modules and types, package metadata, README and licenses. No private AnyWork adapter, AGPL implementation, cloud credentials or user data is bundled.
• The required repository workflow uses actual Redis, controlled OAuth/JWK and both native/browser module integrations. These fixtures are not real Logto Cloud login, public Noise/Quick Tunnel, phone-network or 30-minute/8-hour/24-hour acceptance. Those results remain separately gated by integration-010 and must be reported for the actual final release scope.
• Mac arm64 App/CLI and Android arm64 API28+ debug-test APK/CLI remain test artifacts. Mac is not notarized. CI Android signing is ephemeral: preserve existing authorization and signing ownership before handling a signature mismatch; do not uninstall a user's authorized app to force an upgrade.
• Full source/license manifests, provider pins, release-manifest.json and SHA256SUMS bind assets to the exact public snapshot commit and Actions run. Local unpublished history is not uploaded; the reviewed local freeze → exported tree → public commit mapping is retained separately.

This v0.8.0 release publishes CI-built macOS arm64 and Android arm64 debug-test installation packages from commit f2a3961. These packages are provided for testing; release publication and repository fixture CI do not declare production-client acceptance or completion of integration-010. Real dual-device Logto Cloud authorization, bidirectional Wi-Fi/4G WAN transport verification and the remaining 30-minute/8-hour/24-hour runtime acceptance are not completed by this release. Mac notarization is not provided; Android debug signing is ephemeral, so preserve existing authorization and signing ownership and do not uninstall an authorized app to bypass a signature mismatch.

Original CyberGrid code retains all rights reserved; no new SDK embedding or redistribution grant is implied. Third-party licenses and original notice bytes remain effective.

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.

CyberGrid v0.6.0

CyberGrid v0.6.0 replaces Lab's device-code sign-in with system-browser authorization code + PKCE. Deploy this coordinator and upgrade Lab together: the coordinator now accepts ordinary Logto Native applications with Device Flow disabled, so the Lab 0.2 and CLI device-code login from v0.5.1 cannot sign in to the new service.

The independently versioned components are Go SDK/CLI 0.4.0, Rust SDK 0.2.0, and CyberGrid Lab 0.3.0. Use the source archives in this project release for the updated SDK code; the historical sdk/v0.4.0 tag remains unchanged. 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.
• 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 and original license/notice texts; SHA256SUMS and release-manifest.json bind every asset to this Git commit and CI run.
• 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.

CyberGrid v0.5.1

CyberGrid project release. The independently versioned components are Go SDK/CLI 0.4.0, Rust SDK 0.2.0, and CyberGrid Lab 0.2.0.

• 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 and original license/notice texts; SHA256SUMS and release-manifest.json bind every asset to this Git commit and CI run.
• 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.