@backifydev/cli 0.3.6 → 0.3.7

package/dist/index.js

@@ -17593,6 +17593,28 @@ function unzipSync(data, opts) {
 import { createRequire as createRequire2 } from "node:module";
 import { dirname, resolve } from "node:path";
 import { existsSync, mkdirSync, writeFileSync } from "node:fs";
+async function deployFunctions(call2, appId, environmentId, packageBytes, options = {}) {
+  const result = await call2("/apps/" + appId + "/functions/environments/" + environmentId + "/deploy?confirm=true", { method: "POST", headers: { "content-type": "application/zip" }, body: packageBytes });
+  if (result.status === "succeeded") return;
+  if (!result.operationId) throw new Error("Function deployment did not return a tracking operation. Success has not been verified.");
+  const now = options.now ?? Date.now;
+  const deadline = now() + (options.timeoutMs ?? 20 * 6e4);
+  const sleep = options.sleep ?? ((milliseconds) => new Promise((resolve24) => setTimeout(resolve24, milliseconds)));
+  options.progress?.("Function deployment queued. Waiting for operation " + result.operationId + ".");
+  while (now() < deadline) {
+    let operation;
+    try {
+      operation = await call2("/operations/" + result.operationId);
+    } catch (cause) {
+      throw new Error("Could not read function deployment operation " + result.operationId + ". Check its status before uploading again: " + String(cause));
+    }
+    if (operation.status === "succeeded") return;
+    if (operation.status === "failed" || operation.status === "cancelled") throw new Error("Function deployment " + operation.status + ": " + (operation.errorMessage ?? result.operationId));
+    if (operation.status !== "pending" && operation.status !== "running") throw new Error("Unknown function deployment status: " + operation.status);
+    await sleep(Math.min(options.intervalMs ?? 2e3, Math.max(0, deadline - now())));
+  }
+  throw new Error("Stopped waiting for function deployment. Operation " + result.operationId + " continues on Backify; check its status before uploading again.");
+}
 async function packageFunctions(entry, output) {
   const entryPath = resolve(entry);
   if (!existsSync(entryPath)) throw new Error("Function entrypoint does not exist: " + entryPath);
@@ -17854,8 +17876,8 @@ function manifestDiagnostics(manifest, used) {
 // ../platform/dist/delivery.js
 var deliveryInstructions = `# Backify application delivery and prompt history
 
-Instruction version: 4
-Versioned guide: https://agent.backify.dev/v4/delivery.md
+Instruction version: 5
+Versioned guide: https://agent.backify.dev/v5/delivery.md
 
 These instructions are for AI coding tools building applications on Backify, not the Backify platform implementation. Complete the application and deliver a verified deployment, not just SDK setup. Respect the coding tool's own permissions and confirmation settings; preserve unrelated work and applicable repository instructions.
 
@@ -17873,7 +17895,7 @@ Initialize using App Id from the copied prompt and the current tool selection:
 
     npx @backifydev/cli@latest init --app <app-id> --agent <current-tool>
 
-For a tool without a built-in preset, replace --agent <current-tool> with --instruction-file <relative-path>. Read BACKIFY.md and the instruction file used by the current AI coding tool before changing application code. Create or update only instruction files used by that tool; never create files for other coding tools. Use --agent for a built-in tool preset or --instruction-file <relative-path> for the current tool's native instruction file, as described in the setup guide. Initialization installs this workflow alongside the persistent SDK instructions. Follow https://agent.backify.dev/v4 for instruction version 4; use the guide matching backify.json in an existing application. Do not silently upgrade its managed instruction version or overwrite instructions outside the managed block.
+For a tool without a built-in preset, replace --agent <current-tool> with --instruction-file <relative-path>. Read BACKIFY.md and the instruction file used by the current AI coding tool before changing application code. Create or update only instruction files used by that tool; never create files for other coding tools. Use --agent for a built-in tool preset or --instruction-file <relative-path> for the current tool's native instruction file, as described in the setup guide. Initialization installs this workflow alongside the persistent SDK instructions. Follow https://agent.backify.dev/v5 for instruction version 5; use the guide matching backify.json in an existing application. Do not silently upgrade its managed instruction version or overwrite instructions outside the managed block.
 
 Run the following to discover the connected hosting target, repository, branch, reports, releases, and deployment failures:
 
@@ -17907,6 +17929,12 @@ For Backify Cloud, build a static application with a build script and index.html
 
 Do not claim unsupported hosted server functions or SDK execution paths work. Report unsupported runtime requirements instead of substituting another platform. Keep secrets server-side and out of browser code, project files, and Git.
 
+## Local development before delivery
+
+From the first setup, make every new application runnable and testable locally without a cloud deployment. Follow the matching setup guide's local development steps: preserve the framework, provide a package-manager dev script and README, use @backifydev/sdk/local for platform capabilities and tests, and keep local state and credentials out of Git. Use a native framework dev server for frontend-only apps; for Backify server capabilities, configure backify.yaml and npx @backifydev/cli@latest dev --mode lightweight --json with the supported frontend adapter when needed. Disclose emulator limits and any full-runtime prerequisites.
+
+Start the application, wait for readiness, request the actual local application URL, and verify a representative user flow before shipping. Document safe seed data and local test identities where needed. Cloud connection, preview approval, or deployment failure must not prevent safe local testing; report those blockers separately without bypassing authorization. If requirements are missing, verify a minimal runnable shell before asking the required final question. Never claim local readiness from a build or management-dashboard response alone.
+
 ## Verify, push, and publish
 
 Run:
@@ -17925,6 +17953,8 @@ If testing or approval is required, return the preview URL and explain the remai
 
 After setup or a delivery attempt, give the user concise instructions: explain what is ready, how to open and use the application, and any sign-in, testing, approval, or other next steps. Summarize actual checks and blockers without exposing credentials or asking the user to perform routine deployment work the coding tool can complete.
 
+Include the verified Local URL, exact start command, and local testing/sign-in steps even when cloud delivery is blocked. If local startup was not verified, say unavailable and explain the blocker.
+
 Include separate Preview URL and Production URL lines, using the actual URLs returned by CLI status or deployment results. Include both URLs when available. If either is unavailable, say not deployed or unavailable and explain why; never invent a URL or claim an unverified deployment is live. When production still serves an earlier release, label it as the existing production version and explain that the new changes are preview-only or awaiting approval.
 
 If application requirements are missing after setup, finish the response with this exact question as its final line, without any text after it:
@@ -17935,7 +17965,7 @@ These instructions are an explicit agent workflow, not a universal chat intercep
 `;
 
 // ../platform/dist/index.js
-var INSTRUCTION_VERSION = 4;
+var INSTRUCTION_VERSION = 5;
 var SDK_PACKAGE = "@backifydev/sdk";
 var DOCS_URL = "https://docs.backify.dev";
 var MAIL_LIMITS = Object.freeze({
@@ -18005,6 +18035,7 @@ Require explicit confirmation before destructive data operations or removing sta
 ## Implementation workflow
 
 Inspect the framework, lockfile, scripts, configuration, and applicable repository instructions before editing. Preserve the existing framework and unrelated work. Implement the requested application rather than stopping at SDK setup; ask what to build if requirements are missing.
+From the first setup, make every new application runnable and testable locally without a cloud deployment. Provide a package-manager start script, document prerequisites and local test identities, start the application, and verify its local URL and a representative user flow. Use \`@backifydev/sdk/local\` for local platform capabilities, keep local state and credentials out of Git, and clearly disclose emulation limits. Include the actual Local URL, start command, checks, and any blockers in the user handoff; never claim an unstarted application is ready. Follow the matching setup guide for framework-specific local commands.
 Run relevant tests, typechecking, lint, and builds using the repository's scripts when available. Report changes, checks, and remaining blockers accurately; do not claim unverified success.
 
 ## Connected application delivery
@@ -23070,7 +23101,7 @@ async function main() {
         const environmentId = option("--environment");
         const packagePath = option("--package");
         if (!environmentId || !packagePath || !args.includes("--confirm")) throw new Error("Use backify functions deploy --environment <environment-id> --package <functions.zip> --confirm. This replaces the complete function project.");
-        await call("/apps/" + appId + "/functions/environments/" + applicationGuid(environmentId) + "/deploy?confirm=true", { method: "POST", headers: { "content-type": "application/zip" }, body: new Uint8Array(readFileSync24(packagePath)) });
+        await deployFunctions(call, appId, applicationGuid(environmentId), new Uint8Array(readFileSync24(packagePath)), { progress: (message) => console.log(message) });
         console.log("Functions deployed.");
       } else throw new Error("Use backify functions package or backify functions deploy");
       break;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@backifydev/cli",
-  "version": "0.3.6",
+  "version": "0.3.7",
   "description": "Command-line setup and diagnostics for Backify applications",
   "type": "module",
   "bin": {