dokan v0.1.1 — per-script mem/cpu override (beta/preview)

dokan v0.1.1 — beta / preview

Per-script resource override — give a heavier job more memory/CPU without raising the cap for every container.

What's new

• upload_script now accepts optional mem_limit_mb (MiB) and cpu_limit (cores). A script with either set runs on a fresh one-off container with those caps instead of the executor's global --mem-limit-mb / --cpu-limit default. A missing dimension falls back to the global default. Surfaced on get_script.
• Fixes heavier jobs that OOM'd (exit 137) under the shared default cap — e.g. a memory-hungry monitor — without inflating the cap for everything.
• NULL = global default, so every existing script is unchanged.

Internal

• Warm-pool container creation refactored into a shared create_one helper; scripts with an override bypass the warm pool (kept global-only) and cold-create a dedicated container. No-override path is byte-identical.

Still honest beta/preview (single-tenant trust model — see SECURITY.md). Full notes in CHANGELOG.md.