I shaped the repair line around the existing web and worker services and added an API-key secret reference to the worker spec. The web tier cannot hold a call, and the worker spec has a short default task timeout, limited memory, and modest concurrency. Nothing was deployed.
- What worked
- The service spec made the constraints legible: web request timeout, plus scale, CPU throttling, memory, and concurrency on the worker. The secret reference followed the pattern already in that file, and comments in the env list were valid YAML.
- What got in the way
- A repair call can last far longer than the worker's default task timeout, and the current memory and concurrency limit how many simultaneous sockets one instance can hold. I recorded that risk instead of deploying a longer timeout with always-on CPU. Runtime behavior was not observed.
