@supacloud/cli 0.107.1 → 0.108.1

package/dist/index.js

@@ -21603,7 +21603,7 @@ var starter_metadata_default = {
       version: "0.11.0"
     },
     contracts: {
-      version: "0.13.0"
+      version: "0.15.0"
     },
     db: {
       version: "0.20.0",
@@ -21949,7 +21949,7 @@ function baseFiles(name, sdkDependencies) {
         check: "bun run compile && bun run check:generated && bun run typecheck && bun run test",
         test: "bun run compile && bun --no-env-file scripts/environment.ts test bun test",
         dev: "bun --no-env-file scripts/environment.ts development bun scripts/dev.ts",
-        build: "bun run compile && bun run typecheck && bun build src/application.ts --target bun --minify --outdir dist",
+        build: "bun run compile && bun run typecheck && bun build src/application.ts --target bun --minify --outdir output/supacloud",
         "env:development": "bun --no-env-file scripts/environment.ts development",
         "env:test": "bun --no-env-file scripts/environment.ts test",
         "env:staging": "bun --no-env-file scripts/environment.ts staging",
@@ -21990,7 +21990,7 @@ function baseFiles(name, sdkDependencies) {
     }),
     "bunfig.toml": `env = false
 `,
-    ".gitignore": ["node_modules/", "dist/", ".env", ".env.*", "!.env.*.example", "!.env.test", ""].join(`
+    ".gitignore": ["node_modules/", "dist/", "output/supacloud/", ".env", ".env.*", "!.env.*.example", "!.env.test", ""].join(`
 `),
     ".env.development.example": `APP_ENV=development
 PORT=3000
@@ -22144,10 +22144,15 @@ do not widen them to \`unknown\` just to accept unvalidated data.
 ## Production Boundary
 
 \`bun run build\` emits an application factory, not a server. Import \`createApp\`
-from \`dist/application.js\` in your trusted host and supply real dependency,
+from \`output/supacloud/application.js\` in your trusted host and supply real dependency,
 request-context and command-governance adapters. The memory sandbox is
 development/test only.
 
+Keep backend bundles outside the frontend output directory. Vite normally cleans
+\`dist/\` before building; server artifacts placed there can be deleted or included
+in a public frontend archive. Use disjoint output directories, not a disabled
+frontend clean step. Compiler source artifacts remain in \`generated/\`.
+
 ## Inspection And Repair
 
 \`\`\`sh
@@ -22234,6 +22239,10 @@ sandbox. Bind persistence, authorization and audit to durable adapters before
 invoking it in production. Do not schedule destructive work without an
 idempotency key.
 
+\`bun run build\` emits \`output/supacloud/application.js\`, an application factory,
+not a deployed Worker. Keep it outside any frontend output directory such as
+\`dist/\`; frontend clean steps and public archives must not own server bundles.
+
 ## Inspection And Repair
 
 \`\`\`sh
@@ -22338,6 +22347,10 @@ explicit options; do not install every recipe into this application.
 ## Integration and delivery
 
 createApp requires application-owned trusted identity and durable adapters.
+\`bun run build\` emits \`output/supacloud/application.js\`, not a deployed server.
+Keep this backend directory separate from frontend output such as \`dist/\`,
+which frontend tools may clean and publish. Do not disable frontend cleanup to
+preserve backend artifacts; use disjoint output directories.
 Database migrations and seed data require an explicitly selected development
 database and a reviewed application script; the CLI never infers a production target.
 Commit generated/ after compilation. At release, check generated drift before
@@ -25096,7 +25109,7 @@ function appStarterFiles(name) {
         test: "bun run compile && bun --no-env-file scripts/environment.ts test bun test",
         dev: "bun --no-env-file scripts/environment.ts development bun scripts/dev.ts",
         "dev:integration": "bun --no-env-file scripts/environment.ts development bun scripts/integration.ts",
-        build: "bun run db:check && bun run compile && bun run typecheck && bun build src/application.ts --target bun --minify --outdir dist",
+        build: "bun run db:check && bun run compile && bun run typecheck && bun build src/application.ts --target bun --minify --outdir output/supacloud",
         "env:development": "bun --no-env-file scripts/environment.ts development",
         "env:test": "bun --no-env-file scripts/environment.ts test",
         "env:staging": "bun --no-env-file scripts/environment.ts staging",
@@ -25147,6 +25160,7 @@ function appStarterFiles(name) {
     ".gitignore": [
       "node_modules/",
       "dist/",
+      "output/supacloud/",
       "output/database-audit/",
       "db/migration-candidates/",
       ".env",
@@ -25737,16 +25751,21 @@ must also pin and validate the expected project and API origin.
 
 ## Production Boundary
 
-\`bun run build\` creates dist/application.js, an application factory, not a
+\`bun run build\` creates output/supacloud/application.js, an application factory, not a
 production server. The compiler is a devDependency and is absent from that
 runtime entry. The memory demo is kept in scripts/ and refuses staging/production.
 
-Import createApp from dist/application.js in your trusted host and supply:
+Import createApp from output/supacloud/application.js in your trusted host and supply:
 
 - deps.dbClient implementing ReviewStore, with reads/writes bound to a real transaction;
 - requestContext from verified identity, never a body-supplied actor;
 - commandGovernance authorization, durable idempotency, transaction and audit adapters.
 
+Keep backend bundles outside the frontend output directory. Vite normally cleans
+dist/ before building; server artifacts placed there can be deleted or included
+in a public frontend archive. Use disjoint output directories, not a disabled
+frontend clean step. Compiler source artifacts remain in generated/.
+
 The starter also includes src/host/review-postgres.ts and src/delivery-host.ts.
 The PostgreSQL adapter executes the same compiled approval handler with durable
 receipts, audit, current membership/ownership checks on replay and transaction-bound
@@ -25837,7 +25856,7 @@ startup before any request is served.
 ## Unified User Center
 
 For enterprise unified login, use SupAuth as the external user center. This
-starter exports createSupAuthApp(identity, adapters) from dist/application.js.
+starter exports createSupAuthApp(identity, adapters) from output/supacloud/application.js.
 Supply issuer, audience, clientId, projectId, an explicit HTTPS jwksUrl and resolveAccess
 that reads current application-local access. The runtime verifies credential
 signatures, configured issuer and audience, allowed asymmetric algorithms/keys
@@ -26373,6 +26392,38 @@ export const ${className}JobStatuses = new InjectionToken<${className}JobStatusP
 export const ${className}Refresher = new InjectionToken<${className}RefreshPort>(
     "${name}.refresher", { scope: "job" },
 );
+`,
+    [`${name}.client.ts`]: `import {
+    createFeatureSliceCommandClient,
+    type AuthoritativeCommandContract,
+    type AuthoritativeCommandTransport,
+    type FeatureSliceCommandClient,
+    type FeatureSliceCommandClientOptions,
+} from "@supacloud/contracts/client";
+import type { ${className}ApproveCommand } from "./${name}.model";
+import { ${className}ApproveInvalidateTags } from "./${name}.contracts";
+
+/**
+ * Browser/client boundary for the Feature transition.
+ *
+ * The transport must call the real generated API/RPC path. The framework owns
+ * pending identity, read-only recovery and explicit invalidation metadata;
+ * persistence, authorization and the receipt source remain application-owned.
+ */
+export type ${className}CommandTransport = AuthoritativeCommandTransport<${className}ApproveCommand>;
+export type ${className}CommandContract<Acknowledgement, Authority> =
+    AuthoritativeCommandContract<${className}ApproveCommand, Acknowledgement, Authority>;
+
+export function create${className}CommandClient<Acknowledgement, Authority>(
+    contract: ${className}CommandContract<Acknowledgement, Authority>,
+    transport: ${className}CommandTransport,
+    options: FeatureSliceCommandClientOptions<${className}ApproveCommand>,
+): FeatureSliceCommandClient<${className}ApproveCommand, Authority> {
+    return createFeatureSliceCommandClient(contract, transport, {
+        ...options,
+        invalidateTags: options.invalidateTags ?? ${className}ApproveInvalidateTags,
+    });
+}
 `,
     [`${name}.service.ts`]: `import {
     FeatureAdapterError, Inject, Injectable, Optional, REQUEST_CONTEXT, requireFeatureOperationResult,
@@ -33054,7 +33105,7 @@ async function runProjectDeployment(http, args) {
 // package.json
 var package_default = {
   name: "@supacloud/cli",
-  version: "0.107.1",
+  version: "0.108.1",
   description: "Project-scoped CLI for SupaCloud users",
   type: "module",
   main: "./dist/index.js",
@@ -33112,7 +33163,7 @@ var package_default = {
     typebox: "1.3.37"
   },
   overrides: {
-    "@supacloud/contracts": "0.13.0",
+    "@supacloud/contracts": "0.15.0",
     "@supacloud/delivery": "0.21.0",
     "@graphql-tools/utils": "^12.0.4"
   },

package/dist/shared/tools/app-starter-output.test.d.ts

@@ -0,0 +1 @@
+export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supacloud/cli",
-  "version": "0.107.1",
+  "version": "0.108.1",
   "description": "Project-scoped CLI for SupaCloud users",
   "type": "module",
   "main": "./dist/index.js",
@@ -58,7 +58,7 @@
     "typebox": "1.3.37"
   },
   "overrides": {
-    "@supacloud/contracts": "0.13.0",
+    "@supacloud/contracts": "0.15.0",
     "@supacloud/delivery": "0.21.0",
     "@graphql-tools/utils": "^12.0.4"
   },