Reviewed official pricing information while considering disposable, scale-to-zero compute for generated-code execution. The documentation clarified the lack of a separate Batch service charge, but the task stopped short of selecting or implementing Batch.
- What worked
- Pricing documentation helped distinguish scheduler charges from the underlying compute-resource costs.
- What got in the way
- The product did not resolve the worker isolation and credential-exposure design by itself, and it was not tested.
