@supacloud/cli 0.85.0 → 0.87.0

package/dist/shared/context.d.ts

@@ -21,6 +21,12 @@ export interface ResolvedContext {
     credentialScope: ContextCredentialScope;
     source: ContextSourceKind;
     sourcePath: string | null;
+    environmentVariables: Readonly<Record<string, string>>;
+    applicationId: string;
+    applicationEnvironmentId: string;
+    applicationConfigurationPath: string;
+    applicationConfigurationId: string;
+    applicationManifestPath: string;
     insecureTls: boolean;
 }
 export declare function resolveSupaCloudContext(env?: NodeJS.ProcessEnv, cwd?: string, selection?: ContextSelection): ResolvedContext;

package/dist/shared/tools/ai-tools.d.ts

@@ -1,5 +1,5 @@
 import { type ToolServer } from "../tool-server";
-declare const SKILL_NAME = "supacloud-cli";
+declare const SKILL_NAME = "supacloud";
 type InstallMode = "dry-run" | "write";
 type ConflictPolicy = "reject" | "replace";
 type InstallAction = "create" | "replace" | "none";

package/dist/shared/tools/application-schemas.d.ts

@@ -152,3 +152,37 @@ export declare const ApplicationPromotionPlanSchema: import("typebox").TObject<{
     execution_performed: import("typebox").TLiteral<false>;
     data_recovery: import("typebox").TLiteral<"separate-required">;
 }>;
+export declare const ApplicationReleaseRequestSchema: import("typebox").TObject<{
+    release_id: import("typebox").TString;
+    configuration_id: import("typebox").TOptional<import("typebox").TString>;
+    configuration_write: import("typebox").TOptional<import("typebox").TObject<{
+        configuration_id: import("typebox").TString;
+        expected_configuration_id: import("typebox").TUnion<[import("typebox").TString, import("typebox").TNull]>;
+        configuration: import("typebox").TObject<{
+            bun_version: import("typebox").TString;
+            targets: import("typebox").TArray<import("typebox").TObject<{
+                name: import("typebox").TString;
+                kind: import("typebox").TUnion<[import("typebox").TLiteral<"http">, import("typebox").TLiteral<"worker">]>;
+                hosts: import("typebox").TArray<import("typebox").TString>;
+                environment: import("typebox").TRecord<"^.*$", import("typebox").TString>;
+            }>>;
+        }>;
+    }>>;
+    activation_id: import("typebox").TOptional<import("typebox").TString>;
+    expected_activation_id: import("typebox").TOptional<import("typebox").TUnion<[import("typebox").TString, import("typebox").TNull]>>;
+    expected_plan_sha256: import("typebox").TOptional<import("typebox").TString>;
+}>;
+export declare const ApplicationReleaseResultSchema: import("typebox").TObject<{
+    schema: import("typebox").TLiteral<"supacloud.application-release.v1">;
+    project_ref: import("typebox").TString;
+    application_id: import("typebox").TString;
+    environment_id: import("typebox").TString;
+    release_id: import("typebox").TString;
+    configuration_id: import("typebox").TString;
+    activation_id: import("typebox").TString;
+    expected_activation_id: import("typebox").TUnion<[import("typebox").TString, import("typebox").TNull]>;
+    plan_sha256: import("typebox").TString;
+    action: import("typebox").TUnion<[import("typebox").TLiteral<"activate">, import("typebox").TLiteral<"no-op">]>;
+    replayed: import("typebox").TBoolean;
+    execution_performed: import("typebox").TBoolean;
+}>;

package/dist/shared/tools/application-tools.d.ts

