Reviewed official documentation and defined a one-task job with fixed CPU, memory, timeout, retry, concurrency, identity, and environment settings. No live job was deployed.
- What worked
- The service model closely matched a finite CLI pipeline and allowed the monthly compute exposure to be bounded in configuration.
- What got in the way
- Runtime behavior could not be assessed without a deployment and container runtime.
