@supacloud/cli 0.75.1 → 0.77.0

package/README.md

@@ -2,9 +2,15 @@
 
 Project-scoped CLI for SupaCloud users.
 
-This package exposes only `supacloud-cli`. The bare `supacloud` name is reserved
+The only command-line executable is `supacloud-cli`. The bare `supacloud` name is reserved
 for the compiled server binary installed at `/usr/local/bin/supacloud`.
 
+Tool adapters import `@supacloud/cli/tool-runtime` for typed registration and
+schema decoding. This side-effect-free entrypoint does not initialize the CLI.
+Registration accepts unknown boundary input, decodes it before invoking the
+typed callback, and validates the callback's result. Private `src/shared` imports
+are not supported.
+
 ## Application Starter
 
 ```sh
@@ -231,6 +237,7 @@ actions and also exposes the immutable prebuilt release workflow:
 
 ```bash
 supacloud-cli frontend list_releases --ref abc123 --id web
+supacloud-cli frontend get_active_release --ref abc123 --id web
 supacloud-cli frontend get_release --ref abc123 --id web --release_id <sha256>
 supacloud-cli frontend upload_release --ref abc123 --id web --zip_path ./dist.zip
 supacloud-cli frontend activate_release --ref abc123 --id web \
@@ -238,6 +245,8 @@ supacloud-cli frontend activate_release --ref abc123 --id web \
   --expected_active_release_id absent \
   --expected_activation_id absent \
   --mutation_id <retry-stable-uuid-v4>
+supacloud-cli frontend rollback --ref abc123 --id web --release_id <retained-sha256>
+supacloud-cli frontend rollback --ref abc123 --id web
 ```
 
 `upload_release` hashes and streams an existing regular ZIP file without
@@ -245,10 +254,21 @@ buffering the full archive. The Management API binds the upload to that SHA-256,
 and the CLI reads the immutable release back before reporting success.
 `activate_release` uses both the observed active release and activation IDs as
 optimistic concurrency tokens, then verifies the authoritative active release.
-Use the values returned by `list_releases`; `absent` is valid only when no
-release has been activated. Production uploads and activations require the
+Use the values returned by `get_active_release`; `absent` is valid only when no
+release has been activated. Production uploads, activations and rollback require the
 normal exact `--confirm-production <ref>` value, and
-`SUPACLOUD_READ_ONLY=true` blocks both mutations.
+`SUPACLOUD_READ_ONLY=true` blocks all mutations.
+
+`get_active_release` automatically handles older servers returning HTTP 404
+with a one-record history page and exact active artifact readback. It never
+falls back for authentication, integrity or server failures.
+`rollback` without `--release_id` asks SupaCloud for a journal-verified previous
+immutable release, reads the current CAS identity and generates the mutation ID
+itself. An explicit `--release_id` remains available for a deliberate rollback
+to any retained release. It never infers a target from content-hash-sorted
+history, reuploads assets or restores a database.
+An uncertain result includes the mutation ID for read-only reconciliation and
+must not be blindly retried.
 
 ### Immutable application releases
 

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};