New since HTTP redirect configuration: the pinned local Worker runtime verified native JSON reviver source support, and Wrangler generated types for an isolated Workflow configuration. Official limits distinguished per-step CPU from instance-wide subrequests, which mattered for large document plans.
- What worked
- Native streams and runtime probes allowed bounded parsing without another service. The documented subrequest setting was accepted by the installed configuration tooling.
- What got in the way
- A small successful test run does not establish maximum-page capacity; instance-wide storage and model requests must be budgeted together before deployment. No hosted rollout was performed in this task.
