@withandeo/cli 0.19.5 → 0.19.6

package/skill/tender-accounts/references/workflows.md

@@ -37,7 +37,22 @@ export class CustomerActivity extends WorkflowEntrypoint<{}, { runId: string }>
 // return Response.json({ runId: await run.id }, { status: 202 });
 ```
 
-The CLI packages code for Andeo's Dynamic Workflow hosts. Do not deploy a separate Cloudflare workflow. Global `fetch()` works inside durable steps; a service is not required merely for HTTP. Pin approved destinations, validate variable URLs, bound timeouts/redirects, and make external effects idempotent because steps retry. A callback that only knows a run ID is a demo receipt, not sender authentication; use secret-backed verification for trusted callbacks.
+The CLI packages code for Andeo's Dynamic Workflow hosts. Do not deploy a separate Cloudflare workflow. Public network is denied by default. To permit direct HTTPS, create `andeo.workflow-egress.json` beside the Wrangler configuration with schema `andeo.workflow-egress/v1` and one entry for every declared logical workflow:
+
+```json
+{
+  "schema": "andeo.workflow-egress/v1",
+  "workflows": {
+    "customer-activity": {
+      "https": [{ "hostname": "gateway.example.com", "port": 443 }]
+    }
+  }
+}
+```
+
+An omitted file gives every workflow an empty allowlist. When the file exists, every declared workflow name must be present; use `"https": []` for workflows with no direct public fetches. Destinations are exact HTTPS hostname/443 pairs—never wildcards, IP literals, internal names, credentials, or alternate ports. Redirected GET/HEAD requests are revalidated against the same policy; redirects for mutations are denied. Keep variable URLs constrained to the retained allowlist and bound timeouts and response sizes.
+
+The allowlist covers only direct global `fetch()` from workflow code. It does not list connected service bindings. Put secret-backed provider calls, provider SDKs, and operations needing credentials behind an approved service contract; do not add that provider's public hostname unless the workflow itself fetches it directly. Make external effects idempotent because durable steps retry. A callback that only knows a run ID is a demo receipt, not sender authentication; use secret-backed verification for trusted callbacks.
 
 ## Environment and services