@supacloud/cli 0.114.0 → 0.115.0

package/dist/shared/cli.test.d.ts

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

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

@@ -23,6 +23,14 @@ export interface SkillInstallSummary {
 }
 export declare function installSkill(request: InstallSkillRequest): SkillInstallSummary;
 export declare function resolveDefaultCodexSkillRoot(environment?: NodeJS.ProcessEnv, homeDirectory?: string): string;
+/** Stable aliases for common Agent Skill roots; any other value remains an explicit path. */
+export declare const SKILL_TARGET_ALIASES: readonly ["codex", "claude", "agents", "project"];
+export type SkillTargetAlias = typeof SKILL_TARGET_ALIASES[number];
+export declare function resolveSkillTargetRoot(target: string | undefined, options?: {
+    environment?: NodeJS.ProcessEnv;
+    homeDirectory?: string;
+    workingDirectory?: string;
+}): string;
 export declare function resolveBundledSkillDirectory(moduleUrl?: string): string;
 export declare function registerAiTools(server: ToolServer): void;
 export {};

package/dist/shared/tools/app-starter-database.d.ts

@@ -12,5 +12,5 @@ export declare const STARTER_DATABASE_CONFIG: {
 export declare const STARTER_DATABASE_SCHEMA = "import { sql } from \"drizzle-orm\";\nimport { boolean, check, integer, jsonb, pgTable, primaryKey, text, unique, uuid } from \"drizzle-orm/pg-core\";\n\n// Structure for the reviewed starter migrations. Grants/policies stay in those migrations.\nexport const application = pgTable.withRLS(\"starter_application\", {\n  singleton: boolean().default(true).primaryKey(),\n  projectId: text(\"project_id\").notNull(),\n  tenantId: text(\"tenant_id\").notNull(),\n}, table => [\n  check(\"starter_application_singleton_check\", sql`${table.singleton}`),\n  check(\"starter_application_project_id_check\", sql`length(${table.projectId}) > 0`),\n  check(\"starter_application_tenant_id_check\", sql`length(${table.tenantId}) > 0`),\n]);\n\nexport const reviews = pgTable.withRLS(\"starter_reviews\", {\n  id: text().primaryKey(),\n  ownerId: text(\"owner_id\").notNull(),\n  state: text({ enum: [\"draft\", \"approved\"] }).notNull(),\n  version: integer().notNull(),\n}, table => [\n  check(\"starter_reviews_state_check\", sql`${table.state} IN ('draft', 'approved')`),\n  check(\"starter_reviews_version_check\", sql`${table.version} > 0`),\n]);\n\nexport const members = pgTable.withRLS(\"starter_members\", {\n  subject: text().primaryKey(),\n  enabled: boolean().default(true).notNull(),\n  canApprove: boolean(\"can_approve\").default(false).notNull(),\n  storageSubject: uuid(\"storage_subject\").unique(),\n});\n\nexport const attachments = pgTable.withRLS(\"starter_attachments\", {\n  reviewId: text(\"review_id\").primaryKey().references(() => reviews.id),\n  artifactId: uuid(\"artifact_id\").notNull().unique(),\n  ownerId: text(\"owner_id\").notNull(),\n  runId: uuid(\"run_id\").notNull().unique(),\n  objectPath: text(\"object_path\").notNull().unique(),\n});\n\nexport const attachmentResults = pgTable.withRLS(\"starter_attachment_results\", {\n  reviewId: text(\"review_id\").notNull().references(() => reviews.id),\n  version: integer().notNull(),\n  artifactId: uuid(\"artifact_id\").notNull(),\n  result: jsonb().$type<unknown>().notNull(),\n}, table => [\n  primaryKey({ columns: [table.reviewId, table.version, table.artifactId] }),\n  check(\"starter_attachment_results_version_check\", sql`${table.version} >= 2`),\n]);\n\nexport const attachmentRetries = pgTable.withRLS(\"starter_attachment_retries\", {\n  runId: uuid(\"run_id\").primaryKey(),\n  reviewId: text(\"review_id\").notNull().references(() => attachments.reviewId),\n  previousRunId: uuid(\"previous_run_id\").notNull().unique(),\n  generation: integer().notNull(),\n}, table => [\n  unique(\"starter_attachment_retries_review_id_generation_key\").on(table.reviewId, table.generation),\n  check(\"starter_attachment_retries_generation_check\", sql`${table.generation} > 0`),\n  check(\"starter_attachment_retries_check\", sql`${table.runId} <> ${table.previousRunId}`),\n]);\n\nexport type ReviewRow = typeof reviews.$inferSelect;\nexport type NewReview = typeof reviews.$inferInsert;\n";
 export declare const STARTER_DATABASE_MODULES = "import { defineDatabaseModule } from \"@supacloud/db\";\nimport { getTableConfig } from \"drizzle-orm/pg-core\";\nimport { application, reviews, members, attachments, attachmentResults, attachmentRetries } from \"./schema\";\n\nconst backendPolicies = [\n  [\"starter_backend_binding_read\", \"public.starter_application\", \"select\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_binding_lock\", \"public.starter_application\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_binding_immutable\", \"public.starter_application\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_member_read\", \"public.starter_members\", \"select\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_member_lock\", \"public.starter_members\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_member_immutable\", \"public.starter_members\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_review_read\", \"public.starter_reviews\", \"select\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_review_update\", \"public.starter_reviews\", \"update\", [\"starter_review_http\"]],\n  [\"starter_worker_review_immutable\", \"public.starter_reviews\", \"update\", [\"starter_review_worker\"]],\n  [\"starter_backend_attachment_read\", \"public.starter_attachments\", \"select\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_attachment_lock\", \"public.starter_attachments\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_backend_attachment_immutable\", \"public.starter_attachments\", \"update\", [\"starter_review_http\", \"starter_review_worker\"]],\n  [\"starter_http_attachment_insert\", \"public.starter_attachments\", \"insert\", [\"starter_review_http\"]],\n  [\"starter_worker_result_read\", \"public.starter_attachment_results\", \"select\", [\"starter_review_worker\"]],\n  [\"starter_worker_result_insert\", \"public.starter_attachment_results\", \"insert\", [\"starter_review_worker\"]],\n] as const;\n\n// The module is the single live-Catalog ownership contract for starter tables.\nexport default defineDatabaseModule({\n  name: \"starter\",\n  tables: [application, reviews, members, attachments, attachmentResults, attachmentRetries].map(table => {\n    const config = getTableConfig(table);\n    return (config.schema ?? \"public\") + \".\" + config.name;\n  }),\n  policies: [\n    ...([\n      [\"starter_http_retry_read\", \"select\", \"starter_review_http\"],\n      [\"starter_http_retry_insert\", \"insert\", \"starter_review_http\"],\n      [\"starter_worker_retry_read\", \"select\", \"starter_review_worker\"],\n    ] as const).map(([name, operation, role]) => ({\n      name, table: \"public.starter_attachment_retries\", operation, roles: [role],\n      source: \"migrations/005-review-task-recovery.sql\", tests: [\"tests/database-governance.sql\"],\n    })),\n    ...backendPolicies.map(([name, table, operation, roles]) => ({\n      name, table, operation, roles: [...roles], source: \"migrations/004-review-runtime-roles.sql\",\n      tests: [\"tests/database-governance.sql\"],\n    })),\n    {\n      name: \"starter_member_read\", table: \"public.starter_members\", operation: \"select\",\n      roles: [\"authenticated\"], source: \"migrations/003-review-uploads.sql\",\n      tests: [\"tests/database-governance.sql\"],\n    },\n    {\n      name: \"starter_review_read\", table: \"public.starter_reviews\", operation: \"select\",\n      roles: [\"authenticated\"], source: \"migrations/003-review-uploads.sql\",\n      tests: [\"tests/database-governance.sql\"],\n    },\n  ],\n});\n";
 export declare const STARTER_DATABASE_TEST = "-- Read-only catalog assertions; behavioral authorization tests remain separate.\nBEGIN READ ONLY;\nDO $test$\nDECLARE\n  owned text[] := ARRAY['starter_application','starter_reviews','starter_members',\n    'starter_attachments','starter_attachment_results','starter_attachment_retries'];\nBEGIN\n  IF (SELECT count(*) FROM pg_class c JOIN pg_namespace n ON n.oid=c.relnamespace\n      WHERE n.nspname='public' AND c.relname=ANY(owned) AND c.relrowsecurity) <> 6 THEN\n    RAISE EXCEPTION 'All starter tables must exist with RLS enabled';\n  END IF;\n  IF (SELECT count(*) FROM pg_policy p JOIN pg_class c ON c.oid=p.polrelid\n      JOIN pg_namespace n ON n.oid=c.relnamespace\n      WHERE n.nspname='public' AND c.relname=ANY(owned)) <> 20 THEN\n    RAISE EXCEPTION 'Starter policy inventory changed; reconcile db/modules.ts';\n  END IF;\n  IF EXISTS (SELECT 1 FROM pg_roles WHERE rolname IN ('starter_review_http','starter_review_worker')\n      AND (rolsuper OR rolbypassrls)) THEN\n    RAISE EXCEPTION 'Starter roles must not bypass row security';\n  END IF;\n  IF (SELECT count(*) FROM pg_roles WHERE rolname IN ('starter_review_http','starter_review_worker')) <> 2 THEN\n    RAISE EXCEPTION 'Starter runtime roles are missing';\n  END IF;\nEND\n$test$;\nROLLBACK;\n";
-export declare const STARTER_DATABASE_GUIDE = "\n## Database Source Workflow\n\nDrizzle owns table declarations and inferred row types in db/schema.ts.\nUse the existing @supacloud/db/drizzle-bun adapters for typed queries and governed\ntransactions; never replace permission, idempotency or audit checks with plain CRUD.\nOpaque JSON still needs runtime decoding.\n\nAfter installing dependencies, run `bun run db:generate` once and commit db/contracts/.\nThe default `bun run check` and build fail on stale database contracts before any\ncompiler regeneration. After an intentional source change, run db:generate again,\nreview the diff, then run check.\nThe command starter registers databaseGovernance.moduleFile = \"db/modules.ts\" and\nkeeps the default `databaseGovernance.mode = \"check\"`: compile/check/build run\nthe offline source-contract gate without a database. Use `bun run dev:integration`\nwith the CLI's explicit loopback database URL, or set databaseGovernance.mode to\n\"enforce\" with an explicitly supplied `DATABASE_URL`, to run SQL lint and live\nCatalog reconciliation. Missing connections, stale source contracts and Catalog\ndrift fail closed; no contracts or migrations are silently regenerated.\n\n- Maintain one schema-qualified function with explicit grants per db/functions/*.sql.\n- Preserve migrations/ and its existing executor/ledger. Add forward migrations only.\n- `bun run db:diff` generates Drizzle drafts under db/migration-candidates/, never\n  into the deployment directory. The starter has existing SQL history, so establish\n  and review a matching Drizzle baseline before promoting any draft; the first\n  draft is not automatically an incremental production migration.\n- `bun run db:pull` requires an explicitly selected DATABASE_URL and writes only\n  output/database-audit/drizzle-candidate/. Review candidates; never overwrite source blindly.\n- Full SQL dumps belong under the ignored output/database-audit/ directory. They are\n  audit/recovery artifacts, never ordinary type, application or test inputs.\n- `bun run db:assess` explains adoption/findings without writing or connecting.\n- GraphQL/PostgREST exports remain legitimate protocol contracts. This check is not\n  proof of deployed schema, effective role permissions or complete RLS equivalence.\n\nDo not introduce any/@ts-ignore to bypass a contract. Use Drizzle-inferred types,\npreserve bigint/numeric precision and decode unknown results at the boundary.\n";
+export declare const STARTER_DATABASE_GUIDE = "\n## Database Source Workflow\n\nDrizzle owns table declarations and inferred row types in db/schema.ts.\nUse the existing @supacloud/db/drizzle-bun adapters for typed queries and governed\ntransactions; never replace permission, idempotency or audit checks with plain CRUD.\nOpaque JSON still needs runtime decoding.\n\nAfter installing dependencies, run `bun run db:generate` once and commit db/contracts/.\nThe default `bun run check` and build fail on stale database contracts before any\ncompiler regeneration. After an intentional source change, run db:generate again,\nreview the diff, then run check.\nThe command starter uses the default database governance module path\n`db/modules.ts` and fixes `databaseGovernance.mode = \"check\"`: compile/check/build\nrun the offline source-contract gate without a database. Use `bun run dev:integration`\nwith the CLI's explicit loopback database URL, or set databaseGovernance.mode to\n\"enforce\" with an explicitly supplied `DATABASE_URL`, to run SQL lint and live\nCatalog reconciliation. Missing connections, stale source contracts and Catalog\ndrift fail closed; no contracts or migrations are silently regenerated.\n\n- Maintain one schema-qualified function with explicit grants per db/functions/*.sql.\n- Preserve migrations/ and its existing executor/ledger. Add forward migrations only.\n- `bun run db:diff` generates Drizzle drafts under db/migration-candidates/, never\n  into the deployment directory. The starter has existing SQL history, so establish\n  and review a matching Drizzle baseline before promoting any draft; the first\n  draft is not automatically an incremental production migration.\n- `bun run db:pull` requires an explicitly selected DATABASE_URL and writes only\n  output/database-audit/drizzle-candidate/. Review candidates; never overwrite source blindly.\n- Full SQL dumps belong under the ignored output/database-audit/ directory. They are\n  audit/recovery artifacts, never ordinary type, application or test inputs.\n- `bun run db:assess` explains adoption/findings without writing or connecting.\n- GraphQL/PostgREST exports remain legitimate protocol contracts. This check is not\n  proof of deployed schema, effective role permissions or complete RLS equivalence.\n\nDo not introduce any/@ts-ignore to bypass a contract. Use Drizzle-inferred types,\npreserve bigint/numeric precision and decode unknown results at the boundary.\n";
 export declare function starterDatabaseFiles(): Record<string, string>;

package/dist/shared/tools/app-starter-reactive.d.ts

@@ -1,4 +1,4 @@
 /** Shared reactive conventions for command, HTTP and edge starters. */
 export declare const STARTER_REACTIVE_GUIDE = "# Reactive development / \u54CD\u5E94\u5F0F\u5F00\u53D1\n\nRxJS is the default and only reactive event library in the starter ecosystem.\nOrdinary queries and business commands still use async/await. Use RxJS for\nongoing events and timing/composition, not as a new\ntransaction, retry or durable-delivery system.\n\nHost defaults:\n- In a native Angular host, use signal/resource APIs from @supacloud/app/angular\n  and Angular's scheduler. Do not mix them with the legacy root signal graph.\n- In framework-neutral code, use async/await for one result and RxJS for event\n  composition. Raw continuous protocols use AsyncIterable unless an existing\n  RxJS/Angular boundary is the better fit. The host owns cancellation through\n  an explicit signal.\n\n- Import native operators from rxjs; do not invent another event/operator library.\n- Import takeUntilAborted / toReadableStream from @supacloud/app/reactive.\n- Every subscription belongs to a request, connection, task or application owner.\n  Bind the owner's AbortSignal before starting work; release it on exit.\n- toReadableStream has a bounded item buffer and fails on overflow. It is not\n  an event journal. Do not silently drop durable business events or audit records.\n- Never wrap command submission in defer/retry/repeat or submit from subscribe.\n  Await the existing governed command and then observe its existing receipt.\n- Do not shareReplay authenticated values globally across projects or sessions.\n- subscribe(async ...) does not await processing. Keep acknowledged task-output\n  consumers on the SDK's for-await watch path; do not advance onCursor via next().\n\n## SupaCloud JS\n\nThe platform SDK is @supacloud/js, not a replacement Supabase client. Keep the\nclient from createSupaCloudClient. Database/Auth/Storage calls use client.supabase;\nplatform commands/tasks use the existing client.commands / client.tasks APIs.\nFor applications using this SDK, import observeQuery and observeTask from\n@supacloud/js/reactive. Pass the request signal to the native query builder:\n\n    observeQuery(signal => client.supabase.from(\"widgets\").select(\"id\").abortSignal(signal), { signal: owner.signal })\n\nThe query result keeps data/error/count/status; non-null errors enter error().\nThe query factory runs once per subscriber. This is intended for reads, not\nreplaying writes. A PromiseLike is supported; an already-started Promise is not\nan appropriate factory. Unsubscribe aborts cooperative I/O, not committed work.\n\nSubmit a background task ONCE with the existing SDK, then observe the receipt:\n\n    const task = await client.functions.invokeBackground(\"render\", { body: input });\n    const progress = observeTask(task, { signal: owner.signal });\n\nUnsubscribing progress does not cancel the server task. Task read/decoder errors\nterminate observation; there is no automatic business retry. Realtime-to-polling\nfallback and project validation remain the SDK's responsibilities. Do not invent\na public.tasks table or copy service credentials into browser code.\n\nRun bun run check. Add cancellation, error, overflow and cross-owner isolation\ncoverage whenever adding streaming behavior. These APIs require the matching\nframework/SDK release or the packed candidate packages used by repository CI.\n";
-export declare const STARTER_REACTIVE_AGENTS = "# Application development rules\n\nRead README.md and REACTIVE.md before adding asynchronous features. If the\napplication is hosted by Angular, read the @supacloud/app/angular guidance\nbefore choosing a signal API.\nPrefer the generated contracts and existing project-bound @supacloud/js client.\nUse async/await for a single result; RxJS is the default event-composition\nlibrary. Do not introduce another reactive library without a documented special\nrequirement and equivalent lifecycle tests.\nBind subscriptions to an explicit owner and propagate cancellation to native I/O.\nNever automatically retry a write or turn observable delivery into durable ack.\nDo not bypass authorization, transactions, idempotency or audit to simplify code.\nRun bun run check; include negative and cleanup tests. Never store live credentials.\n";
+export declare const STARTER_REACTIVE_AGENTS = "# Application development rules\n\nRead README.md and REACTIVE.md before adding asynchronous features. If the\napplication is hosted by Angular, read the @supacloud/app/angular guidance\nbefore choosing a signal API.\nPrefer the generated contracts and existing project-bound @supacloud/js client.\nUse async/await for a single result; RxJS is the default event-composition\nlibrary. Do not introduce another reactive library without a documented special\nrequirement and equivalent lifecycle tests.\nBind subscriptions to an explicit owner and propagate cancellation to native I/O.\nNever automatically retry a write or turn observable delivery into durable ack.\nDo not bypass authorization, transactions, idempotency or audit to simplify code.\nStart with `supacloud app context --format json` and `supacloud app doctor --format json`;\ndo not scan the whole repository first or treat generated/ as source. Apply only\nreviewed diagnostic fixes with `supacloud app fix --fix <file>`, then re-run check\nand doctor. Never weaken compiler governance to hide a diagnostic.\nRun bun run check; include negative and cleanup tests. Never store live credentials.\n";
 export declare const STARTER_REACTIVE_TEST = "import { expect, test } from \"bun:test\";\nimport { Observable } from \"rxjs\";\nimport { takeUntilAborted, toReadableStream } from \"@supacloud/app/reactive\";\n\ntest(\"the owner's signal releases reactive work exactly once\", () => {\n  const owner = new AbortController();\n  let starts = 0, stops = 0;\n  const source = new Observable<number>(() => { starts++; return () => { stops++; }; });\n  source.pipe(takeUntilAborted(owner.signal)).subscribe();\n  owner.abort();\n  source.pipe(takeUntilAborted(owner.signal)).subscribe();\n  expect(starts).toBe(1);\n  expect(stops).toBe(1);\n});\n\ntest(\"cancelled stream consumers release their subscription\", async () => {\n  let stops = 0;\n  const source = new Observable<number>(() => () => { stops++; });\n  const stream = toReadableStream(source);\n  await stream.cancel();\n  expect(stops).toBe(1);\n});\n";

package/dist/shared/tools/app-starter-templates.d.ts

@@ -1,7 +1,7 @@
-export type StarterTemplate = "minimal" | "http" | "command" | "edge";
+export type StarterTemplate = "minimal" | "command";
 export interface StarterSdkDependencies {
     "@supacloud/js": string;
     "@supabase/supabase-js": string;
 }
-/** Explicit recipes retain their existing layouts; new projects default to minimal. */
-export declare function appTemplateFiles(name: string, template: StarterTemplate, sdkDependencies?: StarterSdkDependencies): Record<string, string>;
+/** New projects use the minimal layout; the command recipe is emitted separately. */
+export declare function appTemplateFiles(name: string, template: "minimal", sdkDependencies: StarterSdkDependencies): Record<string, string>;

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

@@ -67,33 +67,28 @@ export interface AppToolArguments {
     wait?: boolean;
     timeout_seconds?: number;
     kind?: "module" | "command" | "query" | "controller" | "job" | "contract" | "resource" | "feature";
-    template?: "minimal" | "http" | "command" | "edge";
+    template?: "minimal" | "command";
     name?: string;
     module?: string;
     permission?: string;
     read_permission?: string;
-    "read-permission"?: string;
     rpc?: string;
     database_source?: string;
     database_table?: string;
     database_type?: string;
-    "database-source"?: string;
-    "database-table"?: string;
-    "database-type"?: string;
     dir?: string;
     force?: boolean;
     dry_run?: boolean;
     register_in?: string;
-    "dry-run"?: boolean;
-    "register-in"?: string;
     root?: string;
     include?: string;
     out_dir?: string;
     strict?: boolean;
     format?: "text" | "json";
-    json?: boolean;
     target?: string;
     fix?: string;
+    from_doctor?: string;
+    fix_index?: number;
     write?: boolean;
     /** `app dev` local profile. `fast` is local/ephemeral; `integration` requires an explicit database URL. */
     profile?: "fast" | "integration";
@@ -103,7 +98,6 @@ export interface AppToolArguments {
     watch?: boolean;
     /** Integration dev verifies an explicit loopback database before running dev:integration. */
     database_url?: string;
-    "database-url"?: string;
     offset?: number;
     service?: string;
     search?: string;
@@ -113,7 +107,6 @@ export interface AppToolArguments {
     events?: string;
     /** `app context`: exact opaque request ID to correlate from events. */
     request_id?: string;
-    "request-id"?: string;
 }
 export interface ToolResult {
     isError?: boolean;
@@ -131,12 +124,6 @@ declare function formatGraphText(manifest: AppManifest): string;
 declare function reverseDependencies(manifest: AppManifest, token: string): string[];
 export declare function runAppTool(request: AppToolArguments, options?: AppToolOptions): Promise<ToolResult>;
 export declare function registerAppTools(server: ToolServer, options?: AppToolOptions): void;
-/**
- * Promotes the single-entry development verbs to top-level commands so an AI or
- * developer does not need to remember the `app` namespace. The `app` tool and
- * these aliases share one implementation and one execution-policy classification.
- */
-export declare function registerAppAliases(server: ToolServer): void;
 export declare const __internal: {
     pascalName: typeof pascalName;
     camelName: typeof camelName;

package/dist/shared/tools/db-governance-tools.d.ts

@@ -10,6 +10,7 @@ export interface DbToolArguments {
     database_url?: string;
     schema?: string;
     lite?: boolean;
+    remote?: boolean;
     project_dir?: string;
     schema_dir?: string;
     db_major_version?: number;

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

@@ -23,13 +23,15 @@ interface ToolResponse {
     isError?: boolean;
 }
 export declare const deployToolSchema: {
+    action: Type.TOptional<Type.TEnum<"init"[]>>;
+    root: Type.TOptional<Type.TString>;
     ref: Type.TOptional<Type.TString>;
     cwd: Type.TOptional<Type.TString>;
     skip_build: Type.TOptional<Type.TBoolean>;
     assets_only: Type.TOptional<Type.TBoolean>;
     backend: Type.TOptional<Type.TBoolean>;
     status: Type.TOptional<Type.TString>;
-    json: Type.TOptional<Type.TBoolean>;
+    format: Type.TOptional<Type.TEnum<("json" | "text")[]>>;
 };
 export declare function findDeployConfigRoot(startDirectory: string, environmentName?: string): Promise<string>;
 export declare function createBuildEnvironment(names: string[] | undefined, environmentVariables: Readonly<Record<string, string>> | undefined): {

package/dist/shared/tools/developer-experience-tools.d.ts

@@ -1,6 +1,10 @@
 import { type ResolvedContext } from "../context";
 import type { ToolSchema } from "../schema";
-import { type ToolServer } from "../tool-server";
+import { type ToolResult, type ToolServer } from "../tool-server";
+export interface InitRequest {
+    root?: string;
+    format?: "text" | "json";
+}
 export interface DeveloperExperienceOptions {
     cwd?: string;
     activeContext?: ResolvedContext;
@@ -13,6 +17,7 @@ interface PackageManifest {
 export declare const initToolSchema: ToolSchema;
 export declare const environmentToolSchema: ToolSchema;
 declare function outputDirectoryFor(manifest: PackageManifest): string;
+export declare function initializeProject(request: InitRequest, options?: DeveloperExperienceOptions): Promise<ToolResult>;
 declare function profileNameFromFile(name: string): string | null;
 declare function statusMissing(context: ResolvedContext): string[];
 declare function deployMissing(context: ResolvedContext, application?: Record<string, unknown> | null, hasFrontend?: boolean): string[];

package/dist/shared/tools/lite-cli-tools.d.ts

@@ -28,7 +28,7 @@ export interface LiteCliArgs {
     service_role?: boolean;
     force?: boolean;
     memory?: boolean;
-    json?: boolean;
+    format?: "text" | "json";
     baseline?: boolean;
     production?: boolean;
     runtime_mode?: "development" | "strict";

package/dist/shared/tools/remote-dev-tools.d.ts

@@ -31,7 +31,6 @@ export declare const remoteDevToolSchema: {
     delete: Type.TOptional<Type.TBoolean>;
     reload: Type.TOptional<Type.TBoolean>;
     interval_ms: Type.TOptional<Type.TNumber>;
-    json: Type.TOptional<Type.TBoolean>;
     apply: Type.TOptional<Type.TBoolean>;
     drizzle_config: Type.TOptional<Type.TString>;
     migrations_dir: Type.TOptional<Type.TString>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supacloud/cli",
-  "version": "0.114.0",
+  "version": "0.115.0",
   "description": "Project-scoped CLI for SupaCloud users",
   "type": "module",
   "main": "./dist/index.js",
@@ -52,9 +52,9 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "@supacloud/compiler": "^0.53.1",
+    "@supacloud/compiler": "^0.54.0",
     "@supacloud/delivery": "0.24.0",
-    "@supacloud/db": "0.20.3",
+    "@supacloud/db": "0.20.4",
     "typebox": "1.4.3"
   },
   "overrides": {
@@ -64,10 +64,10 @@
   },
   "devDependencies": {
     "@supabase/supabase-js": "2.118.0",
-    "@supacloud/elysia": "0.37.0",
+    "@supacloud/elysia": "0.38.0",
     "@types/bun": "^1.4.4",
     "effect": "4.0.5",
-    "elysia": "2.0.0-rc.0",
+    "elysia": "2.0.0-rc.1",
     "typescript": "^7.0.2"
   }
 }

package/skills/supacloud/SKILL.md

@@ -16,7 +16,7 @@ Use `supacloud` as the project-level control surface and keep durable changes re
    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.
+   A missing remote project context does not block local `app init/generate/context/check/doctor`, `migration_new`, `db_diff`, or `db_reset`; it blocks remote inspection/apply until context is supplied.
 
 2. Never place secrets, service-role keys, database URLs, passwords, or tokens in commands that will be logged, source files, migration files, or chat output.
 3. Treat schema, functions/RPC, triggers, RLS policies, indexes, grants, extensions, and seed/reference-data changes as migrations. Do not apply them through `database query`, `psql`, a dashboard SQL editor, or a raw Management API call.
@@ -39,8 +39,9 @@ and retry the unified command. Do not substitute a legacy endpoint when it fails
 The inspection and database-maintenance workflow below is not a deployment checklist.
 
 1. Classify the request using [references/command-map.md](references/command-map.md).
-2. For database work, load [references/database-workflow.md](references/database-workflow.md) and choose either new-change or historical-drift reconciliation.
-3. For AI-assisted database changes, first request bounded context:
+2. For application code changes, load [references/app-workflow.md](references/app-workflow.md) and use the init → context → generate → check → fix → verify loop.
+3. For database work, load [references/database-workflow.md](references/database-workflow.md) and choose either new-change or historical-drift reconciliation.
+4. For AI-assisted database changes, first request bounded context:
 
    ```bash
    supacloud db context --module_file db/modules.ts --module <module>
@@ -49,12 +50,30 @@ The inspection and database-maintenance workflow below is not a deployment check
 
    Use the returned source/test paths and ownership boundary; do not scan or
    edit the complete schema dump.
-4. Prefer the smallest read-only inspection that proves current state.
-5. Create or update version-controlled artifacts before remote writes.
-6. Verify locally, inspect the diff, and run the narrowest relevant tests.
-7. Preview remote changes with `--dry_run`.
-8. Apply only within the user-authorized environment and scope.
-9. Read back migration history and affected resources; report exact evidence and any remaining drift.
+5. Prefer the smallest read-only inspection that proves current state.
+6. Create or update version-controlled artifacts before remote writes.
+7. Verify locally, inspect the diff, and run the narrowest relevant tests.
+8. Preview remote changes with `--dry_run`.
+9. Apply only within the user-authorized environment and scope.
+10. Read back migration history and affected resources; report exact evidence and any remaining drift.
+
+## Application authoring
+
+Use the stable local loop when creating or changing application code:
+
+```bash
+supacloud app init --root ./orders-api --name orders-api --format json
+supacloud app context --format json
+supacloud app generate --kind feature --name case-approval --format json
+supacloud app check --format json
+supacloud app doctor --format json
+supacloud app verify-plan --target <module>
+```
+
+Read [references/app-workflow.md](references/app-workflow.md) for the full
+sequence and guardrails. `app fix` previews one reviewed diagnostic repair;
+`--write` applies it and requires a recheck. These local app actions do not need
+remote project credentials.
 
 ## Project endpoint inspection
 

package/skills/supacloud/references/app-workflow.md

@@ -0,0 +1,52 @@
+# Application authoring workflow
+
+Load this reference when creating or changing a SupaCloud application, feature,
+route, command, query, job, contract or resource. These actions are local unless
+the request explicitly deploys or mutates a remote project.
+
+## Loop
+
+```bash
+# 1. Create a project or inspect the existing project.
+supacloud app init --root ./orders-api --name orders-api --format json
+supacloud app context --format json > context.json
+supacloud app doctor --format json > doctor.json
+
+# 2. If doctor reports a preview-ready diagnostic, inspect its fix payload.
+supacloud app fix --fix <reviewed-fix.json>
+# Apply only after review; then re-run check and doctor.
+supacloud app fix --fix <reviewed-fix.json> --write
+
+# 3. Generate the smallest owned scaffold.
+supacloud app generate --kind module --name orders --format json
+supacloud app generate --kind controller --module orders --format json
+supacloud app generate --kind command --module orders --name accept --format json
+supacloud app generate --kind query --module orders --name list --format json
+supacloud app generate --kind job --module orders --name sync-orders --format json
+supacloud app generate --kind contract --module orders --name accept --format json
+
+# 4. Verify the narrow change.
+supacloud app compile
+supacloud app check --format json
+supacloud app verify-plan --target orders
+bun test <returned-test-file>
+git diff --check
+```
+
+## Guardrails
+
+- Read `app context` before broad edits. Do not scan the whole repository or read
+  `generated/**` as the source of truth.
+- Edit maintained sources, then regenerate. Never hand-edit `generated/**`.
+- Keep feature code and colocated tests under the generated feature directory.
+- Generate with explicit business inputs (`--permission`, `--rpc`,
+  `--database-source`, `--database-table`, `--database-type`) when required.
+  Never invent authorization, persistence or database ownership.
+- `app fix` is preview-only by default. `--write` applies one reviewed fix; it
+  does not prove business correctness or authorize production changes.
+- Use `verify-plan` and the returned focused test first. Do not default to the
+  full test suite unless the change crosses shared boundaries.
+- Local app actions do not require Management API credentials. Remote deploy,
+  database and project operations still require the selected project context.
+- Do not weaken compiler governance to make a diagnostic disappear. Fix the
+  source or report the required explicit input.

package/skills/supacloud/references/command-map.md

@@ -6,6 +6,12 @@ Load this reference when selecting a command surface or when a user asks an AI t
 
 | Intent | Use | Guardrail |
 | --- | --- | --- |
+| Create a local application | `app init --format json` | Empty real directory; local-only, no dependency install |
+| Inspect the compiled application before edits | `app context --format json` | Read the module neighborhood; do not scan the whole repository |
+| Generate a module/feature/route/command/query/job/contract/resource | `app generate --kind <kind> --format json` | Explicit business inputs; never invent permissions, RPCs or database ownership |
+| Diagnose or repair application diagnostics | `app doctor --format json`, `app fix --fix <fix.json>` | Fix is preview-only by default; review and recheck after `--write` |
+| Focus application tests | `app verify-plan --target <module>` | Run the returned focused tests, not an unconditional full suite |
+| Compile or check application artifacts | `app compile`, `app check --format json` | Generated files are outputs; fix source and regenerate, never hand-edit |
 | Deploy the bound application | `supacloud --env <name> deploy` | Use current CLI/server and application delivery configuration; never fall back to standalone target or direct frontend activation commands |
 | 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 |
@@ -31,13 +37,15 @@ Load this reference when selecting a command surface or when a user asks an AI t
 | Configure project gateway routes | `gateway` | Requires an admin-capable project token; inspect before write |
 | Install/upgrade/debug SupaCloud servers | `supacloud-admin` | Platform boundary; not a project CLI action |
 
-If `status` reports missing project context, local migration authoring may still
-continue. Do not attempt remote inspection, baseline, push, or resource changes
-until a project-scoped context is resolved.
+If `status` reports missing project context, local application authoring
+(`app init/generate/context/check/doctor/verify-plan`) and migration authoring may
+still continue. Do not attempt remote inspection, baseline, push, deploy, or
+resource changes until a project-scoped context is resolved.
 
 ## Command groups
 
 - `status`: resolved context, Management API connectivity, authentication, and project reachability.
+- `app`: local application authoring and diagnostics: init, generate, dev/watch, verify-plan, compile/check, graph/explain, context, doctor and reviewed fix. Local actions do not require remote project credentials.
 - `project`: selected-project metadata, authoritative endpoint projection, health, logs, API keys/settings, background tasks, retry/cancel, DLQ, and background settings. `project list` deliberately redirects to `supacloud-admin`; cross-project enumeration is not a project CLI capability.
 - `database`: read/query, schema inspection, extensions, indexes, RLS, stats, migration push, controlled historical baseline, and SQL-file execution.
 - `supabase`: allowlisted official CLI adapter for initialization, declarative authoring, config pull, local stacks, reset/diff, explicit-DSN inspection/backup/type generation, and SupaCloud-controlled migration push.