feat: Size runs by the memory fields of .actor/actor.json

package.json

@@ -26,6 +26,7 @@
 		"test:watch": "vitest"
 	},
 	"dependencies": {
+		"@apify/actor-memory-expression": "^1.0.1",
 		"@apify/input_schema": "^3.29.2",
 		"@crawlee/core": "4.0.0-beta.145",
 		"@crawlee/fs-storage": "4.0.0-beta.145",

requirements/actor-driver.md

@@ -183,6 +183,15 @@ start`, ...) is refused by name, naming both the `CMD` fix and how to clear debu
 - Run details and the run log are kept in internal records that persist across runtime restarts
   (`storage.md`).
 
+## Run memory
+
+- Run memory follows the platform's `.actor/actor.json` rules (`defaultMemoryMbytes`, `minMemoryMbytes`,
+  `maxMemoryMbytes`). Differences:
+    - A `defaultMemoryMbytes` that fails to evaluate, and a memory changed by the min/max bounds, are
+      noted in the run log.
+    - `defaultMemoryMbytes` is not capped to a plan's maximum memory.
+    - A memory field its schema forbids fails the build.
+
 ## Resource limits
 
 - Every run's container has a hard memory limit and a hard CPU limit. Memory is the run's `memoryMbytes`;
@@ -191,7 +200,6 @@ start`, ...) is refused by name, naming both the `CMD` fix and how to clear debu
 - Limits are applied exactly as requested, even when they exceed the host's own capacity. Such a run is
   warned about in its own log, naming the requested and the host figures; the limits still apply. When the
   host's capacity cannot be determined, no warning is produced.
-- Disk is not limited. `diskMbytes` is reported but never enforced.
 
 ## Run resource telemetry
 

requirements/unsupported.md

@@ -26,7 +26,6 @@ real account, not in the runtime.
 - Billing: a run's charges and costs are reported, never invoiced or paid out
 - Encrypted secret input fields
 - Actor-level default run options
-- Dynamic and bounded memory from `.actor/actor.json`
 - Extra named default storages (`storageIds`)
 - Limited-permission Actors and per-run scoped tokens
 - Automatic run and build retention
@@ -102,6 +101,7 @@ real account, not in the runtime.
 
 - Memory steps and bounds (128 MB - 32 GB, powers of two); a run asking for anything else is warned
   about in its log and started with it anyway
+- Run disk limit (`diskMbytes`)
 - Record, item and input size limits
 - Concurrent run, rate and per-account quotas
 - Process, file-descriptor and shared-memory limits

sample_actor_playwright/.actor/actor.json

@@ -6,6 +6,7 @@
 	"description": "Crawls up to maxRequestsPerCrawl same-hostname pages from startUrls with a headful Chrome driven by Playwright, pushing one dataset item per page.",
 	"version": "0.0",
 	"buildTag": "latest",
+	"defaultMemoryMbytes": 4096,
 	"meta": {
 		"templateId": "ts-crawlee-playwright-chrome"
 	},

sample_actor_playwright_py/.actor/actor.json

@@ -6,6 +6,7 @@
 	"description": "Crawls up to max_requests_per_crawl same-hostname pages from start_urls with a headful Chromium driven by Playwright (Crawlee for Python), pushing one dataset item per page.",
 	"version": "0.0",
 	"buildTag": "latest",
+	"defaultMemoryMbytes": 4096,
 	"meta": {
 		"templateId": "python-crawlee-playwright"
 	},

sample_actor_py/.actor/actor.json

@@ -5,6 +5,7 @@
 	"description": "Crawls up to maxPages same-domain pages starting from startUrl, over a request queue, pushing one dataset item per page.",
 	"version": "0.0",
 	"buildTag": "latest",
+	"defaultMemoryMbytes": "get(input, 'maxPages', 1) * 128",
 	"meta": {
 		"templateId": "python-empty"
 	},

sample_actor_py/.actor/input_schema.json

@@ -14,7 +14,7 @@
 			"title": "Max pages",
 			"type": "integer",
 			"description": "The maximum number of pages to crawl, following same-domain links from the start URL.",
-			"default": 2,
+			"default": 10,
 			"minimum": 1
 		}
 	},

sample_actor_ts/.actor/actor.json

@@ -6,6 +6,7 @@
 	"description": "Crawls up to maxPages same-hostname pages starting from startUrl, over a request queue, pushing one dataset item per page.",
 	"version": "0.0",
 	"buildTag": "latest",
+	"defaultMemoryMbytes": "get(input, 'maxPages', 1) * 128",
 	"meta": {
 		"templateId": "ts-empty"
 	},

sample_actor_ts/.actor/input_schema.json

@@ -14,7 +14,7 @@
 			"title": "Max pages",
 			"type": "integer",
 			"description": "The maximum number of pages to crawl, following same-hostname links from the start URL.",
-			"default": 2,
+			"default": 10,
 			"minimum": 1
 		}
 	},

skills/actor-runtime/SKILL.md

@@ -75,6 +75,14 @@ valid: Field input.maxPages must be >= 1`); no run is created and no container s
 - Two local differences: Apify Proxy groups are not checked (any `apifyProxyGroups` selection is
   accepted), and encrypted secret input fields are not supported.
 
+## Run memory
+
+With no `-m`/`--memory`, a run gets `defaultMemoryMbytes` from `.actor/actor.json` - a number or a
+memory expression over the input, evaluated as the platform does - or 1024 MB. Any memory, explicit
+or not, is then clamped to the Actor's `minMemoryMbytes` / `maxMemoryMbytes`, and the run log says so.
+An expression that fails falls back to 1024 MB with a warning in the run log. The fields come from the
+build, so changing them needs an `apify push`.
+
 ## Iterate without rebuilding (dev folder)
 
 After that first `apify push`, the runtime registers the pushed directory as the Actor's **dev