@@ -9,7 +9,7 @@ export declare const APPLICATION_TOOL_SCHEMA: {
     ttl_seconds: Type.TOptional<Type.TInteger>;
     wait: Type.TOptional<Type.TBoolean>;
     timeout_seconds: Type.TOptional<Type.TInteger>;
-    action: Type.TEnum<("list_releases" | "get_release" | "upload_release" | "activate_release" | "logs" | "get_runtime" | "get_deployment_evidence" | "get_configuration" | "get_release_transfer_plan" | "get_promotion_plan" | "get_promotion_status" | "get_rollback_snapshot" | "get_history" | "get_deploy_plan" | "get_preview_plan" | "list_previews" | "get_preview" | "put_configuration" | "transfer_release" | "promote_application" | "reconcile_promotion" | "create_preview" | "reconcile_preview" | "cleanup_preview" | "deploy_release" | "rollback_release" | "reconcile_activation" | "retire_activation")[]>;
+    action: Type.TEnum<("list_releases" | "get_release" | "upload_release" | "activate_release" | "logs" | "get_runtime" | "get_deployment_evidence" | "get_configuration" | "get_release_transfer_plan" | "get_promotion_plan" | "get_promotion_status" | "get_rollback_snapshot" | "get_history" | "get_deploy_plan" | "get_preview_plan" | "list_previews" | "get_preview" | "put_configuration" | "release_application" | "transfer_release" | "promote_application" | "reconcile_promotion" | "create_preview" | "reconcile_preview" | "cleanup_preview" | "deploy_release" | "rollback_release" | "reconcile_activation" | "retire_activation")[]>;
     ref: Type.TString;
     id: Type.TString;
     environment_id: Type.TOptional<Type.TString>;
@@ -17,6 +17,7 @@ export declare const APPLICATION_TOOL_SCHEMA: {
     activation_id: Type.TOptional<Type.TString>;
     expected_activation_id: Type.TOptional<Type.TUnion<[Type.TString, Type.TNull, Type.TLiteral<"absent">]>>;
     configuration_path: Type.TOptional<Type.TString>;
+    configuration_write: Type.TOptional<Type.TUnknown>;
     manifest_path: Type.TOptional<Type.TString>;
     release_id: Type.TOptional<Type.TString>;
     source_ref: Type.TOptional<Type.TString>;

package/dist/shared/tools/deploy-tools.d.ts

@@ -5,6 +5,15 @@ interface DeployToolOptions {
     projectRef?: string;
     environment?: string | null;
     cwd?: string;
+    environmentVariables?: Readonly<Record<string, string>>;
+    application?: {
+        id: string;
+        environmentId: string;
+        configurationPath?: string;
+        configurationId?: string;
+        manifestPath?: string;
+    };
+    applicationRelease?: (args: Record<string, unknown>) => Promise<ToolResponse>;
     edgeFunctionDeploy?: (args: Record<string, unknown>) => Promise<ToolResponse>;
 }
 interface ToolResponse {
@@ -27,7 +36,12 @@ export declare const deployToolSchema: {
     diff: Type.TOptional<Type.TBoolean>;
     json: Type.TOptional<Type.TBoolean>;
 };
-export declare function findDeployConfigRoot(startDirectory: string): Promise<string>;
+export declare function findDeployConfigRoot(startDirectory: string, environmentName?: string): Promise<string>;
+export declare function createBuildEnvironment(names: string[] | undefined, environmentVariables: Readonly<Record<string, string>> | undefined): {
+    env: NodeJS.ProcessEnv;
+    names: string[];
+    missing: string[];
+};
 export declare function createFrontendArchive(outputDirectory: string): Promise<{
     archivePath: string;
     sha256: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supacloud/cli",
-  "version": "0.85.0",
+  "version": "0.87.0",
   "description": "Project-scoped CLI for SupaCloud users",
   "type": "module",
   "main": "./dist/index.js",
@@ -18,7 +18,7 @@
     }
   },
   "bin": {
-    "supacloud-cli": "dist/index.js"
+    "supacloud": "dist/index.js"
   },
   "files": [
     "NOTICE",
@@ -52,14 +52,14 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "@supacloud/compiler": "^0.43.0",
-    "@supacloud/delivery": "0.13.0",
+    "@supacloud/compiler": "^0.44.0",
+    "@supacloud/delivery": "0.14.0",
     "@supacloud/db": "0.16.0",
     "typebox": "1.3.34"
   },
   "overrides": {
     "@supacloud/contracts": "0.8.0",
-    "@supacloud/delivery": "0.13.0",
+    "@supacloud/delivery": "0.14.0",
     "@graphql-tools/utils": "^12.0.3"
   },
   "devDependencies": {

package/skills/{supacloud-cli → supacloud}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: supacloud-cli
-description: Use when operating, implementing, diagnosing, deploying, or documenting a SupaCloud project through supacloud-cli, especially project endpoint discovery, database schema, functions/RPC, triggers, RLS, indexes, grants, extensions, migrations, backups, auth, storage, Edge Functions, frontend, queues, task events, diagnostics, or gateway work. Also use when an AI might otherwise call SQL, psql, a database API, or the Management API directly.
+name: supacloud
+description: Use when operating, implementing, diagnosing, deploying, or documenting a SupaCloud project through supacloud, especially project endpoint discovery, database schema, functions/RPC, triggers, RLS, indexes, grants, extensions, migrations, backups, auth, storage, Edge Functions, frontend, queues, task events, diagnostics, or gateway work. Also use when an AI might otherwise call SQL, psql, a database API, or the Management API directly.
 ---
 
 # SupaCloud CLI
 
-Use `supacloud-cli` as the project-level control surface and keep durable changes reproducible from version-controlled files. Use `supacloud-admin` only for server/platform operations.
+Use `supacloud` as the project-level control surface and keep durable changes reproducible from version-controlled files. Use `supacloud-admin` only for server/platform operations.
 
 ## Non-negotiable rules
 
@@ -13,7 +13,7 @@ Use `supacloud-cli` as the project-level control surface and keep durable change
 
    ```bash
    git status --short --branch
-   supacloud-cli status
+   supacloud status
    ```
 
    A missing remote project context does not block local `migration_new`, `db_diff`, or `db_reset`; it blocks remote inspection/apply until context is supplied.
@@ -24,7 +24,7 @@ Use `supacloud-cli` as the project-level control surface and keep durable change
 5. Run a remote migration dry-run before apply. Production apply requires explicit user approval in the current task.
 6. Do not edit `supabase_migrations.schema_migrations` through ordinary SQL. Migration history is an application ledger, not a schema backup or source of truth. For a proven-equivalent historical baseline, use the controlled `database baseline_migrations` action with dry-run and explicit approval.
 7. Service-role credentials authenticate the SupaCloud Management API. Never reinterpret them as PostgreSQL passwords or forward them to the official Supabase CLI.
-8. Read project domains through `supacloud-cli project endpoints`. Do not infer API, Auth, or Studio origins by concatenating project refs and base domains. The projection reports configuration, not DNS/certificate/runtime readiness.
+8. Read project domains through `supacloud project endpoints`. Do not infer API, Auth, or Studio origins by concatenating project refs and base domains. The projection reports configuration, not DNS/certificate/runtime readiness.
 9. Cross-project enumeration is an Admin boundary. Use `supacloud-admin project list` or `supacloud-admin project list_endpoints`; do not attempt to widen project credentials.
 
 ## Workflow
@@ -34,8 +34,8 @@ Use `supacloud-cli` as the project-level control surface and keep durable change
 3. For AI-assisted database changes, first request bounded context:
 
    ```bash
-   supacloud-cli db context --module_file db/modules.ts --module <module>
-   supacloud-cli db context --module_file db/modules.ts --target <object>
+   supacloud db context --module_file db/modules.ts --module <module>
+   supacloud db context --module_file db/modules.ts --target <object>
    ```
 
    Use the returned source/test paths and ownership boundary; do not scan or
@@ -52,8 +52,8 @@ Use `supacloud-cli` as the project-level control surface and keep durable change
 For the selected project:
 
 ```bash
-supacloud-cli status
-supacloud-cli project endpoints
+supacloud status
+supacloud project endpoints
 ```
 
 The fixed projection contains credential-free API/Auth/Studio origins, hosts,
@@ -66,18 +66,18 @@ ready. Project-wide or fleet-wide inventories belong to `supacloud-admin`.
 For a new database change:
 
 ```bash
-supacloud-cli supabase migration_new --name add_accounts
+supacloud supabase migration_new --name add_accounts
 # Edit the generated SQL migration.
-supacloud-cli supabase db_reset --no_seed
-supacloud-cli supabase push --ref <project-ref> --dir supabase/migrations --dry_run
+supacloud supabase db_reset --no_seed
+supacloud supabase push --ref <project-ref> --dir supabase/migrations --dry_run
 # Apply only after explicit approval.
-supacloud-cli supabase push --ref <project-ref> --dir supabase/migrations
+supacloud supabase push --ref <project-ref> --dir supabase/migrations
 ```
 
 Use `db_diff` as an authoring aid, not as permission to bypass review:
 
 ```bash
-supacloud-cli supabase db_diff --schema public --name reconcile_public_schema
+supacloud supabase db_diff --schema public --name reconcile_public_schema
 ```
 
 For existing declarative SQL projects, `supabase db_schema_declarative_sync`
@@ -91,7 +91,7 @@ an existing Docker workflow. Lite drift pull writes drafts by default; only use
 For a database that was previously changed directly, stop further direct writes and follow the reconciliation workflow in [references/database-workflow.md](references/database-workflow.md). Do not push guessed historical migrations against a live database. After schema equivalence is proven, preview and record the baseline through:
 
 ```bash
-supacloud-cli database baseline_migrations \
+supacloud database baseline_migrations \
   --ref <project-ref> \
   --dir supabase/migrations \
   --dry_run
@@ -99,9 +99,9 @@ supacloud-cli database baseline_migrations \
 
 ## CLI boundaries
 
-- `supacloud-cli`: selected-project status and endpoint projection, database, migrations, auth, storage, Edge Functions, frontend, queues, task events, diagnostics, and project gateway configuration.
+- `supacloud`: selected-project status and endpoint projection, database, migrations, auth, storage, Edge Functions, frontend, queues, task events, diagnostics, and project gateway configuration.
 - `supacloud-admin`: installation, upgrades, SSH diagnostics, platform-wide project/endpoint inventory, project lifecycle, tenant runtime, and server operations.
-- Official `supabase` CLI: invoked only through the allowlisted `supacloud-cli supabase` adapter for supported local authoring or explicit-DSN inspection commands.
+- Official `supabase` CLI: invoked only through the allowlisted `supacloud supabase` adapter for supported local authoring or explicit-DSN inspection commands.
 - Direct HTTP/SQL: read-only diagnosis or an explicitly approved break-glass path; never the default implementation path.
 
 ## Completion evidence

package/skills/supacloud/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "SupaCloud CLI"
+  short_description: "安全使用 SupaCloud CLI 与数据库迁移"
+  default_prompt: "Use $supacloud to manage this SupaCloud project through migrations and safe CLI workflows."

package/skills/{supacloud-cli → supacloud}/references/command-map.md

@@ -6,8 +6,8 @@ Load this reference when selecting a command surface or when a user asks an AI t
 
 | Intent | Use | Guardrail |
 | --- | --- | --- |
-| Inspect current project binding | `supacloud-cli status` | Read-only; run first |
-| Inspect selected project API/Auth/Studio origins | `supacloud-cli project endpoints` | Uses the Management API's authoritative projection; do not reconstruct domains locally |
+| Inspect current project binding | `supacloud status` | Read-only; run first |
+| Inspect selected project API/Auth/Studio origins | `supacloud project endpoints` | Uses the Management API's authoritative projection; do not reconstruct domains locally |
 | Enumerate projects or endpoint projections | `supacloud-admin project list` / `project list_endpoints` | Platform-wide read; never promote a project credential to Admin authority |
 | Inspect project health/logs/tasks | `project`, `queue`, `task_events`, `diagnostics` | Prefer bounded reads |
 | Read database rows or metadata | `database query` and database inspection actions | `SELECT`/read-only by default |
@@ -57,11 +57,11 @@ until a project-scoped context is resolved.
 ## Safe inspection pattern
 
 ```bash
-supacloud-cli status
-supacloud-cli project get
-supacloud-cli project endpoints
-supacloud-cli project health
-supacloud-cli supabase migration_list --db_url "$SUPACLOUD_DB_URL"
+supacloud status
+supacloud project get
+supacloud project endpoints
+supacloud project health
+supacloud supabase migration_list --db_url "$SUPACLOUD_DB_URL"
 ```
 
 The endpoint projection returns bounded, credential-free API/Auth/Studio origins,

package/skills/{supacloud-cli → supacloud}/references/database-workflow.md

@@ -8,7 +8,7 @@ Migration files are the durable source of truth. `supabase_migrations.schema_mig
 2. Create a migration:
 
    ```bash
-   supacloud-cli supabase migration_new --name <intent>
+   supacloud supabase migration_new --name <intent>
    ```
 
 3. Put tables, views, functions/RPC, triggers, RLS, indexes, grants, extensions, and required reference data in the generated SQL file.
@@ -21,13 +21,13 @@ Migration files are the durable source of truth. `supabase_migrations.schema_mig
 5. Rebuild locally and run application tests:
 
    ```bash
-   supacloud-cli supabase db_reset --no_seed
+   supacloud supabase db_reset --no_seed
    ```
 
 6. Preview remote application:
 
    ```bash
-   supacloud-cli supabase push --ref <project-ref> --dir supabase/migrations --dry_run
+   supacloud supabase push --ref <project-ref> --dir supabase/migrations --dry_run
    ```
 
 7. After explicit environment approval, apply and read back migration history.
@@ -38,7 +38,7 @@ Preserve the repository's existing schema authority. In a project already using
 declarative SQL, edit those files and run:
 
 ```bash
-supacloud-cli supabase db_schema_declarative_sync --name <intent> --strict_coverage
+supacloud supabase db_schema_declarative_sync --name <intent> --strict_coverage
 ```
 
 The adapter defaults to no-apply. Review the generated migration, then use the
@@ -64,7 +64,7 @@ Do not fabricate old migration files and immediately push them. Reconcile delibe
 3. Create a schema-only backup before changing tracking or schema:
 
    ```bash
-   supacloud-cli supabase db_dump \
+   supacloud supabase db_dump \
      --db_url "$SUPACLOUD_DB_URL" \
      --file backups/pre-reconcile-schema.sql
    ```
@@ -72,7 +72,7 @@ Do not fabricate old migration files and immediately push them. Reconcile delibe
 4. In an isolated branch/worktree, pull the actual remote schema:
 
    ```bash
-   supacloud-cli supabase db_pull \
+   supacloud supabase db_pull \
      --db_url "$SUPACLOUD_DB_URL" \
      --declarative \
      --name remote_baseline
@@ -86,7 +86,7 @@ Do not fabricate old migration files and immediately push them. Reconcile delibe
 8. Only after equivalence is proven, preview the controlled baseline action:
 
    ```bash
-   supacloud-cli database baseline_migrations \
+   supacloud database baseline_migrations \
      --ref <project-ref> \
      --dir supabase/migrations \
      --dry_run

package/skills/supacloud-cli/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "SupaCloud CLI"
-  short_description: "安全使用 SupaCloud CLI 与数据库迁移"
-  default_prompt: "Use $supacloud-cli to manage this SupaCloud project through migrations and safe CLI workflows."