agentful 0.4.5 → 0.4.6

package/README.md

@@ -80,6 +80,12 @@ Actions have **no staging**: they run from your project's source, so a push can
 change what the published app does immediately, while warm instances may serve
 the previous code for up to five minutes.
 
+Actions run **only while the managed server is switched on** in the Backend tab
+(`agentful backend` opens it). A push stores your action files either way, but
+until the server is on every call answers `404 server_not_enabled`. The CLI can
+enable the database for you — not the server. Switching on takes effect on the
+next call; switching off takes effect within 60 seconds.
+
 The figures above are rendered into `AGENTFUL_CLOUD.md` from the machine-readable
 contract at <https://app.agentful.dev/cli/platform-contract.json>
 (`server_side`); the full picture for humans is at

package/dist/index.cjs

@@ -3044,7 +3044,7 @@ var VERSION, brand, useColor, wrap, paint, tuiDesign, sym, ui;
 var init_branding = __esm({
   "src/branding.ts"() {
     "use strict";
-    VERSION = "0.4.5" ? "0.4.5" : null.version;
+    VERSION = "0.4.6" ? "0.4.6" : null.version;
     brand = {
       name: "agentful",
       // the command users type
@@ -5618,10 +5618,11 @@ var contract_default = {
     $comment_limits: "Compressed zip bytes. Enforced server-side as MAX_TEMPLATE_ZIP_UPLOAD_BYTES (aws-services/workspace-manager/handler.py); ~8 MB as base64, under the API Gateway 10 MB request cap."
   },
   server_side: {
-    $comment: "What 'server' means on this platform (server-option plan 2026-09-18, AP2). THREE separate tracks with separate limits \u2014 never quote one track's limits for another. managed_actions.limits is pinned against the source constants by check-parity.py (check 10) and against the agent instructions (check 11); the behaviour behind action_timeout_budget_s is pinned in aws-services/action-runner/tests/sandbox_contract.test.js. Additive block: no schema_version bump.",
+    $comment: "What 'server' means on this platform (server-option plan 2026-09-18, AP2). THREE separate tracks with separate limits \u2014 never quote one track's limits for another. managed_actions.limits is pinned against the source constants by check-parity.py (check 10) and against the agent instructions (check 11); the behaviour behind action_timeout_budget_s is pinned in aws-services/action-runner/tests/sandbox_contract.test.js, the one behind switch_off_delay_s (and the refusal itself) in tests/server_switch.test.js. The switch is enforced only while infrastructure/lib/s3-lambda-stack.ts says SERVER_SWITCH_ENFORCEMENT 'enforce' \u2014 check 12 fails if switch_note promises it under any other mode. Additive block: no schema_version bump.",
     managed_actions: {
       label: "Managed Server Actions",
       summary: "Short request/response functions the platform runs for the project. One file is one endpoint; JSON in, JSON out. Backend tab: Server \u2192 Managed.",
+      switch_note: 'Actions run only while the managed server is switched on in the Backend tab (Server \u2192 Managed). A managed database alone does not switch it on. While it is off, every action of the project answers 404 server_not_enabled. Switching on takes effect on the next call; switching off takes effect after the switch-off delay given under Limits at the latest, because warm instances remember "on" for that long. Storing is not running: uploading or pushing action files is not gated by the switch.',
       offers: [
         "One file = one endpoint: .server/actions/<name>.js is served at /api/p/{projectId}/actions/{name}, any HTTP method, JSON in, JSON out",
         "Runtime secrets that never reach the browser: await ctx.secrets.get('server.<name>')",
@@ -5674,7 +5675,8 @@ var contract_default = {
         max_body_bytes: 1048576,
         max_code_bytes: 262144,
         project_concurrency: 10,
-        max_action_depth: 5
+        max_action_depth: 5,
+        switch_off_delay_s: 60
       },
       limits_note: "The per-action budget is a figure to plan with, not a guaranteed stop: an action still waiting on ctx.fetch or ctx.data when the budget runs out is answered with 408 timeout, synchronous code runs on until the hard limit, and after a 408 the action may still complete calls it had already started. Build actions so that a repeated call ends in the same state."
     },
@@ -6118,6 +6120,7 @@ function checkBackendDeclaration(rootDir = process.cwd()) {
 }
 
 // src/lib/backendSync.ts
+var SWITCH_OFF_DELAY_S = contract_default.server_side.managed_actions.limits.switch_off_delay_s;
 var joinMethods = (methods) => methods && methods.length ? methods.join(" + ") : "none";
 function purposeOf(declaration, key) {
   const entry = (declaration?.secrets ?? []).find((s) => s.key === key);
@@ -6260,9 +6263,9 @@ async function fetchBackendSessionState(auth, userId, projectId, opts = {}) {
 }
 function describeServerState(state) {
   if (state.serverEnabled) {
-    return "Server: managed, enabled (Server Actions \u2014 functions we run for you). There is no activation point: pushed action code can change what the published app does immediately; warm instances may serve the previous code for up to five minutes.";
+    return `Server: managed, enabled (Server Actions \u2014 functions we run for you). There is no activation point: pushed action code can change what the published app does immediately; warm instances may serve the previous code for up to five minutes. Switching it off in the Backend tab stops every action within ${SWITCH_OFF_DELAY_S} s.`;
   }
-  const notOn = "Action files you push are still executable through the platform API \u2014 the switch does not turn them off. It controls /api/* routing on the app's own domain and the sync of server.* secrets.";
+  const notOn = "Action files you push are stored, but calls to them answer 404 server_not_enabled until you switch the managed server on in the Backend tab (`agentful backend` opens it \u2014 the CLI can enable the database, not the server). Switching on takes effect on the next call.";
   if (state.serverMode === "byo") {
     return `Server: your own API (${state.serverStatus || "not active"}) \u2014 /api/* on the app's domain is forwarded to it. Managed server: not switched on. ${notOn}`;
   }
@@ -7115,11 +7118,12 @@ function backendSessionLines(backend) {
   return lines.join("\n");
 }
 function managedServerLine(backend) {
+  const delay2 = contract_default.server_side.managed_actions.limits.switch_off_delay_s;
   if (backend.serverEnabled) {
-    return "Managed server: **enabled**. **There is no activation point:** pushed action source can change what the published app does immediately, while warm instances may keep serving the previous code for up to five minutes.";
+    return `Managed server: **enabled**. **There is no activation point:** pushed action source can change what the published app does immediately, while warm instances may keep serving the previous code for up to five minutes. Switching the server off in the Backend tab stops every action within ${delay2} s.`;
   }
   const ownApi = backend.serverMode === "byo" ? "Server: the owner connected **an API of their own** \u2014 `/api/*` on the app's domain is forwarded to it, and the platform adds no secret and authorizes nobody. " : "";
-  return `${ownApi}Managed server: **not switched on** in the Backend tab. **Action files you push are still executable through the platform API** \u2014 the switch does not turn them off. It controls \`/api/*\` routing on the app's own domain and the sync of \`server.*\` secrets.`;
+  return `${ownApi}Managed server: **not switched on** in the Backend tab. **Action files you push are stored, but every call to them answers \`404 server_not_enabled\`** until the owner switches the managed server on (\`agentful backend\` opens the tab; the CLI can enable the database, NOT the server). Switching on takes effect on the next call. Never tell the user an action works before the server is on.`;
 }
 var bytes = (n) => n >= 1024 * 1024 ? `${n / (1024 * 1024)} MB` : `${n / 1024} KB`;
 function serverSideSection() {
@@ -7130,6 +7134,7 @@ function serverSideSection() {
       `### ${heading} ${t.label}`,
       "",
       t.summary,
+      ...t.switch_note ? ["", t.switch_note] : [],
       "",
       "Offers:",
       ...t.offers.map((o) => `- ${o}`),
@@ -7147,7 +7152,7 @@ function serverSideSection() {
     track(
       "managed_actions",
       "(a)",
-      `${a.action_timeout_budget_s} s budget per action, ${a.hard_timeout_s} s hard limit, ${a.memory_mb} MB memory, request body \u2264 ${bytes(a.max_body_bytes)}, action source \u2264 ${bytes(a.max_code_bytes)}, ${a.project_concurrency} concurrent calls per project, self-call depth \u2264 ${a.max_action_depth}.`
+      `${a.action_timeout_budget_s} s budget per action, ${a.hard_timeout_s} s hard limit, ${a.memory_mb} MB memory, request body \u2264 ${bytes(a.max_body_bytes)}, action source \u2264 ${bytes(a.max_code_bytes)}, ${a.project_concurrency} concurrent calls per project, self-call depth \u2264 ${a.max_action_depth}, switch-off delay \u2264 ${a.switch_off_delay_s} s.`
     ),
     track("own_api", "(b)", null),
     track(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentful",
-  "version": "0.4.5",
+  "version": "0.4.6",
   "description": "Agentful in your terminal — local development with push-to-cloud previews",
   "license": "Apache-2.0",
   "homepage": "https://agentful.dev",