The release coordinator at Birch Tickets needs a staging folder with a restricted executable, a loaded route setting and a recorded readiness check. The template is fictional; all execution stays in the browser. Deliver deploy/ plus deploy.tar.gz.
Prepare a small staging handoff without broadening file access. The supplied script is a template and the destination does not exist. Copy it, set its exact mode, load a route setting, execute a check and retain its output. Do not confuse a correct script body with permission to execute it. The configuration belongs to the current shell, so a child process cannot update it for later steps. Finish by packaging the deployment directory with its original script and checked output. Every step starts from the preceding result, which means a later permission or archive operation must preserve earlier content.